contracts(5): contracts and keys

Addresses, roles and the keys behind them. DarkRoom and its verifier have their source verified on Sourcify; the point table and Poseidon6 are generated bytecode, rebuilt from the files in the repository.

Addresses

contract	address
DarkRoom	0x642FDdc64Ad99C83D97dE3a79377Ca3Ff7CF0479
Groth16Verifier, its point table, Poseidon6	deployed with DarkRoom; read their addresses from its verifier() and poseidon6()
DarkRoom, earlier (v2)	0xfb70Dd59B53a9039981c8E8DcEB23FCe4560F4c4: PLONK proofs made on the CPU, batches up to #5,970,995. Takes no new orders; balances in it stay withdrawable.
stake vault	0x5b210FEC287311198a44a6eDB6E283f8a87757EA
USDG	0x5fc5360D…d168

Roles

owner: the machine wallet. Lists markets, sets the fee (cap 10 bps, 24 h delay), changes the room (24 h delay), binds the stake vault once, pauses new seals. Cannot touch a balance.
room: the operator key. Posts room keys, settles with a proof, records Pons marks, flushes and converts fees. Cannot touch a balance except through a proven fill.
anyone: deposit, withdraw, seal, cancel, mark, flush, contest.

The room process

outbound only

room process ──> chain RPC        logs, settle, keys
             ──> drand relays     rounds, each verified against the quicknet key
             ──> this site        HMAC-signed heartbeat every 10 s
             (no listening socket; the service may not bind a port)

One systemd service on one machine, with memory and CPU caps. Room keys live in a private directory on that machine and are wiped once spent. Losing them only expires the open batches.

/ search · [ ] previous and next page