sure, just tell me what content you want me to do and what timeframe works for you. can do a nostr:npub1eaz6dwsnvwkha5sn5puwwyxjgy26uusundrm684lg3vw4ma5c2jsqarcgz for it
Calling it for a couple hours, mostly turned into dependency updating and had to reinstall nix (since I updated my macOS last night) then spend half an hour waiting for nix devvlops to run in all my fedimint repos.
Got a surprise early dinner date with the wife "we" planned last week I'm jetting off to haha (not sure what percentage of these "plans" actually occurred haha, she counts it as planning when she asks me something while I'm coding and I dumbly nod along and grunt while working lol)
nostr:note194sh785xtpmh4v6kd5q97zvugtg7mt4tpysradrq34j5mueccg2sskk245
https://github.com/fedixyz/fedi
didn't see this, tag me next time haha, I'm on here all the time. Asking about getting nostr:npub1uq70uqgas9pyhds2zt57kr9se8rg3s68ztphjnq82ts8rzeknmeql7u0c2 account access so I can respond there too
feelzgudman
nostr:note1chfk60fcpzyx9lu8p9aurjxvrs4fgnd9nxc2zzeczuaxs8havdrqt99e3l
Janitor time, let's see how many of these we can clean up
probably a retarded Q but how do I actually start a 
livestream on zap.stream haha
Calling it for today. Got a couple PRs reviewed and a new one up for letting the gateway just send and receive ecash like a normal client instead of having to do onchain pegins/pegouts. nostr:npub1yarprdrj3vxyp0su7xqd3u6z047na6792ezas6dqqt5tv4lce4ssjt0gd0 hopped in and helped review until we got stuck on some command line response deserialization error but gotta go walk the dog
nostr:note1kpqn7nlw7ulap5vrwrg65em34wt7s5hz02xy547l7naww2ghxmkq263t5j
tracking, question is whether I should extend the nip-87 PR from Ben or whether there's already something I'm not tracking for like "service provider" where you classify the service. know there's data vending machines but think there's also already something for like marketplaces and stuff
I want to have the lightning gateway announce itself for out of mint discovery over nostr, what's the best way to do that? Currently the gateway has to register with whatever mint its servicing and clients learn of it through the mint. Is there a service provider announcement nip separate from DVMs? or probably a different kind for like mint service provider announcement as a tweak to the NIP-87 PR? https://github.com/nostr-protocol/nips/pull/1110/files
Plan is to run a cashu mint alongside the fedimint lightning gateway against the same lightning, then eventually have the gateway just be generic to support routing for both cashu mints and fedimints. Thinking that direct announcement will work better as a base for third party reviews to reference instead of just the third party reviews/attestations?
nostr:npub1zxu639qym0esxnn7rzrt48wycmfhdu3e5yvzwx7ja3t84zyc2r8qz8cx2y is most of the way to a rust multiplatform that'd work great with CDK, write everything in Rust and dumps to native + wasm
think this looks a little better padding the bottom then moving that dynamic header to replace the wallet actions thing:
Working on a new UI for the Fedimint Lightning Gateway. It's a little complicated because they have 3 pools of funds they have to manage.
1. Ecash: the ecash they have across their different mints. I've currently got this showing as a single total with a clickthrough drilldown into the amount of ecash in each federation, but I think there's probably a better way to show this.
2. Lightning: Standard lightning channels, showing aggregate inbound and outbound with a drilldown for individual channels.
3. Onchain: onchain used in conjunction with the lightning and ecash liquidity management, should normally stay pretty small and just fill up when pegging out of a federation or for opening/closing lightning channels.
Also have an ongoing project of running a cashu mint on top of it and ideally show it in the same UI for management. but not sure the best way to do it, probably just a top level tab over from "Gateway" to "Mint". Maximize the gateway routing fees with normal lightning routing, fedimint routing, and optionally running a cashu mint ontop all in the same interface
They're separating off the first sat to sell separately on an ordinals market
https://github.com/fedimint/fedimint/issues/5525 <- fix will be in the next release
Neither does fedimint's ecash. The client associates the notes it holds with a federationId and can change that association the same way you do with the mintUrl.
It's more complex for the fedimint guardians to agree on an update to the config, creating the new federationId, but in principal it's the same. the approach to that consensus update process just needs to get agreed on and implemented as part of the next release or potentially a hotfix.
This is also possible in principle with the fedimint client, there's more complexity for doing the upgrade because the client associates its notes to the federation id which contains the original endpoints and the guardians have to first agree on the new config then the client has to acknowledge the new config.
99% of the complexity for fedimint here is the consensus not the ecash. But there's (potentially, still confirming implementation options) a short term fix for existing federations to allow a DNS rotation by a guardian and that being acknowledged and reflected in an updated client to reassociate its notes with the new config. Plus a longer term solution to remove the DNS dependency for new federations entirely.
nostr:note1dchlp9hztern24qqk55qy454aakj9wq42wwthxeqjeddrfmgqhaqu92qvm
The Great Fedi Defenestration
pro tip for travelling in Europe, the natives don't wake up til 9am so if you go running early you get all the outdoor siteseeing to yourself
npub1l8wk5a39qcnqkw9z60jmgepp8shy073cwapfl60wvrs8rgc6qltsq66m2c
is one of the more interesting bots to follow, good to have a consistent reminder in the timeline