QA transparency

Live pool config, pending queue, and rule registry from public RPC — same methods the explorer uses elsewhere. Anyone can Allow or Reject Unsure deploys in the public QA vote below.

QA gate rules · QA pre-flight (bytecode check)

Auto-refresh every 45s

Rule registry

From boing_getQaRegistry. Repo JSON is a comparison baseline; live networks may differ.

Canonical QA config (docs) →qa_registry.canonical.json (raw) →qa_pool_config.canonical.json (raw) →RPC-API-SPEC →

Live governance pool (testnet)

Public vote

Automated QA already Allow/Rejects most deploys. Items here are Unsure — public voting: connect Boing Express to Allow or Reject based on the asset (name, symbol, purpose, bytecode) before it can enter a block. This explorer does not pay voters. Counted Allow/Reject votes earn on-chain treasury rewards (typically 1 BOING) when a signed QaPoolVote is included. Abstain does not pay by default. RPC spec.

Reference

Allow / Reject / Unsure — automated path; Unsure may yield pool entry (-32051).
QA gate rules — every Allow / Reject / Unsure rule, plus PDF.
QA pre-flight — boing_qaCheck dry run.
QA policy · RPC error codes

QA RPC error code list

-32050Deployment rejected by protocol QA (rule_id + message in response).
-32051Unsure — referred to the governance QA pool; includes pending tx_hash.
-32052No pending pool item for that transaction hash.
-32053Voter is not a governance QA administrator (node still has open voting off).
-32054QA pool disabled by governance (e.g. no admins / zero capacity).
-32055Global pool capacity reached.
-32056Per-deployer pending cap reached.
-32057Operator RPC auth — vote/apply require X-Boing-Operator when the node sets BOING_OPERATOR_RPC_TOKEN.