How REAL fits together
How REAL's three layers coordinate around a shared financial record.
A shared financial record
REAL's design keeps the authoritative financial record on its dedicated chain. Asset terms, identity checks, settlement events, risk assessments, and validation history can refer to the same asset, allowing services to coordinate throughout its lifecycle. Connections to other networks extend access while REAL retains its own network policy and authoritative state.
Shared records make actions traceable. Contracts apply configured rules; the parties submitting external information remain responsible for its accuracy.
Follow an asset
- Network — Real Chain executes transactions and records shared state.
- Asset — Tokenization Engine applies token, identity, and compliance rules.
- Accountability — Business Validators perform assigned services backed by stake and enforcement.
The layers share records, not interchangeable authority. The example below follows one bond across them; BV assignments and insurance apply only where explicitly configured. Consider an issuer representing a bond as a permissioned token. The bond's terms establish the rights and obligations. REAL's systems provide different parts of the infrastructure used to record and operate that asset.
1. Configure the asset token
The issuer sets up a token suite: a group of contracts covering the token, identity checks, and transfer rules. Authorized participants configure who can operate the suite and the eligibility requirements that apply to investors.
2. Establish investor eligibility
An investor's wallet is associated with an identity. Claims from trusted parties attest to relevant facts, such as completion of an identity check. Each suite determines which claims it requires and which claim issuers it accepts. Reusing an identity does not automatically make an investor eligible for every asset.
3. Execute token operations
When a transaction reaches Real Chain, the network executes the relevant contracts. For an ordinary token transfer, the token and its connected contracts check the applicable identity requirements, transfer restrictions, and token state before balances can change.
A confirmed transaction establishes what the contracts executed. It does not independently establish the truth of every underlying business fact or fulfil an issuer's obligations outside the chain.
4. Carry out assigned business responsibilities
For assets connected to the Business Validator Protocol, assigned participants take on tokenization, scoring, or insurance responsibilities. The protocol defines how those responsibilities relate to stake, rewards, and enforcement. Participation and coverage depend on the asset's assignments and the integration in use.
An insurance role does not mean every tokenized asset is insured. In the protocol design, stake supports accountability; insurance payouts are a separate obligation funded by the insurance participant.
Keep authority separate
| Participant or role | Responsibility | Boundary |
|---|---|---|
| Network validator | Participate in chain consensus | Does not receive issuer or token-management powers from this role |
| Issuer workspace administrator | Perform authorized platform operations | A platform account alone does not grant contract permissions |
| Contract owner or agent | Configure or operate contracts within assigned permissions | Authority is specific to the contract and role |
| Claim issuer | Attest to facts used in identity checks | A suite must trust that issuer for the relevant claim |
| Business Validator | Carry out assigned protocol responsibilities | Admission does not automatically grant token-agent authority |
One organization may hold several roles. Each role still needs its own authorization and has its own responsibilities.
Choose the system you need
- Real Chain explains network infrastructure and execution.
- Tokenization Engine explains permissioned assets and issuer operations.
- Business Validator Protocol explains business responsibilities and enforcement.