XRP262XRP262
STELLAR MAINNET / PROTOCOL
01 / THE PROTOCOL

Infrastructureyou can verify.

XRP262 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.

PUBLIC IDENTIFIERSON-CHAIN STATE900B MAX SUPPLY
PROTOCOL MAP
One asset. Three explicit layers.
LIVE / PUBLIC
01XRP262
CLASSIC STELLAR ASSET

The canonical asset identity on Stellar.

GCGVZEE7RD2BFF2EIQUT37DYJUR7WDCQ2KWA5LUWYATRFLKEYHMJ3XRP
02XRP262 SAC
STELLAR ASSET CONTRACT

The Soroban representation of the Stellar asset.

CC7L34EWYCTDCA3L7CRRULWX577UJWET32KNJFD2WTEQ4KD7IAUKHIS6
03LEXORA
SOROBAN CONTROLLER

The programmable policy and accounting layer.

CAJL2JO6EILWBTHDRMIQVJA6MTZIUWHOD6WNVJDN7FWTYD6H3NFXH542
NETWORK
PUBLIC
REGISTRY
ACTIVE
PROOF
LEDGER
CLARITY

Separate the asset, its Soroban interface, and its controller.

EVIDENCE

Use public identifiers, transactions, and state—not screenshots.

CONTROL

Expose the policy surface so important state is inspectable.

02 / ARCHITECTURE

Simple enough to understand.Specific enough to inspect.

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.

ASSET

Defines XRP262 on Stellar.

SAC

Makes that asset available to Soroban.

LEXORA

Records controller policy and supply state.

03 / VERIFIED STATE

The numbers have a reason to be here.

This is the completed genesis snapshot: issuance, burn accounting, and the resulting circulating supply reconcile to one explicit invariant.

OPEN SUPPLY ARCHITECTURE →
MAX SUPPLY
900,000,000,000
XRP262
GENESIS MINTED
900,000,000,000
XRP262
BURNED
426,026,808
XRP262
CIRCULATING
899,573,973,192
XRP262
SUPPLY INVARIANT
900,000,000,000 − 426,026,808 = 899,573,973,192 XRP262

Genesis mint minus recorded burn equals the stated circulating supply.

04 / LEXORA CONTROL PLANE

Policy that is visible,not implied.

LEXORA is the controller layer behind XRP262. Its public state makes important protocol conditions easier to understand and independently check.

REGISTRY
ACTIVE
TOKEN ALLOWED
TRUE
SAC BINDING
VERIFIED
MINTING
ENABLED
PAUSED
FALSE
CLAWBACK
FALSE
05 / GENESIS TRAIL

Follow the state change.

Four completed mainnet transactions explain the genesis path from initial issuance to the final reconciled supply state.

VIEW VERIFICATION SURFACE →
01
GENESIS MINT9.00 × 10¹¹ XRP262
7afe1d6f7be92cb0b7859b71c71e3eae4ad68fa523362c915217a425782be67f
INSPECT ↗
02
REGISTRY ENABLEASSET ACTIVATED
c26e354ac5fe32565aeacd42cfe0dfcdad5e40bbb8f58c47a67ef08520859a90
INSPECT ↗
03
LEXORA TRANSFER426,026,808 XRP262
2f89fbfd0ced1d7392950a1a6bcbfb2f22ea61b0c9d77898447598b3e511cbc5
INSPECT ↗
04
BURN426,026,808 XRP262
4ed32c2fe4b14466c8ce92db3f94e695071e26db4ef49f7f8979b043cd65f434
INSPECT ↗
06 / PUBLIC IDENTIFIERS

Nothing important should depend on a shortened address.

The canonical identifiers are displayed here so you can copy them directly, compare them elsewhere, or inspect them through Stellar infrastructure.

07 / VERIFICATION FIRST

The website is the map. The ledger is the evidence.

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.