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

Protocol integration

Use an operational pre-check without mistaking it for investment advice.

Before accepting an RWA interaction

The source blueprint demonstrates an onchain guard or offchain middleware pre-check. It does not identify a deployed reconciler contract. No deployment address should be invented.

  • BLOCK: reject the interaction.
  • WARNING: apply a conservative policy or require confirmation.
  • SAFE: continue only within the application’s configured checks and other risk controls.

Source: PDF p3 §8

Fail-closed application handling

This illustrative integration pattern adds an explicit transport/unknown-status boundary. It is documentation, not an API connected to this preview.

Documentation example
type Status = 'SAFE' | 'WARNING' | 'BLOCK';

function interactionPolicy(status: Status) {
  switch (status) {
    case 'BLOCK': return 'reject';
    case 'WARNING': return 'require_confirmation';
    case 'SAFE': return 'continue_with_other_controls';
    default: throw new Error('No verified operational status');
  }
}

// If fetching, validation or freshness checks fail,
// do not call this with a fabricated SAFE result.

Source: PDF p3 §8; additional defensive integration guidance

Audience

Wallets, DeFi protocols, issuers and users can consume operational reconciliation. Comms is not itself a lending protocol, brokerage, trading venue or issuer.

Source: PDF p1 §1; p4 §12