W-CONF

What confidential Multi-Purpose Tokens (MPTs) on the XRP Ledger hide, and what they do not. A research project, shown on one snapshot of the Devnet.

Where these values come from

read from https://s.devnet.rippletest.net:51234

validated ledger 6324784 at 2026-10-22T12:49:50.477Z

network_id 2 (Devnet) rippled 3.4.1

This page shows the XRPL Devnet, a test network. Its tokens have no value, and it is reset from time to time. Each value was read from Ripple's public Devnet endpoint, at the ledger and date shown, and a lying or lagging server behind it would have made it wrong. The page does not update: it shows Devnet as it was at that ledger, not as it is now. Nothing on this page signs or submits. Do not use a value shown here to build a transaction.

Vercel, which hosts this page, sees your IP address and the pages you open.

One position, field by field

Public balance

MPTAmount

an ordinary amount anyone can read

The holder's encryption key

HolderEncryptionKey

public once registered, and never changeable

Spending balance, encrypted to the holder

ConfidentialBalanceSpending

value hidden, unless it is the recognisable zero

Inbox, encrypted to the holder

ConfidentialBalanceInbox

value hidden, unless it is the recognisable zero

The issuer's copy, encrypted to the issuer

IssuerEncryptedBalance

kept beside every confidential balance; the issuer can read it

The auditor's copy, if the token names an auditor

AuditorEncryptedBalance

encrypted to the auditor; the auditor can read it

Version counter

ConfidentialBalanceVersion

counts changes to the balance, publicly

On the token: the total held in confidential form

ConfidentialOutstandingAmount

public

publichidden from the publicthe issuer can read it

One confidential position on the ledger, and what an observer can tell from each field. The panels below read these fields for four test accounts.

Public

The account's address, and every account it has transacted with (P-4).
When each transaction happened, and how often (P-11).
The public MPT balance.
The issuance's ConfidentialOutstandingAmount: the total of all confidential balances.
The holder's encryption key, once registered.
The ConfidentialBalanceVersion, which counts changes to the balance.
Whether a confidential balance is exactly zero, when it holds the canonical encryption of zero. New, merged and clawed-back balances do; a balance spent down to zero does not (F-1, E-211).
Each tranche size, when a position is retired in tranches: the amount is plaintext on every ConvertBack (F-24).

Hidden

The value of a confidential balance that is not the canonical encryption of zero, even when that value is zero (E-211).
The amount of each ConfidentialMPTSend.
Both are hidden from observers, not from the issuer (P-9). Nothing else here is hidden.

Observer view: Holder A — an active position

rHeah37pL6aFPf59nzWGwujPzSFkp4TUL8

One of the two accounts the observer view was first read against, on 2026-08-28 (CLAIMS.md E-208).

read at validated ledger 6324784

What a full-ledger observer sees

public MPT balance 750

registered true

ConfidentialBalanceVersion 11

ConfidentialOutstandingAmount 1364 (public: the total of all confidential balances)

spending

021D3288E7E5BF982641DF0ADCDB067DCFDBA95E312F0159A85E2A81B5496999B4029652CF4E578E5E03E539CBBBF04D57F5244A56D7FC1FDF4E8672E76418FDF947

Not the canonical encryption of zero, so an observer cannot tell the value. That is not the same as saying it is non-zero: a balance that reached zero by spending looks exactly like this. The issuer can still decrypt it (P-9).

inbox

03B67732AAE2EDB348088A27B147EE3D01387631CDDD357B12C24659F6EB26A04F02EE0D0A18BEED84DA931C481F57A712C8CC0731F822B5013ADE72739A0C3217C4

Publicly known to be exactly zero. This is the canonical encryption of zero, which anyone can recompute from the holder's public key, the account and the issuance, with no secret (CLAIMS.md F-1).

Observer view: Holder B — a derived-key account

rDYMkRMh7o7QfkNaoGvtd7TgFzmt12FEM8

Onboarded with the derived key, so its ElGamal key comes from its master seed.

read at validated ledger 6324784

What a full-ledger observer sees

public MPT balance 586

registered true

ConfidentialBalanceVersion 5

ConfidentialOutstandingAmount 1364 (public: the total of all confidential balances)

spending

02C8F5B45590A1CF7F9006F974DAA91FFD7C64FAA85FC2964F18F6495E23577313028556C7AA02F610759762A7449B7AF4A4A4EDFA73F8BF96BF93A09DFB09B87EBC

inbox

03C9FC4098EDC4B287A3873E21ABCA828FFE9CF50150DEE079221267F21AD8535D0289A21820DDA63C5FB4BC107A710898DBB7F10E5EEE4B8DBA205D7D8967CD8214

Publicly known to be exactly zero. This is the canonical encryption of zero, which anyone can recompute from the holder's public key, the account and the issuance, with no secret (CLAIMS.md F-1).

Observer view: Holder C — the ed25519 signing account

rsc9Z29Qz6w99TnpECxbeU6vBs2L3E3CbY

The account the hedged ed25519 signing ran on. Its ledger view is ordinary: an observer cannot see the signing change.

read at validated ledger 6324784

What a full-ledger observer sees

public MPT balance 30

registered true

ConfidentialBalanceVersion 0

ConfidentialOutstandingAmount 1364 (public: the total of all confidential balances)

spending

031AE5A70B242D81691C1FC43D684FCD908BC7DCCC07CE3ED7DD1096A9575F5D1C03CE6F696A2AACEBEB02E4728249B72E362D2DD76754F084B819A289628691F31C

Publicly known to be exactly zero. This is the canonical encryption of zero, which anyone can recompute from the holder's public key, the account and the issuance, with no secret (CLAIMS.md F-1).

inbox

022E7F2111A54AA7B0CA18EE831CB0BFCFF32FB4A4DBF2E10AAEB9ED5698657F980348759FC36C71AE3F6FE16A6904C23312D36DEFAAE95A9A2C9EE7DA7E6F84D9F2

Observer view: Holder D — an early spike account

rEVXh6wpmhKvuot95mNMb4DmkJsZqkdsWH

An early test account, kept as a second position to compare against.

read at validated ledger 6324784

What a full-ledger observer sees

public MPT balance 0

registered true

ConfidentialBalanceVersion 4

ConfidentialOutstandingAmount 1364 (public: the total of all confidential balances)

spending

0382CD36EC99297C61FE6D878C8ED59CFE0C38EEB36A316EB0FE0AC8379FC66A9603A2AA18361F6ACFBE85FDC97EEAC7F6822C5767CB74256564FDA95009C6E11A17

inbox

0266912F17A098DC7E54BFEC56277DEA0422888A0212874D411A841E385A1D1D4D0240B6B9DB0AF95113717F95B056815D5B3A1C69FE596518ACB564F0A5E92FECE5

Publicly known to be exactly zero. This is the canonical encryption of zero, which anyone can recompute from the holder's public key, the account and the issuance, with no secret (CLAIMS.md F-1).