2023-08-28 Fedimint Dev Call Summary

Habla

Habla

Read, Highlight, Write, Bookmark, Earn

For more details, please view the recording here:

BitcoinTV.com

20230828 - Fedimint Dev Call

A repository of educational video content for the Bitcoin community, without distractions like advertising, altcoins, or third-party trackers.

And find the list of PRs/Issues here:

GitHub

August 28, 2023

Federated E-Cash Mint. Contribute to fedimint/fedimint development by creating an account on GitHub.

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.

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.

@naddr1qqxnzd3exvergvfhxycrvdfsqgs9ajvxw0lwe25ntjq52qtfygf9ngh3xf35u7y35rzn0h9k8meulvgrqsqqqa28xw0m9c

naddr1qqxnzd3exvergvfhxycrvdfsqgs9ajvxw0lwe25ntjq52qtfygf9ngh3xf35u7y35rzn0h9k8meulvgrqsqqqa28xw0m9c

skiff.com

Skiff - Private, encrypted, secure email - 10 GB free

Skiff Mail privacy-first, end-to-end encrypted product home, with Mail, Calendar, Pages, and Drive overview.

What nodes should I package fedimintd for?

Talking to my co-worker XMR bro, wicked smart guy. Tell him about fedimint. "Oh, it has modules." "Yea, it's transaction in and out at the core protocol" "So it could do swaps for Monero" Got me thinking a bit. Plebs want sats. Many plebs want more sats. Monero bros wants more XMR. XMR is 'easier' to mine and can be done on CPU by design (last I understood). Plebs have CPUs more than they have ASICs. Plebs min XMR, bring to a fedimint and swap for ecash. Monero bros come to fedimint and swap sats for eash. Plebs get sats. Monero bros get XMR. Monero gets more TX volume and mining. Arbitrage opportunities abound. Is this shitcoining? What if it unlocks some pleb level arbitrage with just a Fedmint module to swap XMR for ecash? Is the what it's like working on a permissionless protocol?

Start9

Running StartOS on Mac M1/M2

Below is a quick and easy guide for installing StartOS onto your Apple Silicon computer using UTM virtualization. UTM employs Apple's Hypervisor vi...

Well this is pretty neat...

@🌬⚡️Agron is there an ecash spec somewhere? Seems like having published specs on handling ecash tokens would be helpful

RPOW - Reusable Proofs of Work

"Using RPOW tokens for email would have advantages, as people could then reuse tokens from incoming email in outgoing email. Spammers will have no such advantages since almost all of their email is outgoing. Reuse allows the cost of the POW token to be much higher since most people won't have to generate them, making the system more effective as an anti spam measure." ecash can be RPOW.

Gist

Chaumian ecash designs, notes

Chaumian ecash designs, notes. GitHub Gist: instantly share code, notes, and snippets.

Interesting read on ecash. Good linked references as well.

Fedimint allows you to spread risk of rug pull across multiple entities. In addition, it can provide you privacy. Not all custodial solutions can say the same. note17q92hkm88jhguz3hllhn3z0usv0npf3nnufes7n8xpnup4r2ynrscqwglx

It seems that there will be a market that could develop around "L1 insurance". Where a large capital allocator collects on "insurance" and promises you exit support during times of congestion/high fees where an average user cannot afford to exit from one of the aforementioned "bitcoin banks". Inspired thought by:

Delving Bitcoin

Thoughts on scaling and consensus changes (2023)

Back in June, AJ published an underread blogpost about scaling. I’ll do a hasty job of paraphrasing the post – which you should read in full �...

@Logan is the real TFTC Logan. He confirmed on air.