AgoraSeal

WIP paused on 2026-10-08 at the user's request. See the English handoff for the exact implementation state, validation, PLONK memory-pressure interruption and prerequisites for resuming.

On 2026-10-18 the maintainer authorized the bounded vote-context encoder synchronization for CellScript #51. That maintenance updates source/template/lock, the compiler pin and documentation; the broader application, proving and deployment work remains paused.

ZK voting settlement and treasury execution on CKB, with application policies implemented in CellScript. AgoraSeal explores the ZK direction independently of the Nervos treasury team's optimistic tally design.

Development status: not production-ready. The executable starting point is a CellScript vote Type Script, treasury payment Lock and bounded native replay of authenticated CKB block transaction commitments and per-deposit voting semantics. The SP1 guest/prover and canonical public statement are implemented; execution and proof evidence is recorded separately in the ZK boundary. The exact SP1/CellScript boundary, node-backed voting eligibility, proposal/escrow creation and release admission are tracked in the production ledger. Native replay is not a ZK proof or a consensus validator.

Design

Each proposal fixes its vote program, chain domain, window, quorum, recipient and requested amount. DAO deposit outpoints identify voting rights. The latest ballot for a deposit wins; withdrawing that deposit invalidates its ballot. Deposits must predate the proposal, enforced by the vote Type Script. The prover must process every transaction in the exact anchored window, including spends.

The ZK guest seals the tally. CellScript settlement binds that result to the proposal and CKB chain context. A separate treasury policy enforces one-time payment to the committed recipient. Funds can come from ordinary pre-funded Cells; integration with secondary issuance requires a separately activated CKB treasury provider. See the protocol.

This is proof-backed counting over public ballots; ballot secrecy is not claimed.

Development

The sibling ../CellScript checkout (or CELLSCRIPT_ROOT) must be at 602795b3f8a095860eeb544518778495a7e55976. The gate builds the compiler from that checkout, compiles the actual .cell, verifies its ELF/metadata/source binding, and executes it in CKB-VM.

./scripts/gate.sh dev
./scripts/gate.sh ci
cargo run --locked -p agoraseal-cli -- replay PROPOSAL_SCRIPT_HASH START_HASH END_HASH block0.bin block1.bin

The native gate checks the ZK host but does not generate a proof. The separate ./scripts/zk.sh test-guest and ./scripts/zk.sh prove-core commands require the pinned guest toolchain described in zk/README.md.

Block files are canonical CKB Molecule blocks in chain order. Hash arguments are 32-byte hexadecimal values. The command checks the full transaction roots (including witnesses), proposal inclusion, contiguous range and tally. Its JSON output is labeled native replay and must not be accepted as settlement proof.

./scripts/gate.sh production intentionally fails until all production layers have their own executable evidence. The full goal includes deployable artifacts, wallet/prover tooling, adversarial runtime tests, reproducible costs and an operational runbook; a green native gate cannot satisfy it.

The executable application policy is contracts/treasury/treasury.cell. Its current VM evidence covers exact payment, authenticated settlement Type identity, quorum, fee bounds and 15 substitution failures. The settlement fixture uses an artificial Type Script: this is component evidence, not a verified ZK tally or a deployable treasury. See the treasury boundary and comparison with ckb-vote-poc.

The actual vote policy also compiles and executes in CKB-VM, including its pinned generic context adapter. DAO eligibility, owner authorisation, weight and snapshot comparison are all in CellScript. See its ABI, bounds and evidence. The Rust reference is not substituted for this policy. Complete ZK settlement remains pending.

Rust is used for proof/crypto infrastructure, clients and test models. reference/vote is a Rust eligibility baseline only, not the application's authoritative voting implementation.