Running a Fedimint
This guide has been developed as a community project and is a live document. We would appreciate any feedback you may have and you can submit edits, corrections and pull requests through the link at the bottom of each page.
A fedimint requires a set of trusted guardians to establish the federation, hold the keys to the bitcoin multisig and to custody the hardware that runs the fedimint nodes.
These guardians will play a pivotal role in securing funds and running the fedimint infrastructure on behalf of the community. Therefore it is envisaged that these guardians will be part of a "second party trust" network with the user.
Second party trust refers to a situation where there is a direct existing trust relationship between the individual committing funds to the fedimint and the guardians of the fedimint.
Some examples of this second party trust relationship could be:
- The guardian is a technically literate member of your family.
- The guardians are members of your broad friendship network.
- The guardians are respected members of a local community with high degree of social capital that they stand to lose through misdeeds.
- The guardians are known institutions with a history of honest service.
This is a broad membership base of society and as such there is likely to be a very wide range of practical use cases and varied implementation patterns for fedimints.
Therefore, it is not the scope of the protocol to define how or why fedimints are deployed in practice, and no such specific templates are given, due to the variation in need and requirements of the community.
Instead we expect to see a world where there a wide range (millions of individual fedimints) deployed across the full spectrum of custody.
To support this approach Fedimint provides the protocol with minimal tools to run, monitor and manage operations.
A set of APIs is to be used to support 3rd party applications and services. This will allow other projects and businesses to extend these services and meet specific user needs, allowing for innovation in a competitive ecosystem outside of the core protocol.
Whilst the specific deployment, configuration and tools used to manage a fedimint may differ there are some commonalities that are likely to be familiar across fedimint deployments.
- Fedimints will utilize a number of fedimint nodes, operated by "guardians".
- Fedimint nodes will be connected via public networks and may utilize different anonymous networking protocols or overlay networks for speed, simplicity or security.
- All fedimint nodes are modular in design.
- Any particular node may run both core modules (eCash, multisig) as well as 3rd party modules.
- The specific configuration and module install base of a fedimint node will be driven by the needs of the fedimint community.
- Fedimint nodes will come to consensus on installed modules.
Fedimint guardians, as the custodians of the fedimint nodes, will have responsibility for backing up any private keys and ensuring the physical (or virtual) custody of the hardware on behalf of the community.
Each fedimint node would be lightweight in practice, similar to a pruned bitcoin node. There will however, be a linear growth in the storage requirement which whilst small at first will grow as more eCash is spent and redeemed.
Whilst the actual growth will need to be tested in a real life enviornment at a high usage of ~1 transaction per second of 10 tokens per transaction would result in ~10GB a year of storage growth.
The form factor of fedimint nodes could be any combination from a number of options from laptops, towers, smartphones, mobile phones, single board systems or remotely operated computers in the cloud - as long as the system can run the bitcoind and fedimintd daemons and connect to the internet.
The deployment of fedimint, currently utilizes a simple UI which allows a user to view their private key and build a federation by adding additional "peer" private keys from the other federation guardians.
This allows the fedimint scripts to collect the appropriate information before automating the remainder of the deployment.
This in turn is then to be made accessible via an API to allow additional 3rd party services to innovate on the federation setup and management process.
To be updated with screenshots as the UI is pushed to the project.