One engine for the official record

Read balances, supply, and transfers for each token from its own chain, at a fixed, finalized height with the block hash recorded.

• XRPL, Ethereum, Base, Solana, and Stellar adapters, each passing one shared contract test suite
• Every query in a snapshot is pinned to the same height; amounts stay exact integers
• Built for two RPC providers per chain, so a disagreement on finalized supply raises an alert instead of being trusted

Not yet: Provider cross-checks and monitoring run in the worker, which is planned.

Links each wallet to a verified holder, reconciles the record against on-chain supply, and keeps point-in-time records.

• Holders prove wallet ownership by signing, on every supported chain
• Wallets not yet linked to a holder are flagged as exceptions, never hidden
• A break between the record and the chain's supply is an alert, not a footnote

Not yet: The console views for the holder file are planned.

Checks every proposed transfer against legends, lockups, identity, accreditation, jurisdiction, holder limits, and freezes, and returns every violation at once.

• Rules are versioned; lifting a freeze is a new rule, never an edit
• The same engine runs for every chain; only enforcement differs
• Each result names the rule and the evidence behind it

Not yet: Screening status as a restriction arrives with the screening module.

Prepares the chain's own control transaction (authorize, freeze, unfreeze, clawback, pause) unsigned, for you to sign in your own custody.

• Uses native controls or audited standards only: XRPL MPT flags, ERC-3643, Token-2022 extensions, Stellar authorization
• Before submission, a signed payload is checked to be exactly the prepared transaction
• Each token shows what its chain can and cannot enforce

Not yet: The submit-and-track flow through the API is planned.

An append-only, hash-chained log of every change. Its head is anchored on the XRP Ledger so later alteration can be detected by anyone.

• Database rules make updates and deletes of records fail; corrections are new events
• Anchoring and verification are tested on the XRPL testnet
• Examiners and auditors can verify the chain themselves

Not yet: Signing anchors with a key held in AWS KMS is planned.

Checks each reserve report against a configurable eligible-asset list and maturity limits, and computes coverage across every chain the coin is on.

• Circulating supply excludes unissued treasury balances
• Fractions of a cent round against you, so coverage is never overstated
• Alerts on a shortfall and on reserve reports that go stale

Not yet: Uploading reserve reports through the console and API is planned.

Wallet sanctions and risk screening through a licensed vendor, with hits turned into blocked addresses.

• A screening hit can open a freeze workflow on any chain that supports one
• Results and evidence go to the audit trail

Not yet: The screening vendor has not been chosen yet.

Rule-pack report drafts and examiner exports tied to an exact block. Formats are configuration, because most of the rules are not final.

• Examiner CSV with the height and block hash in its header
• Tokenized-issue report draft and monthly reserve disclosure draft
• Always marked draft until you approve them; filing stays with you

Not yet: JSON and PDF exports to retained storage are planned.

Versioned written procedures with staff attestations, kept alongside the audit trail as evidence.

• Each version is kept; attestations name the person and the version they read