For implementers · edition 0.6.1

Recode ZooBC from its specification.

ZooBC is a proof-of-participation blockchain: registered nodes, drawn by lot from the previous block's seed, make its blocks without mining.

zoobc.dev offers everything you need to build a compatible ZooBC node in the language you choose: the specification, about 2,500 exact tests, and a sandbox chain to connect to.

  • 36chapters
  • 2,508test cases
  • 2,154run in your browser
  • 4conformance levels

Read the specification

36 chapters, from byte order and hashes to blocks, the spine chain, the wire protocol and the HTTP API. Every mechanism has the same eight headings, ending in a vector and the defects to match.

Open the specification

Test your code

2,508 cases with exact inputs and the exact expected output or refusal. Compute each one in the browser, paste what your implementation produced, and see the first byte that differs.

Browse the tests

Join the discussion

Questions about the specification, a statement that does not match the network, proposals: everything is discussed on the ZooBC forum, zoobc.pro.

Go to zoobc.pro

The two chains

The TestNet and the DevNet relaunch from genesis on 0.6.1. A chain is identified by its genesis hash: there is no network byte.

The live hashes follow at launch

The launch sets the genesis timestamp, and with it the genesis hash, the block-0 id and the spine genesis hash: each chain announces its live identity on its launch day, on GET /api/v1/node/info (33 §1). Until then, these are the identities of the genesis files as shipped (timestamp 1,793,509,027), which 06 §3 and 33 §1 use to check a genesis builder.

TestNet zoobc-test / zoobc-spine-test

Genesis hash · shipped file
3A2897E7C5AD6143429BAB33A92D14D11FFD6FC281F2B62A6FD6B49C183B863D
Spine genesis hash · shipped file
7CD929C4D52D9C9455ED179D24A65F90ECBF3D1A3E1214A19611635791B3545C
Block-0 id · shipped file
4,855,352,938,787,711,034

DevNet zoobc-dev / zoobc-spine-dev

Genesis hash · shipped file
A37B1692EC47C7B17A7F9CB4C13CC8A73A1D5E843565A5733B9DA2A544DF99F8
Spine genesis hash · shipped file
5876B908090A5BCA4BD735DD96A559FD8FBBE64C1419C053DE227BE3CACCEEF3
Block-0 id · shipped file
−5,636,457,327,242,085,469

How to use zoobc.dev

  1. Read a mechanism. Start with chapters 01–07, the foundation. Each mechanism states its purpose, inputs, output and how to compute it.
  2. Run its vectors. Under every Vector heading, the section's test cases open in place: compute them, then check your own output byte by byte.
  3. Claim a level. L1, L2, L3, L4: each level has a checklist in chapter 33. Pass every check of a level to claim it.

The sandbox chain for implementers is coming soon.