CLASSIC STELLAR ASSET
The canonical asset identity on Stellar.
XRP262XRP262 combines a native Stellar asset, its Stellar Asset Contract, and the LEXORA controller into a clearly separated protocol stack.
This page answers the questions that matter before trust: what exists, where it lives, how the pieces connect, and what mainnet state can be checked independently.
The canonical asset identity on Stellar.
The Soroban representation of the Stellar asset.
The programmable policy and accounting layer.
Separate the asset, its Soroban interface, and its controller.
Use public identifiers, transactions, and state—not screenshots.
Expose the policy surface so important state is inspectable.
XRP262 is intentionally not presented as one opaque contract. Each layer has a distinct role and public identifier. That separation reduces ambiguity for users, integrators, and anyone reviewing the protocol.
The canonical asset identity on Stellar.
The Soroban representation of the Stellar asset.
The programmable policy and accounting layer.
Defines XRP262 on Stellar.
Makes that asset available to Soroban.
Records controller policy and supply state.
This is the completed genesis snapshot: issuance, burn accounting, and the resulting circulating supply reconcile to one explicit invariant.
Genesis mint minus recorded burn equals the stated circulating supply.
LEXORA is the controller layer behind XRP262. Its public state makes important protocol conditions easier to understand and independently check.
Four completed mainnet transactions explain the genesis path from initial issuance to the final reconciled supply state.
VIEW VERIFICATION SURFACE →The canonical identifiers are displayed here so you can copy them directly, compare them elsewhere, or inspect them through Stellar infrastructure.
Use this page to understand the system, the formal protocol PDF for the dossier, and the verification surface to check the public mainnet state yourself.