What we're building next — and what we're pushing the ecosystem to make possible.
Today's NFT Delivery-vs-Payment uses two sequential transactions — buyer accepts the NFT, then payment releases automatically. With XRPL Hooks (XLS-30), both will happen in a single ledger entry: truly atomic, with zero window for either party to back out. Coming when XLS-30 launches on XRPL mainnet.
In progress upstreamRLUSD is already supported for payments, but native RLUSD escrow (locking stablecoin funds on-chain) requires Ripple to enable the lsfAllowTrustLineLocking flag on their issuer account — a requirement of the XLS-85 token escrow standard. We're ready to activate this the moment they do.
Waiting on RippleCurrently NFT proof verification covers XRPL native NFTs. Ethereum ERC-721 and Solana NFTs are next — allowing buyers to require proof of ownership from any chain, with the same on-chain verification guarantees.
Coming soonW3C Verifiable Credentials are already live on AgentTrust today. XLS-26 goes further — it brings Decentralised Identifiers (DIDs) natively to the XRPL ledger itself, so identity anchors to the chain rather than an external DID document. We'll add DID-based identity as a first-class proof option the moment XLS-26 hits mainnet.
Coming soonThere is no public database mapping company names to their NFT-issuing wallet addresses — across any chain. AgentTrust is building it. Cryptographically verified via domain records, the registry will be published as an open standard any protocol or chain can reference. We're in early conversations with the XRPL Foundation about making this ecosystem infrastructure.
Proposed