Devnet Docs
Internal reference for engineers working with the Sietch devnet stack.
Architecture
Sietch devnet runs the full stack: a validator set producing blocks via BFT consensus, ZK proof generation for every mint/transfer/burn, and on-chain SHPLONK/BN254 verification on the Ethereum bridge. The Ethereum L1 layer runs on Reth in dev mode with disk-backed MDBX storage, preserving the complete block history from genesis. The watcher process monitors L1 deposit events and submits mint proofs to validators.
This explorer indexes Sietch chain state and bridge contract events into Postgres, then serves it. It does not replace sietch-cli or node RPC -- it reads what they expose.
What is real
Devnet runs the same consensus, circuit constraints, and EVM verification contracts that will ship to mainnet. Proofs are generated and verified end-to-end -- nothing is mocked or faked. Block finality, state roots relayed to L1, and bridge deposit/withdrawal flows behave identically to a production deployment.
Both the Sietch chain and the Reth-backed L1 persist state from block 0 across restarts. Devnet differences from production: genesis pre-funded accounts, a small validator set, and no economic stake. This is a test environment -- nothing here implies a mainnet audit or financial guarantee.
Performance profile
Each Sietch RPC node in the current devnet runs on 200 MB RAM and 0.2 CPU. The testnet target is ~250 ms per block -- measured and reproduced across validator sets during internal testing.
Full benchmarks (throughput, proof latency, memory profiles) will be published alongside the first public codebase release. The numbers above reflect observed devnet behavior, not projections.
Whether to relax devnet constraints and target sub-400 ms blocks on the devnet environment is under internal discussion.
Services
This UI. Indexed devnet state: blocks, mempool, pool, bridge, watcher health.
Ethereum L1 block explorer backed by Reth's native ots_* APIs. Browse blocks, transactions, logs, and decoded calldata from genesis.
Contract verification. Verified sources make Otterscan decode function calls and events.
CLI quick reference
The primary way to interact with devnet wallets and the chain is sietch-cli. Key commands:
| Command | Purpose |
|---|---|
| wallet create --name alice | Create a new wallet with a random seed |
| wallet list | List wallets, balances, and note counts |
| deposit-eth --name alice --amount 1 | Deposit ETH into the shielded pool via L1 bridge |
| transfer --from alice --to bob --amount 0.5 | Private transfer inside the pool |
| withdraw-eth --name bob --amount 0.5 | Withdraw ETH back to L1 |
| status | Node connection, block height, state root |
Default RPC is http://127.0.0.1:11000 (validator-0). Pass --rpc-url to target a different validator.
Full CLI reference and deployment config live in the sietch-core/deploy/README.md and docs/rnd/TOOLING.md files inside the repository.