Skip to documentation
Reality-grade bankingDocumentationOpen implementation
Documentation contents

Start

Trust you can inspect

Know what you own, where value is held, what authorizes movement, and how to verify or recover the result.

Reviewed 2026-10-25 · SDK 129.0.0Read Markdown ↗

Know what you own

Reality-grade banking keeps identity, value, ownership and recorded operations connected to their actual sources. You can inspect the Original, see the supported rights, trace the relevant history and retain the evidence beyond a screen or session. The proof-native economy is the economic system; reality-grade banking is the standard for interacting with it; Receiz supplies the underlying primitives.

A financial relationship you can follow
  1. SourceWhat establishes the value and rights.
  2. AuthorityWho can approve the exact movement.
  3. ResultWhat was actually accepted.
  4. ContinuityWhat you retain and can inspect later.

Know where value is held

The account should answer the question precisely
QuestionWhere to look
What is available in my account?The admitted Reserve and Settlement sources and their supported total.
What is committed elsewhere?Actual Note funding, backing commitments and their original results.
What do my investments represent?Exact shares, offered rights, cost basis and recorded trades.
What is separately protected?The Vault private original, contained sources and separate custody.
What have I received but not credited?Received Notes, retained separately until confirmed account credit.

Valuation, backing and available exchange capacity have their own evidence. The manual explains each so a useful dollar presentation does not obscure the underlying units, ownership or financial state.

Stay in control of movement

Read access and financial approval are separate. Before value moves, inspect the actual source, recipient, amount, fee and supported terms. Your agent can explain context and propose action while the native execution contract retains its own authority. A public identity, shared proof or conversation cannot grant another person the private right to spend.

Verify the result yourself

Use the supported original and matching independent reader to inspect the evidence that an operation carries. The enclosing artifact verifies before its fields are projected. Public evidence can be checked without handing over private keys or a Vault bearer original. A record proves what it actually contains at its coordinate; current custody or another action needs its own accepted source.

  1. Inspect the exact event

    Match intended participants, amount, asset and operation reference.

  2. Open the supported proof

    Read the complete original under the matching verifier/resources.

  3. Retain the evidence

    Save the source and result needed for independent later inspection.

Keep a recovery path

Save identity and private proof backups separately. Keep current Vault/Note originals and resolve pending custody before retiring a device. If a response is interrupted, recover the same saved attempt. A timeout leaves an unknown result; it does not erase a committed payment. The operating guides name the matching recovery control and the evidence needed to resolve it, including partial cases such as card credit completed before a recipient payment.

Assess the actual implementation

The standard is inspectable: source, schemas, receiving requirements, refusal tests and the independent assessment procedure are published. An assessment names the exact build, capability, roots, rail, runtime and device. Apply the same criteria to any implementation. Local checks and deployed financial/device evidence each retain their actual scope. Confidence grows from being able to inspect the stated operation, its accepted evidence and its recovery behavior.

Implementation sources

Inspect the exact path.

Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.