RWA infrastructure

Blockchain for the regulated transfer of permissioned RWA tokens.

Dexpace is being designed as an infrastructure-layer blockchain for the issuance and circulation of tokenized assets.

About the technology

Use cases

Tokenization scenariosAddressing the challenges of complex markets

Commodities

Tokenization of tailings and mine waste

Companies holding residual raw materials — tailings, waste dumps and by-products of extraction and processing — can issue tokens linked to the volume, quality and storage location of the material, creating a digital register of rights in order to attract buyers and investors and to enable the subsequent transfer of interests.

Equity

Tokenization of shares

An issuer that needs a faster and more flexible way to raise capital and to maintain a transparent cap table can issue tokens reflecting the economic rights attached to shares or participation interests, with ownership rules, transfer restrictions, KYC and automated on-chain holder records on the Dexpace blockchain.

Debt

Tokenization of debt

A company that needs to raise debt financing, refinance existing obligations or sell debt claims can create a tokenized debt instrument — a loan, a bond, a promissory note or a pool of claims — with records of holders, coupon or interest payments, redemption and secondary transfer through Dexpace.

Real estate

Tokenization of real estate

An owner who needs to raise financing, sell a stake, divide a large asset into smaller investment units or improve the liquidity of a property can issue tokens linked to the property or to an SPV, maintain records of the interests, distribute income from rent or sale, and organize regulated secondary transfer.

Funds

Tokenization of fund units

A management company that needs to simplify the subscription and redemption of units, automate its investor register and reduce operating costs can issue tokenized fund units on Dexpace: investors complete verification and receive unit tokens, while subscription and redemption, distributions and transfer restrictions are recorded through smart contracts.

Carbon

Tokenization of carbon credits

An issuer or holder of carbon credits that needs to strengthen confidence in the origin of the credits, avoid double counting and simplify their sale can issue tokens linked to verified carbon credits, carrying data on the project, the standard, the volume of CO2e, redemption status, transfer, retirement and ownership history.

Technology

Network registry technology

Dexpace moves identification, recognition, jurisdictions and the lifecycle of obligations to the level of network registries. This allows issuers to issue regulated instruments, investors to complete verification once and then use the Dexpace Passport, and consortium members to determine for themselves whose data they trust and to what extent.

Dexpace Passport

Identity

The on-chain identity of the user. The Passport stores not personal data but claims: signed attestations regarding KYC/KYB, AML, jurisdiction, accreditation, sanctions status and other checks.

Dexpace Manifest

Instrument rules

The compliance contract of the token. It verifies the holder's Passport before issuance, custody and transfer.

Dexpace Compact

Network layer

The layer of network registries: consortium members, issuers, instruments, users, jurisdictions, recognitions, lifecycle events, collateral, settlement and sanctions lists. This layer is extended with new registries by DAO decision.

Registry map

How the registries operate in sequence

The diagram shows who initiates an action, which registry is updated, and how that data is subsequently used in the issuance and secondary transfer of tokens.

Onboarding a network participant

Initiated by: a consortium member or network governance.

Organization Registry

The legal entity receives its network status and permitted roles.

Product Registry

The organization registers a product: a tokenization platform, a DEX, a bridge, a wallet or an identity gateway.

Issuer Registry

If the organization issues assets, its jurisdiction, admission status and available instrument types are recorded.

Preparing an instrument for issuance

Initiated by: the issuer, through a tokenization product.

Jurisdiction Registry

Determines the mandatory claims, the permitted instruments and cross-border restrictions.

Token Manifest

The issuer records the rules of the instrument: token type, issuance terms, transfer restrictions and requirements for holders.

Dexpace Passport

The investor completes KYC/KYB, and the identity provider adds claims to their on-chain identity.

Issuance and secondary transfer

Initiated by: the issuer at issuance; the holder or the trading venue at transfer.

Recognition Contract

Determines whether a product may trust claims issued by another platform or jurisdiction.

Token Manifest

Before issuance or transfer, checks the holder's Passport against the rules of the instrument.

Result

If the requirements are met, the issuance or transfer proceeds. If not, the operation is blocked until they are satisfied.

Diagram 1

Principles of token issuance on the blockchain

A single process supports both ordinary ERC-20 tokens and regulated security tokens. What differs is the depth of verification performed through the Dexpace Manifest.

Initiator: the organization

A participant registers in the network and receives a role: tokenization, identification, exchange, custody, bridge or service agent.

Initiator: the issuer

The issuer registers the instrument: token type, jurisdictional profile, issuance terms, document hash and status.

Action: configuring the Manifest

For an ERC-20 token, basic registration is sufficient. For a security token, the issuer defines the admission rules and transfer restrictions.

Initiator: the investor

The investor completes KYC/KYB with a provider, after which claims are added to their Dexpace Passport.

Action: mint

The Token Manifest verifies the investor's Passport before issuance. If the rules are satisfied, the tokens are issued to their address.

ERC-20Security token
Organization Registry Instrument Registry Dexpace Manifest Dexpace Passport Identity Registry

Dexpace separates the token, the identity and the admission rules. The issuer does not store personal data on the blockchain, yet obtains verifiable on-chain proof of compliance with the conditions of issuance.

Diagram 2

Principles of secondary token transfer

Every transfer is verified before execution: the recipient, the claims, network recognition, jurisdictions and any additional restrictions of the instrument.

01Initiator: the holder

The token holder initiates a transfer to another address or a transaction on the secondary market.

02Action: transfer request

The Token Manifest intercepts the operation before execution and launches the compliance check.

03Checked: the recipient

The recipient's address is matched against the Dexpace Passport through the instrument's Identity Registry.

04Result of the check

If all conditions are met, the transfer proceeds. If not, the operation is rejected.

05Checked: the Passport

KYC/KYB, AML, jurisdiction, accreditation, sanctions status and tax profile.

06Checked: recognition

The Recognition Contract determines whether the venue may trust claims issued by another platform.

07Checked: jurisdiction

The Jurisdiction Registry determines whether cross-border transfer is permitted.

08Also considered: additional registries

Sanctions, collateral, permitted means of settlement and lifecycle events.

Secondary transfer is programmed at the network level: liquidity may move between platforms and jurisdictions, but only where recognition rules have been explicitly established.

Economics and governance

Governance principles · Foundation and token

Network economics and governance

Dexpace launches as a permissioned network with a clearly defined perimeter of participants and progressively transfers control to a formalized consortium DAO. The Dexpace Foundation is responsible for developing the base protocol, maintaining the network registries and preparing this transition, while the network token serves as an infrastructure element of the ecosystem, used to pay for gas and for governance.

Participants

Licensed organizations build the products of the network: tokenization, identification, exchanges, bridges, custodians and settlement rails.

Validators

Maintain consensus, finality and the availability of the registries. At an early stage they operate under a PoA model.

Issuers

Responsible for the parameters of the instrument, the terms of issuance, transfer restrictions, document disclosure and lifecycle events.

DAO

As the network grows, governance manages the admission of participants, recognitions, jurisdictions and the updating of rules.

Foundation

Coordinates the development of the protocol and the maintenance of the network registries until the full transition to the consortium DAO.

Network token

Used to pay for gas and to participate in the governance processes of the Dexpace ecosystem.

Principles

Autonomy, plurality, interoperability

01

Autonomy

Each jurisdiction retains its own rules on admission, identification, cross-border transfer and restrictions.

02

Plurality

The network is designed for a multiplicity of participants, products, jurisdictions and asset types without enforced uniformity.

03

Interoperability

Participants can read and verify one another's data, but trust is always established explicitly through the Recognition Registry.

Roadmap

Dexpace development roadmap

A status map of the work: from the EVM L1 and the rules of token transfer through to the official mainnet launch, the expansion of the registries and the transition to a DAO.

Delivered In progress Planned Network launch

Q1 2026Delivered

Development of the EVM L1 blockchain

The base L1 layer of Dexpace, compatible with the EVM and designed for the further development of regulated registries.

Q2 2026Delivered

High-level rules of token transfer

Rules of token transfer in accordance with regulatory requirements, including seizure and freeze mechanisms.

Q2 2026Delivered

Bridge and DEX

Implementation of a Bridge and a DEX by an independent organization as infrastructure for the movement of assets and liquidity.

Q2 2026 – Q2 2027In progress

Super-app built on a decentralized messenger

Development of an application that brings the user scenarios of Dexpace together around communications, the wallet and access to the products of the network.

Q3–Q4 2027Planned

Core registries

Development of the Dexpace Passport and the Token Manifest, together with the registries of organizations, products and issuers.

Q1–Q2 2027Planned

Process for adding organizations, jurisdictions and recognitions

Formalization of the flow for onboarding new organizations, jurisdictional profiles and rules of mutual recognition.

Q1–Q2 2027Planned

Registry of new registries and developer tools

Tools for developing and registering new network registries that extend the base architecture of Dexpace Compact.

Q1–Q2 2027Network launch

Official mainnet launch

Public launch of the Dexpace mainnet following the preparation of the base infrastructure, the rules of transfer and the key user scenarios.

2027Planned

Onboarding tokenization platforms

Connection of external tokenization platforms to the Dexpace ecosystem and expansion of the number of practical RWA issuance scenarios.

2027Planned

Expansion of the registries

Addition of new types of registry on top of the base layer as the products, jurisdictions and requirements of network participants develop.

2028Planned

Transition to a DAO

Transfer of the key governance processes to the consortium: development of the rules, onboarding of participants and management of the network registries.

Partners

Singapore

XEU LABS

Development partner for blockchain products and infrastructure, including DEX and bridge solutions.

Singapore

Mexenger

Development partner for a blockchain-powered mobile super app with an integrated wallet.

Join Dexpace

Request access

Tell us who you are and what you plan to issue on the network. We will reply to the address you leave here.

Participation in the network is open to licensed organizations: issuers, tokenization platforms, identity providers, trading venues, custodians and validators.

Enter your name

Enter the name of your organization

Enter a valid work email

Choose a role

Complete the check to continue

The request could not be sent. Please try again.