Keystone Registry

Enforcement with each chain's own controls

Reading holders and supply works the same on every chain. Enforcement uses what each chain and token already provide: native controls or audited standards, never a contract we wrote.

Launch chains: XRPL, Ethereum, Base, and Solana, with Stellar next. Every adapter passes one shared contract test suite. Nothing runs on mainnet yet; status as of .

The same rules on every chain

Every snapshot is read at a finalized height with the block hash recorded, every amount is an exact integer, and every enforcement action is prepared unsigned for you to sign in your own custody. What a token can enforce depends on how it was created, so the console shows each token's capabilities, gaps included.

XRPL

Built
Tokens
Multi-Purpose Tokens (MPT)
Holder record
Every holder of an issuance read from a validated ledger, including past ledgers.
Finality
Validated ledger
Tested on
Recorded and live runs on the XRPL testnet.
XRPL: enforcement actions
ActionHow it is enforced
AuthorizeIssuer authorizes each holder when the issuance requires authorization
FreezeLock a single holder, or the whole issuance, when the issuance allows locking
Claw backNative clawback, when the issuance was created with clawback enabled

Issuance flags are fixed when the token is created. A token created without clawback can never be clawed back, and the console says so.

Ethereum and Base

Built
Tokens
ERC-3643 (T-REX) tokens, or an existing token contract through a configured ABI
Holder record
Rebuilt from Transfer events from the deployment block, then each balance checked against the contract at the snapshot block.
Finality
Finalized block
Tested on
Recorded fixtures, including a simulated reorg, and a local development chain. A Base Sepolia run is pending.
Ethereum and Base: enforcement actions
ActionHow it is enforced
AuthorizeIdentity registry verification (ERC-3643), handled in your onboarding
FreezeERC-3643 address freeze or partial freeze, or your contract's own freeze function
Claw backERC-3643 forced transfer, or your contract's equivalent
PauseERC-3643 pause, or your contract's pause function

We never deploy contracts for you. A plain ERC-20 with no controls can be recorded but not enforced on chain. Arbitrum, Polygon, and Avalanche C-Chain are supported as configuration of the same adapter.

Solana

Built
Tokens
Token-2022 mints (legacy SPL tokens read-only)
Holder record
Every token account for the mint at finalized commitment, summed per owner wallet. Past states come from stored snapshots.
Finality
Finalized commitment
Tested on
Recorded fixtures. A live devnet run is written and waiting on devnet funding.
Solana: enforcement actions
ActionHow it is enforced
AuthorizeAccounts frozen by default, thawed for approved holders by the freeze authority
FreezeFreeze authority freezes every token account the wallet owns
Claw backPermanent delegate extension moves tokens back to the treasury
PausePausable extension, when the mint has it

Solana nodes do not serve past account state, so point-in-time records rely on snapshots stored at the time. Transfer hook programs are read-only for us unless the issuer documents them.

Stellar

BuiltNext after launch
Tokens
Classic Stellar assets
Holder record
Every trustline for the asset from the latest closed ledger. Past states come from stored snapshots.
Finality
Closed ledger
Tested on
Recorded fixtures and a live testnet run, replayed offline from its recorded responses.
Stellar: enforcement actions
ActionHow it is enforced
AuthorizeIssuer authorizes each trustline when authorization is required
FreezeRevoke authorization, or keep offers but block payments
Claw backNative clawback, only on trustlines opened after clawback was enabled

Stellar has no protocol-level pause. Soroban token contracts are not supported yet.

See it on your token

We walk through testnet tokens end to end with synthetic data: a holder record, a blocked transfer, a prepared freeze, a reserve coverage check, and chain verification.