ONCHAIN STATE. OFFCHAIN EVIDENCE. ONE CLEAR VIEW.Frontend preview
Documentation /

Status model & rules

Three operational outcomes, with explicit policy boundaries.

Status definitions

StatusMeaning
SAFENo configured blocking or warning conditions across reserves, oracles or permissions. Not a guarantee of safety or investment quality.
WARNINGNon-fatal staleness or operational delay requires caution.
BLOCKActive mismatch, paused or restricted state, or severe deficit requires rejection of the asset interaction.

Source: PDF p1 §1

The two specified matrix combinations

These are the only complete combinations supplied by the document. Do not infer a full production decision table from them.

Supply vs reservesOracleContractSequencerStatus
Synced (CR ≥ 100%)Fresh (< heartbeat)Active / unpausedHealthySAFE
Synced (CR ≥ 100%)Stale (> heartbeat)Active / unpausedHealthyWARNING

Source: PDF p2 §6

Lifecycle defaults

StateDescriptionDefault
ACTIVENormal minting, burning and secondary-market transfers.SAFE
NAV_ADJUSTMENTTemporary transfer or mint pause during NAV recalibration.WARNING
CORPORATE_ACTIONDividends, stock splits or issuer rebalancing in progress.WARNING
REDEMPTION_ONLYPrimary minting closed; redemption by burning remains active.WARNING
RESTRICTED / PAUSEDPause toggle active, transfer hooks failing or minting manually frozen.BLOCK

Source: PDF p2 §4B

Unresolved backend policy

These are implementation decisions still required, not rules already running in the frontend. An unavailable service is shown as NOT CHECKED, not translated into SAFE, WARNING or BLOCK.

  • Exact equality at heartbeat, 60-minute and 2.0% thresholds is not specified.
  • NAV deviation is marked for manual review without a prescribed status severity.
  • The full risk matrix, combined-rule precedence and sequencer failure policy are not defined.
  • NAV_ADJUSTMENT can include a temporary pause and still defaults to WARNING; it must not be conflated with RESTRICTED / PAUSED.
  • Accepted assets, authorized attestors, offchain evidence sources and production operating policies require configuration and verification.

Source: Document gaps in PDF p2 §§4–6; frontend fail-closed boundary