Duniter v2 is a rewrite of Duniter v1 in the substrate framework with the goal of migrating the Ğ1 currency. It is now under development and needs testing. You will find here user documentation extracted from Duniter git repository as well as general explanation.
- git repository https://git.duniter.org/nodes/rust/duniter-v2s/
- development forum section https://forum.duniter.org/c/dev/duniter-v2s/
- protocol forum section https://forum.duniter.org/c/protocols/g1v2proto/
- support forum section https://forum.duniter.org/c/support/duniter-v2/83
In this section you will find everything needed to start contributing to the network. If you feel like there is something missing, please ask on the forum support section, this helps improving the tutorials and is by itself a valuable contribution!
Run a mirror node🔗
A mirror node is a node the user connects to through the RPC API. Running a Duniter mirror node is useful for the network's redundancy, it allows to share the load between different servers and increase resilience to failures. This is also a good practice step before forging blocks.
- run a mirror node
- configure your node (docker) (external)
- inspect your node in polkadotjs app
- run an indexer
A mirror node in archive mode is needed to run an indexer indexer.
Start forging blocks🔗
In Duniter vocabulary "smith" means someone allowed to add blocks to the blockchain. Contrary to Duniter v1, smith is mainly a technical role, the goverance being done on chain. The competences needed to become smith are less technical than human. A smith should:
- follow good security practices for his keys and node
- be able to react quickly in case of failure (or go-offline)
- contribute to the smith web of trust by inviting other smith
Here are the steps to become smith:
- run a smith node (a node enabled to forge blocks)
- become smith (be member of the smith web of trust)
Whether you contribute to an existing end client like Ğcli or an Indexer or create a new client from scratch, you might be interested to read:
- generated documentation for calls, events and errors
- general documentation about the RPC API (TODO)
- graphql schema of the duniter-squid indexer (TODO)
Don't hesitate to reach up in the "clients" forum section https://forum.duniter.org/c/clients/16.