Skip to main content

QA transparency

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

QA pre-flight (bytecode check)

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)

QA gate

Automated QA already Allow/Rejects most deploys. Items here are Unsure — reviewers given the role vote Allow or Reject based on the asset (name, symbol, purpose, bytecode) before it can enter a block. RPC spec.

Reference

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.
  • -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.