Ethan Tuttle's avatar
Ethan Tuttle
ethantuttle@nobluecheckfor.me
npub1tmyc...el78
professional ehash shill shill pioneer
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
image Is this the appropriate response to very obvious scammers sending you a DM?
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
How do I get a telegram account without a phone number?!?
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
I want to pick three node in a boxes to bundle Fedimint and gatewayd for. 1. Start9 2. Umbrel 3. ???? Thoughts? Please share for viz
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
@jb55 can I borrow your brain to talk nostr event lifecycle to draft a state machine?
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
Who wants to talk about the lifecycle of a nostr event? Just a basic note. What would that state machine look like?
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
I’ve been talking non-stop Fedimint for days now and couldn’t be happier.
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
Nonce handling in Frost (or in general). Would it be better to pre-arrange nonces ahead of time or compute them prior to a signing round? Assume constant (minimum of threshold) communication between participants.
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
Anyone want to brain storm on nostimint? Planning some hours this week to sit down and think through how a Fedimint would handle nostr keys using frostr
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
You already have a lot of trust with your mining pool. Fedimint can derisk that trust with a Fedipool. Building it atop stratum v2 means more options for miners. This seems to be a critical vulnerability point for bitcoin
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
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.
Ethan Tuttle's avatar
Ethan Tuttle 2 years ago
2023-08-28 Fedimint Dev Call Summary For more details, please view the recording here: And find the list of PRs/Issues here: 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.