LanguageDistributed ledger built for tokenized securities
The distributed ledger infrastructure for IXTO’s governance and lifecycle management. Configure nodes to match institutional participation and operating requirements.
Who it is for
Operators that need dedicated ledger infrastructure for a tokenized securities business, and institutions evaluating IXTO
Build a dedicated ledger environment for securities operations.
PURPOSE BUILT
Securities operations
Record ledger entries and changes in rights through IXTO smart contracts on the distributed ledger.
DATA RESIDENCY
Operating options
Choose between institution-operated nodes and dedicated nodes provided by TESSA. A separate dedicated ledger can also be scoped.
ACCESS CONTROL
Node and access control
Control node access and smart contract execution according to institutional roles and network policies.
The ledger functions a tokenized securities business needs, provided as standard.
SECURITY LEDGER
A ledger structured for tokenized securities
Issuance, account transfer, redemption, pledge, seizure and disposal restriction are supported at ledger level.
TOKEN MANAGER
Contract deployment and permissions
TokenManager handles the deployment and permissions of tokenized-securities smart contracts.
SECURITY TOKEN
The record of holdings and rights
The SecurityToken ledger records holdings and processed changes in rights.
KSD INTERFACE
Total-volume management interface
Provide smart contract interfaces for integration with the electronic registration institution’s total-volume management functions. Institutional scope and procedures are confirmed during adoption.
ON PREMISES
Deployed in your environment
Define Besu node deployment and connectivity according to institutional infrastructure and security requirements.
View the network summary alongside the latest blocks and transactions. Find records by block or transaction hash, and check contract events and their processing status.
Shows indexing status and the on-chain range covered.
Explore records by block number or transaction hash.
Distinguishes decoded events from undefined ones.
Three layers: the network, the smart contracts, and the institutional interfaces.
Network
IXO-NET RPC Node
Ledger access
Node operation
Deployed in your environment
Smart contracts
TokenManager
Deployment and permissions
SecurityToken
Rights-change ledger
Institutional connections
Quantity-management interface
Electronic registration institution interface
IXTO connection
Lifecycle management solution
Consensus nodes and business-access nodes have distinct roles. Connections between institutions follow integration standards and security requirements, with VPN and access-control scope agreed case by case.
Block proposal · Validation
Consensus participation
Consensus participation
Validator and RPC separated
Total-volume node integration
Queries · Transaction submission
Conceptual view of node roles and integration targets · actual node count and topology agreed with each institution
Proposes and validates blocks and reaches consensus. Access is managed separately from business access paths.
Handles queries and transaction submission, keeping business-service access paths separate from consensus nodes.
Ledger finality and the explorer’s indexing status are checked separately. IXTO links actual processing results to workflow status.
Business validation · Signing request
Signed transaction submission
Consensus → Ledger finality
Results · Events · Balances
Look up blocks, transactions, addresses and security tokens. The explorer has no ledger-entry permissions and shows its lookup scope and indexing lag.
The participation model and scope of supply are set to match each institution’s operating capability and security requirements.
The institution builds and operates its own Validator and RPC nodes.
Operating team · Node setup · Network accessThe scope of use and operating responsibilities for a TESSA-provided dedicated node are agreed.
Operating scope · Access rights · Support modelFor institutions that need a separate network, the scope of a private ledger and IXTO supply is agreed.
Consensus · VPN · Contracts · IntegrationBuilt on EVM contracts and standard RPC and WebSocket interfaces. For a private network, the deployment, signing and upgrade paths of the target environment are confirmed.
We confirm your infrastructure environment together, then compose the network.
STEP 01
Environment assessment
We review your infrastructure environment and operating policy together.
STEP 02
Network composition
Define node topology, access rights and operating policies.
STEP 03
Contract deployment
TokenManager and SecurityToken are deployed and verified.
STEP 04
Business integration
Connected to IXTO and the institutional interfaces, and confirmed in operation.
Runtime for IXTO
Acts as the execution layer for IXTO, our governance and lifecycle management solution
Deployment environment
Support for on-premises operation
Electronic registration institution interface
Participation in the total-volume management testbed project (June 2025)Tokenized securities distributed ledger integration testing (October 2026)
Share your business plans and system environment. We will help define the scope and timeline.
Request a consultation