Nix + Fedimint. Wanna learn more? Injest this👇
Call with
nostr:npub1m6yz8nwf0xl5cafjy0kurxn6hs67eleft8h4pj57n4tn4s8c8lgqd2mzj9 nostr:npub1tmycvul7aj4fxhypg5qkjgsjtx30zvnrfeufrgx9xlwtv0hne7cs67el78 nostr:npub1yarprdrj3vxyp0su7xqd3u6z047na6792ezas6dqqt5tv4lce4ssjt0gd0 and others
https://fountain.fm/episode/gOc183heBu2qTaHBpPPV
More here too. Much good. Very learn.
https://bitcointv.com/w/mdPgH8o4UugLpHdkxAHnMF
Today's Fedimint Deep Dive went over the nix dev setup the project uses. We didn't finish the whole thing but join us next week during the Deep Dive (Thursday at 12pmET) for the conclusion.
You already have an "account" with mining pools. And I can generate any npub I want, it doesn't have to be a primary nostr account. In fact, I would recommend against it.
poolimint - nostr is the accounts? Then ecash can only be “unlocked” with nsec. Maybe a proxy in front of the fedimint for actual pool software? Pool software gets main coinbase address from the fedimint. Shares are submitted as usual, and tallied up. Reward total is passed in from the pool to the fedimint so the respective npubs have their share according to pool rules. Ecash redemptions can be made by verifying ownership of said npub.
What problem would this disclosure fix?
2023-08-28 Fedimint Dev Call Summary
https://habla.news/u/EthanTuttle@learnfedimint.com/1693241710650
For more details, please view the recording here: https://bitcointv.com/w/4MDVgBucaxPZJvbBZaoPNG And find the list of PRs/Issues here: https://github.com/fedimint/fedimint/wiki/August-28,-2023
For fedimintd, there were a some flaky tests resolved. One test was flaky due to how the consensus was formed around block height. There was also progress announced for audit summary; the summary is not available via API.. Discussion occurred around optimizing the auditing code by compacting LN contracts for gateways and around looking into database encoding/decoding optimization. The database work has not been done yet but a background task was added to compact LN contracts; which is in draft PR status. There is a new UI Issue filed to add the this audit information to the Guardian dashboard. Another flaky test was fixed using environment variables to manage db migrations.
A few LN related PRs were made. One to enable to gateway to configure and register the number of route hints. Another was completed to allow LND to pay <1 sat invoices in tests. The sub-1 sat invoice payment involved updating the channel configuration since the LND default is 1 sat. A commit hash was pinned for the ldk-node dependency; this will be updated once a release is complete for LDK node.
Some extra documentation and explanations were added to Client code for serialization/deserialization and metdata, and outcomes for operations.
A PR was merged to prefix ecash notes with the fedimint id for better external consumption.
Progress has been made for TOR support. This PR for jsonrpsee will enable it to use TOR as the underlying communication layer. Once this upstream code lands, the RPC client can be updated in fedimint to enable TOR.
There is now a tagged v0.1.0-rc1 commit in the main fedimint repository. Moving forward there should be a "release" every 1 to 2 months with periodic backports for bug fixes. As time progresses a more stable release cadence will be established with long term support releases for fedimint. It is recommended that developer peg to this release and file any issue or bugs in the main fedimint repository. Any fedimints using this release tag should expect no backwards compatibility or database migration with the next release and will need to shutdown and restart any mint they have running to migrate.
Long term plan.
Nostimint- talk to your fedimintd using nostr. Post notes as a Fedimint.
Poolimint - Fedimint mining pool on stratum v2.
STAY HUMBLE AND STACK SATS.
There's what seems to be obscure bug in a branch of code I'm working on and I'm weirdly excited to hear the post mortem.
There are many more than these two.
First federated ecash mint was scrit, way before fedi ( https://raw.githubusercontent.com/scritcash/scrit-whitepaper/master/scrit-whitepaper.pdf ). There's ecash on eth called ZeroWei... Many mixing solutions are based on conversion to ecash notes, either temporary (Wasabi) or more long term (Tornado).
So I would say the meaning expanded, not became more specific.
It's specific when talking about money, but yes, not the first "ecash" system out there.
@naddr1qqxnzd3exvergvfhxycrvdfsqgs9ajvxw0lwe25ntjq52qtfygf9ngh3xf35u7y35rzn0h9k8meulvgrqsqqqa28xw0m9c
naddr1qqxnzd3exvergvfhxycrvdfsqgs9ajvxw0lwe25ntjq52qtfygf9ngh3xf35u7y35rzn0h9k8meulvgrqsqqqa28xw0m9c
Ecash now has specific meaning and context. There are currently two ecash implementations, Cashu and Fedimint. They allows users to obtain 1:1 bitcoin for privacy (via blinded signatures) preserving ecash notes.
The origins stem from David Chaum.
Ecash is a privacy and scaling solution for bitcoin.
🫂 🤝
Great idea.
Yea, their docs so far look the least complex. but we'll see. Maybe I'll do a write up.
What nodes should I package fedimintd for?
I think with the modularity, people will use them for a number of reasons.
There will almost certainly be a market for gambling to run atop fedimint. But now the poker chips ARE actually as good as money, and you always know they return to you eventually, or you keep a cut.
Or gaming companies that can embed ecash as data objects in games for players to find or win and immediately reissue for real money.
All redeemable on chain or over lightning with complete privacy.