Asset registration
Registers an asset identity in the controller registry and records its active/disabled status.
XRP262LEXORA is the Soroban controller that gives XRP262 an explicit, inspectable policy layer around registration and supply management.
Instead of hiding protocol state behind a website, XRP262 exposes the controller address, the asset contract binding, supply policy, and current registry state so users and integrators can verify the system directly on Stellar.
The controller contract defines the policy surface used by XRP262. These are contract capabilities and state variables—not promises about future functionality.
Registers an asset identity in the controller registry and records its active/disabled status.
Exposes an explicit is_token_allowed state so integrations can check whether a registered asset is currently active.
Stores the configured XRP262 Stellar Asset Contract address as part of the controller policy surface.
Tracks maximum supply, minted amount, burned amount, minting state, pause state, and clawback policy state.
Owner-authorized minting is constrained by the configured maximum-supply accounting and controller policy.
Records XRP262 burned through the controller and exposes the resulting supply accounting on-chain.
LEXORA does not replace the native Stellar asset. It sits alongside the asset and its Stellar Asset Contract as a programmable policy and accounting layer.
Classic Stellar asset identity
Soroban interface for the Stellar asset
Controller policy and supply accounting
Keep the underlying asset recognizable and interoperable, while making the protocol policy surface explicit and inspectable.
Current XRP262 controller records verified from the completed mainnet genesis state.
Every important address shown here is public. The controller state can be read through Stellar infrastructure, and the protocol dossier documents the architecture and completed genesis sequence.