Use one complete runtime - Nullark

Nullark calls its complete configuration a runtime. It packages the chain ID, RPC, pool, deployment block, verifiers, adapters, bytecode hashes, fee policy, selectors, proving hashes, and proof-input order. Use it as a whole. Do not assemble those values one by one.

Browser

Open Nullark. The browser loads the selected runtime and checks its chain, contracts, fee, and proving files together. If any part disagrees, the flow stops. Use Current runtime when you need the exact published values.

Public integration status

Use the browser for the full Nullark app or install the TypeScript SDK in your own app. The CLI remains a workspace tool; there is no public CLI binary yet. If you are reviewing or building from source, use the repository’s complete runtime object. Do not reconstruct one from addresses copied across pages.

Values that travel together

Before any value-moving action, these values must come from the same runtime:

Chain ID and RPC response
Pool and deployment block
Deposit and withdrawal verifiers
Verifier adapter and expected bytecode hashes
Withdrawal selector and fee policy
Manifest, setup record, WASM, and zkey identities
Groth16 public-input order
Recovery-note chain, pool, runtime, and template binding

Mismatch behavior

Mismatch	Required behavior
RPC chain differs	Reject reads and submission
Pool or verifier differs	Reject runtime and proof binding
Recovery export belongs elsewhere	Reject import
Artifact hash or input order differs	Reject proof generation
Fee state changed	Regenerate proof
Unknown runtime	Reject selection

On any mismatch, Nullark stops before fallback, weaker proving files, or replacement submission.