Selective Disclosure Needs Salts and Key Binding

Selective disclosure uses unique per-claim salts to make hidden credential values impractical to guess, while key binding proves that the presenter controls the private key associated with the credential. Its clearest nearby crypto datapoint is modest: Universal Bridge reserves rose about $55,000 over 30 days to $6.93 million, based on DefiLlama’s 0.8% change, while the protocol represents less than 0.05% of Ethereum bridge value. That is the largest verified change relevant to this verification pattern, but it is custody backing—not evidence of a purchase, sale or deposit at a trading venue. The ratio makes it operationally interesting and market-insignificant.

What does a salt do in selective disclosure?

A salt prevents a verifier from guessing a concealed claim by hashing likely values until one matches the issuer-signed digest. Under SD-JWT, the issuer builds a Disclosure from a random salt, the claim name when applicable, and the claim value; it encodes that package, hashes it, and signs the resulting digest inside the credential. The holder later sends only the Disclosures needed for a particular check. The verifier recomputes each digest and matches it to the signed payload.

This matters for predictable facts. “Over 18,” a country code or an accreditation status has too little entropy to hide behind a plain hash. RFC 9901 recommends at least 128 bits of cryptographically secure random data and a fresh salt for every claim. Reusing salts creates correlation; weak salts invite dictionary attacks. A salt hides an undisclosed value, but it does not hide a value once its Disclosure is presented, and selective disclosure is not automatically a zero-knowledge proof.

How does key binding stop credential theft?

Key binding makes a copied SD-JWT insufficient by requiring a fresh signature from the holder’s private key. The issuer places the holder’s public key, or a reference to it, in the credential. At presentation, the holder signs a Key Binding JWT containing an audience, a verifier challenge, an issuance time and a hash covering the presented SD-JWT and Disclosures. The verifier checks both the issuer’s signature and the holder’s signature.

The challenge resists replay, the audience limits reuse at another verifier, and the hash stops an attacker from attaching the proof to a different presentation. The limit is equally important: possession of a key proves key control, not that the presenter is the human described by the claim. Lost-key recovery, wallet portability and verifier tracking remain product and privacy problems.

Does selective disclosure change crypto market flows?

No: it changes what can be verified about a position or reserve, not where capital goes. The distinction is visible in the Universal Bridge reserve analysis, where backing and demand must be evaluated separately.

• Reserve custody establishes backing; it is not an on-chain venue inflow.
• Minting or bridging creates or relocates representation; idle issuance can remain unused.
• Internal transfers reorganize balances without changing market exposure.
• DEX liquidity or exchange deposits put assets where execution can affect price and slippage.

For traders over the next 30 days, salted credentials and key-bound proofs alone carry no directional signal. Watch net venue deposits, DEX pool depth and executed volume instead. This view would be invalidated by a sustained rise in verified bridge issuance accompanied by matching venue inflows and material growth in pool depth—not by another attestation or wallet transfer. The verdict: selective disclosure is valuable trust plumbing, but market relevance begins only when verified assets become deployable liquidity.