What a Bank Should Evaluate Before Adopting an On-Chain Real Settlement Layer

A bank evaluating an on-chain real as a settlement layer is not choosing a token, it is choosing a dependency for how value is held and moved behind its products. The useful evaluation is a due-diligence checklist across a few concrete dimensions. For BRLV, issued by Crown, each dimension maps to something a bank can verify rather than take on trust. This is the checklist, dimension by dimension.

Backing and its verification

The first question is what stands behind each unit and how it is checked. BRLV is backed 100% by Brazilian federal government bonds (Letras Financeiras do Tesouro, or Tesouro Selic), registered in the SELIC system and custodied by institutions authorized by the Central Bank of Brazil. Verification runs on three independent tracks: reserves attested daily by an independent third party and published on a public transparency page; smart contracts audited periodically by an independent security firm; and financial statements audited by an independent accounting firm. A bank should confirm each track exists and is independent of the issuer, the same reserve-composition scrutiny a treasury applies in non-USD stablecoins for corporate treasury.

Legal structure and insolvency

For a bank, the failure case is not optional to model. The reserves behind BRLV sit in a bankruptcy-remote structure, segregated from the issuer’s own estate, with an independent collateral agent that executes holders’ access to the reserves if the issuer becomes insolvent. A bank should evaluate whether that segregation is contractually real and whether the collateral agent’s mandate survives an insolvency, because that is what separates a claim against a company from access to segregated assets.

Regulatory standing

The bank inherits regulatory context from the provider. Crown operates under Brazil’s virtual asset framework (Law 14.478/2022) and the Central Bank of Brazil’s rules, and has filed for authorization as a virtual asset service provider, operating meanwhile under the transition regime that currently applies to all such providers. A bank should confirm the provider’s status, its reporting obligations, and how regulatory change would be absorbed by the provider rather than by the bank.

Integration surface and custody

An on-chain settlement layer only reduces work if it integrates cleanly. Crown’s platform is accessible by API, documented publicly, covering accounts and sub-accounts under a partner model, wallet creation and transfers, Pix deposits and withdrawals, conversion orders, balance and full transaction history, and webhooks for each event. Custody runs on institutional infrastructure using multi-party computation, with wallets segregated per client. A bank should test whether this collapses several per-function bank integrations into one layer, the same shift that changes settlement timing in real-time BRL settlement for ERPs.

Compliance and residual risk

Finally, the bank should evaluate the provider’s own compliance posture and the residual risks it cannot remove. Crown runs KYC and KYB with biometric and multi-provider identity verification, sanctions and politically-exposed-person screening, beneficial-owner mapping, source-of-funds evaluation and on-chain transaction monitoring. None of this removes the documented risks of any virtual asset, which a counterparty should size on its own terms, as laid out in eligibility and redemption risks for a foreign institution. The evaluation is complete when the bank can state, from evidence, how each dimension behaves under stress.