One asset verification platform - identity, provenance and financial utility for everything of value.
Six capabilities, one record per asset. Vault ID gives it an identity. Verified History and sealed documents give it provenance. Vault Score grades the evidence. Tokenise, Lending & Collateral and the Vault API connect it - through regulated partners - to capital and to the systems that already run your business.

Platform facts
Property Vault's own facts, from the pilot's code, 7 Oct 2026.
Asset → Identity → Verification → Value → Collateral → Credit.
It isn't property → token. Each step is evidenced by the one before it, and the chain is the same for a house, a watch, a yacht or a cask.
-
Asset
Twelve classes
Anything with a natural key
UPRN, VIN, hull number, serial, cask number - held off-chain.
All asset classes -
Identity
Live in pilot
Vault ID
One permanent identity per asset - the unit of record.
Vault ID -
Verification
Live in pilot
Verified History
Every event, document and owner, sealed and graded by issuer.
Verified History -
Value
Live in pilot
Vault Score
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.
Vault Score -
Collateral
Roadmap · subject to approvals
Tokenise · Lending & Collateral
A pointer token follows the Vault ID - never title. Regulated lenders read the Vault as collateral.
Tokenise Lending & Collateral -
Credit
Roadmap · subject to approvals
Markets
Regulated issuers, venues and lenders host any offer and settle; Property Vault supplies the evidence.
Property Vault Markets
A digital asset register starts with one permanent identity per asset.
The unit of record is the asset - not the owner, not the address. Format PV-GB-{AREA}-{6 digits}; issued once, never reused. For homes a UPRN or a stated reason is required.
Natural keys are captured per class and held off-chain. Launching Transfer with history intact: when the asset changes hands the Vault ID and its record go with it - the buyer accepts, the seller releases, the Vault Score recomputes - and there is no toll on transferring the record of your own asset.
- Private by design - no public lookup by address, registration or serial
- Seeding every home Vault from open data - HM Land Registry open datasets, the EPC register, planning, flood zone, OS Open UPRN - is launching
Provenance you can check, not just read.
Every event in a Vault - extension, rewire, boiler, roof - carries its evidence and the grade of whoever issued it: scheme certificate first, registered professional next, owner upload last.
Documents are hashed on upload and given an integrity receipt - the hash and timestamp that prove the file has not changed. Originals are kept; corrections are new versions. Scopes hide documents, not history; opens are logged.
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. On mainnet, a daily Merkle root of receipts will be written to the XRP Ledger - a timestamp nobody, including Property Vault, will be able to rewrite - and any receipt will be checkable on the public verifier.
A verification score with its method published.
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.
It is computed by a rules engine whose method and weights are published: Building Control 1.0, registered professional 0.9, firm 0.7, owner-provided 0.4; owner-only evidence capped at 65; listed-but-unverified professionals ×0.8. The result is 0-100 and a band - High, Partial or Low - recomputed on every event.
Owner-only cap 65 · listed-but-unverified ×0.8 · verification-rules.ts, 7 Oct 2026.
Two kinds of token. Neither is title.
Roadmap · subject to approvals A pointer token follows the Vault ID on the XRP Ledger (XLS-20/46, mutable) and references a scope-gated manifest. It is a pointer to the record - never title; the statutory register wins on any conflict. Planned for testnet after the data-protection impact assessment, then mainnet.
Fractional ownership is different: a regulated instrument issued by an FCA-authorised issuer or Digital Securities Sandbox participant through an SPV or trust, 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, runs a venue, holds keys or moves money.
Verified assets as financeable collateral.
Roadmap · subject to approvals Lending against verified assets is through regulated lenders. What a lender assesses - ownership, valuation, condition, insurance, liens, title - would be read from the Vault under a lender-valuer scope - next after the four scopes live in pilot - not re-assembled from paper.
On-ledger, it depends on XRPL amendments still in validator voting - Single Asset Vault (XLS-65) and the Lending Protocol (XLS-66) - and is supported when they activate; until then lenders assess Vaults through the Vault API. Settlement in RLUSD; liquidity in XRP.
The XRP Ledger (XRPL)
Where the daily anchor will be written - in rehearsal on the XRPL testnet today - and, through regulated partners, where tokens would live.
RLUSD
The settlement asset for regulated issuers and lenders. Property Vault never holds or moves it.
XRP
The ledger's native asset - liquidity and reserves.
The record, inside the systems you already run.
Scoped reads, registered-professional writes, webhooks and an open record schema - so a Vault can be read by a claims platform, written by a scheme and exported whole. Through the Vault API it is the data your systems call.
- Scoped reads. 160-bit tokens, stored hashed, expiring; lender-valuer, loss-adjuster, probate and broker scopes next.
- Registered-professional writes. An Organisation registered by reference to a scheme it already holds - Gas Safe, NICEIC/NAPIT, FENSA, HETAS, RICS, CLC/SRA - issues verified events.
- Webhooks on every event, version and transfer.
- Open record schema. The whole Vault exports; no URI is the only path to it.
// illustrative - a read under an insurer-surveyor scope GET /v1/vaults/PV-GB-LDS-204871 Authorization: Scope s_•••••••••••••••• { "vaultId": "PV-GB-LDS-204871", "class": "property", "vaultScore": { "value": 78, "band": "mid", "rulesVersion": "2026.10" }, "events": [ { "type": "building-control.completion", "issuerClass": "statutory", "weight": 1.0, "sealed": true }, { "type": "electrical.eicr", "issuerClass": "registered-professional", "weight": 0.9 } ], "documents": "withheld by scope" }Illustrative request and response.
The record stays off-chain. The ledger holds what identifies no one.
The record is off-chain by design. Documents, personal data, natural keys, scoring and legal title never go on-ledger. The ledger will be the independent timestamp that lets anyone check a seal - once anchoring reaches mainnet; today it is a testnet rehearsal.
Off-chain - the Vault
- The record and its documents - events, owners, versions
- Personal data - Members and Organisations
- Natural keys - UPRN, title number, VIN, serial
- Vault Score - computed by the published rules engine
- Legal title - with the statutory register, which wins
On the XRP Ledger
- A daily anchor - one Merkle root of integrity receipts; a hash, no data. Testnet rehearsal today.
- Later, pointer tokens - one per Vault ID; no address, VRM or serial reachable from the ledger.
- Later, issuer registrations - XLS-70 Credentials for registered professionals.
- Through regulated partners - fractional instruments and lending, when approved.
One record. Three ways to use it.
The same Vault - Vault ID, Verified History and Vault Score - serves the Owner who holds it, the Organisation that works on it through Pro, and, through regulated partners, the market that finances it.
| Capability | Property Vault Owners · free |
Pro Organisations · talk to us |
Markets From launch · subject to regulatory approvals |
|---|---|---|---|
| Vault ID per asset | |||
| Verified History and sealed documents | |||
| Vault Score | |||
| Portfolios, issuing, analytics, seats | |||
| Pro workflows | |||
| Tokenise | |||
| Lending & Collateral | |||
| Status | Live in pilot | Live in pilot Pro workflows launching | Roadmap · subject to approvals |
The asset verification platform, answered.
What is an asset verification platform?
A system that gives a physical asset a permanent identity, records what has happened to it with evidence, grades that evidence by who issued it, and shares the result only under the owner's control. Property Vault's asset verification platform does this with Vault ID, Verified History, Vault Score and the Vault API. The Homes pilot is live; other classes are launching or on the roadmap.
Which asset classes does the platform cover?
Twelve master classes on one record shape: Property, Land, Vehicles, Marine, Aviation, Luxury, Art, Collectables, Consumable Collectables, Specialist Assets, Infrastructure and Financial / Rights. Property is live in pilot; watches and jewellery are next, then Vehicles, then Marine; every other class is designed for - register interest.
Does Property Vault tokenise assets or lend against them?
No. Tokenise and Lending & Collateral are launching through regulated partners, subject to regulatory approvals. Any offer is made by a regulated issuer or lender; Property Vault supplies the Vault ID, Verified History, Vault Score and eligibility data, and never hosts an offer, lends, holds keys or moves money.
How does an Organisation connect its systems to the platform?
Through the Vault API - scoped reads, registered-professional writes, webhooks and an open record schema - which is launching with early access by request, and through Property Vault Pro, the professional asset management product.
Is the record stored on a blockchain?
No. Documents, personal data, natural keys, scoring and legal title stay off-chain. 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. On mainnet, a daily hash of integrity receipts will be written to the ledger, and pointer tokens are planned for testnet after the data-protection impact assessment. Nothing reachable from the ledger identifies a property or a person.
If you own it, put it in your Vault.
Create the Vault ID for your first asset, or see how Organisations work with Vaults.