Checks & permissions
Reserve backing, oracle health, contract lifecycle and administrative control.
Contract state
Read contract code, pause and transfer restrictions, supply controls and proxy implementation state.
Evidence source: Onchain RPC and contract reads.
Source: PDF p2 §4B; p4 §11
Reserve reconciliation
Compare totalSupply() with verified reserves, evaluate backing limits and PoR heartbeat, and validate authorized attestation signatures.
Evidence source: Token contract, PoR feed and authorized attestations.
Source: PDF p2 §4A
Oracle & NAV health
Require a non-zero NAV value and active oracle code. Check attestation freshness and flag out-of-bound NAV changes for manual review.
Evidence source: NAV oracle and timestamped observations.
Source: PDF p2 §4C
Sequencer health
Include sequencer health in the reconciliation context. Failure thresholds and recovery policy need explicit backend configuration.
Evidence source: Robinhood Chain infrastructure signals.
Source: PDF p2 §6; p4 §10
Asset lifecycle
Track ACTIVE, NAV_ADJUSTMENT, CORPORATE_ACTION, REDEMPTION_ONLY and RESTRICTED / PAUSED states.
Evidence source: Contract state and verified issuer lifecycle data.
Source: PDF p2 §4B
Permission audit
Monitor owners, admins, pause controls, minters, burners, compliance controllers and upgrade authorities.
Evidence source: Contract roles, governance and proxy records.
Source: PDF p2 §5
Reference baselines
The collateral ratio is verified reserves divided by circulating supply. Production reconciliation must normalize token and reserve units and decimals before comparing them. The PDF does not define a zero-supply calculation policy.
The strict inequalities are preserved. Equality at the freshness/deviation boundary and the exact per-asset heartbeat require an explicit policy.
| Baseline | Reference value | Interpretation |
|---|---|---|
| Backing ratio | ≥ 100% | Verified reserves divided by token supply. Units and decimals must be normalized. |
| Attestation age | < 60 min | Reference freshness baseline. Per-feed heartbeat policy is configured by the backend. |
| NAV deviation | < 2.0% | Reference step-change baseline. Exceeding safety boundaries requires manual review. |
Source: PDF p2 §4A and §4C; unit-normalization implementation requirement
Permission audit
The administration matrix in the PDF is illustrative. Its abbreviated addresses, multisig configuration and “reviewed” label are not claims about a deployed Comms asset.
| Role | What it controls |
|---|---|
| Owner / Admin | Multisignature or governance control |
| Pause control | Emergency freeze authority |
| Minter / Burner | Supply alteration permissions |
| Compliance admin | Blacklist and allowlist controllers |
| Upgrade authority | Proxy implementation control |
Source: PDF p2 §5