Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The Great Setup Ceremony Cleanup #482

Open
Kodylow opened this issue Aug 10, 2024 · 2 comments
Open

The Great Setup Ceremony Cleanup #482

Kodylow opened this issue Aug 10, 2024 · 2 comments
Assignees

Comments

@Kodylow
Copy link
Member

Kodylow commented Aug 10, 2024

There's a bunch of things that need to get improved for the setup ceremony to minimize the chances someone fucks it up. Many of these should be done before attempting DKG including:

  1. Network Confirmation: Setup Leader's network in the "Set Configuration" is the source of truth. Follower's network MUST match leader's before being allocated a "Pending" slot, should toast error otherwise.

  2. Bitcoin RPC Connection Test: Each guardian should ping to confirm the bitcoin configuration works, have had a couple people fail it.

  3. Wipe / Restart: Guardians should be able to hard reset during the setup ceremony through the UI if they mess up. Currently we do this by the Setup Leader initiating it, the followers detect it and opt it. However this forces everyone to restart. We should have a 2nd option (probably hidden or danger zone-y) where whatever guardian can force a hard reset if just one of them messes up during the process.

  4. TODO: check with @dpc for other ideas he had

@elsirion
Copy link
Contributor

Not sure if some are redundant or if I misunderstood some of your points, mentioning anyway:

  • Check both p2p and API connectivity between all guardians
  • I'd model the Bitcoin RPC connection test as a module params test: each module can sanity-check the params it will be given. That way other modules that may rely on other external sources of truth could check their availability.
    • Check that bitcoind is on the correct BTC network

This will likely need some changes on the fedimint/fedimint side too, should also have an issue there once we know what we want.

@Kodylow
Copy link
Member Author

Kodylow commented Aug 10, 2024

^ yeah I'm going to wait for this to get addressed fedimint-side before continuing here, all this would be better to address then only if not possible there I'll add backstops to the UI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants