Duniter Block information

another query i have. is there anywhere i can find details about the duniter blockchain, and whether there will be much changes with v1 going to v2… in the relation the points below…
or if this points can be expressed here, suits me.

few points would love clarity around are:

  • what is the time duration between blocks.
  • what is the max size of a block, and how much on average transactions are there in each block (if that’s available).
  • what hashing algorithm duniter uses.

any other useful information around these areas greatly appreciated.
thanks so much.

1 Like

Duniter v1 blockchain protocol (DUBP) is defined here.

Block duration is between blocks is 5 minutes on average. The 5 minutes target is reached by tweaking global and individual PoW difficulties.

In Duniter V2, it’s 6 seconds. Yes it’s short, but it’s the standard in the Substrate ecosystem. It allows more throughput, smaller blocks, more reliability (some blocks can be skipped due to network or smith failure without causing too much damage), and more security (the consensus method relies on a high number of blocks in each session for security).

Max size of a V1 block is max{500, ceil(1.1 * average_block_size)}, average block size being computed on the current frame (the X latest blocks). Size is the number of lines in some given fields of the block (each transaction takes multiple lines, a certification is a line, etc.).

There is another limit of 40 transactions per block. (V1)

In Duniter V2, we call transaction not only money transfers, but any data that can be put in a block. We fix a maximal “cost” that a block can contain (e.g. 2,000 billions), and benchmark each transaction type to assign a cost to it (e.g. certification costs 1 million (random number for the example)), such that the cost is proportional to the amount of time needed to execute the transaction on some reference hardware (Raspberry Pi 4). This way a block has bounded size and execution time.

I don’t know what is the maximum number of transactions per hour, but it’s largely enough. We can know this once the benchmarks are implemented.

Duniter V1 uses SHA256.


thanks so much, again, tuxmain, for the thorough response. really appreciate it.
have noted it all… and will impart the knowledge to anyone interested.