Tokenisation Engine
Issue compliant security tokens for any real-world asset.
Developer docs
What it does
The Tokenisation Engine mints security tokens under ERC-3643, the standard purpose-built for regulated tokens. Eligibility, KYC, and transfer restrictions are enforced by the token contract itself, so a transfer to an ineligible party simply cannot execute, and the rules can be updated as regulations change without reissuing the token. Where an asset calls for a different structure, such as fractional units issued in series under ERC-1155, it draws the right standard from the Token Standards Library. It is the core issuance module beneath SBX Prime and, in development, Rizq Finance.
How it works
The Tokenisation Engine sits at the start of the asset lifecycle. It takes a structured asset, mints the compliant token, then hands off to Asset Lifecycle Management for servicing, to the Compliance Engine for eligibility enforcement, and to the Secondary Marketplace for trading.
Select a step to replay it. Hover to pause.
1/5 · Asset. A real-world asset is selected. Here, an example Central London commercial building.
Key capabilities
ERC-3643 issuance
Tokens are minted under the standard built for regulated securities, not a general-purpose token.
Fractional ownership
A single asset can be divided into units sized for the investors it is meant for, including ERC-1155 series where a structure calls for it.
Embedded transfer rules
Eligibility is checked by the token on every transfer, and rules can be updated without reissuing.
Cap table management
The register of holders updates as tokens move, so the cap table is always current.