Contract roles and bindings - Nullark

One runtime supplies every address in the call path. Keep that object intact instead of selecting contracts one by one. Use Current deployment for the exact pinned values.

Contract responsibilities

Role	Responsibility	Must match
Pool	Holds ETH, inserts bundle commitments, tracks roots and nullifiers, applies fees, and pays withdrawals	Chain, deployment block, accounting, and verifier routes
Deposit verifier	Checks the six-input deposit relation	Key hash, bytecode hash, setup, and input order
Withdrawal verifier	Checks the nine-input selected-child withdrawal relation	Key hash, bytecode hash, setup, and input order
Deposit adapter	Binds the pool to the deposit verifier interface	Pool, verifier, and adapter bytecode
Withdrawal adapter	Binds the pool to the withdrawal verifier interface	Pool, verifier, and adapter bytecode
Poseidon2 and Poseidon6	Provide the field hashes used by tree and bundle relations	Address, bytecode, and field semantics
Fee controller	Manages the active fee within the contract’s hard maximum	Controller address and live fee state

Deposit path

The pool requires the transaction value to equal the proof-bound amount. It also binds the commitment, chain, pool, deposit context, and encrypted recovery payload hash.

Withdrawal path

The proof binds the destination, gross amount, fee, chain, pool, proof context, and encrypted payload. An unspent sibling already belongs to the deposited bundle, so a withdrawal creates no new commitment.

Code and accounting

Runtime validation combines addresses with expected code and verifier identities, then uses live reads for current fee state. The pool’s ETH and accounting must cover every allowed exit without counting accrued fees twice. UI balances and transaction receipts are views of that state, not alternate ledgers.