XRP Ledger tokenisation: how it works - and why the record comes first.

"Tokenisation" is used to mean five different things. This article takes XRP Ledger tokenisation in the order Property Vault intends to build it - a hash, a pointer, a credential, a regulated fraction, a settlement - and says at each step what the XRP Ledger does, what a regulated partner does and what stays off it. The order matters: a token that points at an unverified record points at nothing.

Start with a hash

The cheapest and most honest thing a ledger can do for a physical asset is prove that a document existed, in exactly this form, on a given day. Every file added to a Vault is hashed on upload and given an integrity receipt - the hash plus a timestamp. Once anchoring reaches mainnet, each day's receipts will be combined into a single Merkle root, and that one 32-byte value written to XRPL mainnet in the memo of an AccountSet transaction from Property Vault's own account.

No per-asset object, no personal data, no address or serial - at most one hash a day, committing to every receipt of that day, and none on a day when nothing changed. Anyone holding a receipt can recompute the path from their document to the root and check it against the public ledger, which is what the verifier will do. The ledger adds what a company's own signature cannot: a public, independent timestamp that nobody, Property Vault included, can rewrite.

Launching Integrity anchoring runs as a rehearsal on the XRPL testnet: Merkle roots of keyed commitments are written to the test network, which can be reset, and listed on the public anchor page; mainnet anchoring is on the roadmap, subject to approvals. Anchoring on mainnet and the public verifier are the first ledger milestone.

A pointer, not a deed: the XRPL NFT pointer

The second step gives each asset something on the ledger that can be pointed at. The XRP Ledger has had native non-fungible tokens since 31 Oct 2022 (XLS-20), and since 11 Jun 2025 (XLS-46, DynamicNFT) a token can be mutable, so its URI follows the record as it grows. Property Vault's XRP Ledger tokenisation design uses exactly that: one pointer token per Vault ID, the digital asset identity, its taxon set to the asset class, its URI pointing at the Vault's manifest - a short, versioned description of the record whose current hash the pointer attests to.

Two limits keep the word "pointer" honest. The manifest sits behind a scope, so nothing reachable from the ledger reveals a UPRN, address, registration or serial. And the pointer is not title: if it and the statutory register of title ever disagree, the register wins and the pointer is corrected.

Two identity primitives sit around it. A Decentralised Identifier (XLS-40, live 30 Oct 2024) gives Property Vault, and later each registered professional, a DID on the ledger. Credentials (XLS-70, live 4 Sep 2025) let one account make a signed statement about another: Property Vault would issue a registered-professional credential to an electrician's account, by reference to the scheme membership they already hold, and withdraw it when that membership ends.

This is where drafts of "verified history on-chain" go wrong. An XLS-70 credential binds an issuer account to a subject account, not to a token - the right tool for registering who may say things, the wrong tool for the events themselves. A credential from a gas engineer's account to a homeowner's account about an identifiable property would put personal data on a public ledger. Instead, each verified event is a hash inside the record, referenced from the pointer's manifest, so history travels with the asset, not with any account.

XRPL RWA tokenisation: fractions, through a regulated issuer

The third step is what most people mean by tokenisation - dividing economic ownership of an asset into fungible units - and it is the step Property Vault does not perform. A fractional interest in a house, a painting or a cask is usually a regulated investment; issuing, promoting and trading it belong to an FCA-authorised issuer or a Digital Securities Sandbox participant, working through a special-purpose vehicle or a trust. What follows is how such an issuer would use the ledger - not what Property Vault offers.

The XRP Ledger does this without a smart contract. Multi-Purpose Tokens (XLS-33, live 1 Oct 2025) are fungible tokens with protocol-level controls: RequireAuth so only approved accounts may hold them, lock and clawback so an issuer can halt transfers or recover units under a court order, and 1,024 bytes of metadata for the legal wrapper and a link to the pointer token. Permissioned Domains (XLS-80, live 4 Feb 2026) define who counts as approved - a set of credential types from named issuers, such as a KYC provider. The Permissioned DEX (XLS-81, live 18 Feb 2026) gives domain members their own order book, so transfers happen only between parties the issuer's rules admit - for XRP and trust-line tokens today; an MPT can trade there only once the MPT DEX amendment (XLS-82), not yet enabled, activates. Token Escrow (XLS-85, live 12 Feb 2026) holds units or stablecoin against a condition, such as a completion payment.

Settlement would run in RLUSD, the dollar stablecoin issued on the ledger, so a completion does not move with a volatile price; XRP supplies liquidity and pays fees and reserves. One implementation note: pointing an MPT issuance at a Permissioned Domain through its DomainID field is documented as requiring the SingleAssetVault amendment, still in validator voting; until it activates, per-holder MPTokenAuthorize does the same job one account at a time.

XRP Ledger tokenisation primitives, with dates

Status as of 7 Oct 2026 (xrpl.org Known Amendments; xrpldashboard). Items in voting are listed below.

What stays off-ledger

Why put anything on a public ledger, and what exactly? An XRPL engineer and a data-protection officer ask the same question, and the answer is a short list on the ledger and a long list off it. Documents stay off because a survey runs to megabytes and an NFT URI holds 256 bytes; personal data because the UK GDPR right to erasure cannot be honoured on a public chain; natural keys because they would turn the pointer into a public lookup; scores because they are recomputed whenever the evidence changes; and legal title because it lives in the statutory register.

The law, stated correctly

Four pieces of law and policy are quoted around XRP Ledger tokenisation more often than they are read.¹

The 2025 Act. The Property (Digital Assets etc) Act 2025 (Royal Assent 2 Dec 2025) confirms that a digital token can be property in its own right - a third category of personal property. It does not link a token to a home, car or watch - that link is contractual. Only the agreement and the record behind a token make it mean anything about a house.

The Digital Securities Sandbox. The Bank of England and FCA Digital Securities Sandbox has been live since 8 Jan 2024 and runs to 2029; the Bank and the FCA were working with 16 firms in it in May 2026 (Bank of England, 18 May 2026); HSBC (13 Jul 2026) and ClearToken (18 Sep 2026) have passed Gate 2. CurveBlock, the first entrant focused on real-estate development fund tokenisation (Gate 1, May 2025), is Leeds-based. Its participants are the kind of issuer the third step assumes.

MiCA. MiCA's crypto-asset service provider regime has applied across the EU since 30 Dec 2024, with transitional periods ending by 1 Jul 2026. It does not cover tokenised securities (MiFID) or unique NFTs.

Dubai. The Dubai Land Department issues its own title-deed tokens on the XRP Ledger through a licensed platform (Phase 1, May 2025; secondary trading, 20 Feb 2026). It proves the ledger carries registry-grade tokens. It also shows the condition: the deed tokens work because the registrar itself is the issuer.

What is still in voting: XLS-65 and the XLS-66 lending protocol

Three amendments matter to the later chapters and none has an activation date. Each activates only after more than 80% of trusted validators vote yes for two continuous weeks, so the phrase for all three is "when activated".

• Single Asset Vault · XLS-65Pooled liquidity with vault shares - and the amendment the MPT DomainID field is documented to depend on.In voting · 57% on 7 Oct 2026, 80% needed
• Lending Protocol · XLS-66Fixed-term loans from vault liquidity with terms, repayments and defaults on the ledger. Supported when it activates; until then regulated lenders assess Vaults through the Vault API - see how borrowing against verified assets is planned.In voting · 48%, 80% needed
• ConfidentialTransferEncrypted balances and amounts with a public supply check - relevant later to private ownership of high-value items.In voting · 51%, 80% needed

Validator support as of 7 Oct 2026 (xrpldashboard). Percentages move; the rule does not.

Where Property Vault sits in XRP Ledger tokenisation

Property Vault's position is the layer underneath all five meanings. The Vault ID is one permanent identity per asset. The Verified History is every event, document and owner, sealed on upload and graded by who issued it. The Vault Score is a verification score - whether the documents exist, who issued them and that they are unaltered since issue; never a valuation, a credit input or a judgement of the work. Tokenisation - whole, as a pointer; or fractional, as a regulated instrument - is offered only by FCA-authorised issuers or Digital Securities Sandbox participants for assets that meet a minimum Vault Score and a clean statutory record. Property Vault supplies the Vault ID, Verified History, Vault Score and eligibility data; it never hosts an offer, gates holders, runs a venue, holds keys or moves money.

That is why, in XRP Ledger tokenisation, the record comes first. Tokenised property failed when the record went stale - unpaid taxes, blight and litigation (RealT, Jul 2026); illiquidity (USDR, Oct 2023). A live record fed by institutional data is the fix - the layer Property Vault builds. The primitives are ready; the discipline is to use them in order. More on the asset tokenisation platform, RWA tokenisation through Property Vault Markets, the Vault API, tamper-evident documents and security and real-world asset infrastructure for investors. The tokenise-to-lend flow has been run end to end on XRP Ledger test networks: see the XRPL testnet tokenisation demo (no real assets, money or offers).