Applications and partners
Wallet, enterprise portal, internal systems and integrations that originate requests.
Architecture
The RDE design separates sensitive data, business rules, network validation and searchable evidence into clear layers. The sequence below is an illustrative end-to-end technical example.
Animated example
Conceptual demo. This page sends no transactions and records no documents on the network.
Public and private network
Use the controls to compare the principles of each environment. The deployment status of the RDE is kept on the network and availability page.
Infrastructure layers
Wallet, enterprise portal, internal systems and integrations that originate requests.
Planned layer for sending requests, querying state and integrating with external services.
Digital signatures, roles, authorized issuers and governance controls.
Rules for records, evidence, events and automations, per the technical specification.
The design considers permissioned nodes to validate transactions, apply rules and take part in confirmation.
The architecture plans to organize confirmed transactions into blocks with hash, timestamp and cryptographic roots.
Explorer, logs, metrics and query APIs remain planned and depend on the deployment of the network.
Integration guidelines will be published upon technical confirmation.
Planned access layer for applications, APIs and enterprise systems. No public endpoints have been published in this version.
Lookup interface for blocks, transactions, addresses, contracts and on-chain evidence of the RDE.
See the ExplorerThe final network topology, the consensus mechanism, the roles of participants and the operating parameters have not been published yet. The diagram on this page is conceptual.