Skip to main content
ROBINHOOD MAINNET 4663// Association Set Policy (ASP)

Association Set Policy (v1)

Deterministic, mechanical inclusion rules for clean withdrawal sets on Robinhood Chain. Zero human discretion, open automated publishing tooling, and anti-censorship guarantees.

Mechanical Inclusion/Zero Discretion/Open Source Tooling
Core Policy Rules
§1Every Onchain Label Included
§2Mechanical Script Execution
§3Anti-Censorship Gated Role
§4Zero Human Discretion
§1

The Inclusion Rule

The association set contains every label ever deposited onchain plus the genesis sentinel, nothing more, nothing less. No human decides inclusion or exclusion. Publication is strictly mechanical: scripts/publish-asp.mjs rebuilds the Merkle tree from on-chain Deposited events and submits updateRoot to the 0xbow Entrypoint proxy.

node scripts/publish-asp.mjs --network mainnet
§2

Why the Updater Role is Gated

updateRoot on the 0xbow Entrypoint proxy requires the designated postman role. An open, unpermissioned updateRoot would allow malicious actors to publish fraudulent roots that omit legitimate user labels, effectively stranding withdrawals. Open deterministic publication tooling paired with a dedicated operational updater key represents the minimal safe architecture: the rule is public and mathematically verifiable, while the key prevents censorship.

§3

Current Association Sets

Robinhood Chain Mainnet (4663)CANONICAL LIVE

Published from live pool deposits with deterministic root updates under the rule above. Genesis sentinel CID is permanently pinned to IPFS.

Genesis IPFS CID:QmVtkNm5Ro2F1oVBdP17TxcAcafXtMoG8rYPnu7S8kXJxV
Testnet 46630 (Historic Reference Only)

Sentinel-only genesis retained strictly for regression testing and historic telemetry benchmarks.

§4

Rule Mutations

Any rule change requires a published policy revision before code changes are deployed. Code never leads policy. Refer to ratified Owner Decisions for ratification histories.

Ready to verify association sets on-chain?Launch Veil Terminal