Question (flightofthefox)
at the moment the link between users accounts and personas are trivially known to any dApp builders who can harvest linkages between them. (not the best design from RDXW TBH, but it is what it is). warrants perhaps being cautious about over-loading personas with this new responsibility (rather than starting with a new primitive)
The current Persona/account linkage problem
In the current Radix Wallet implementation, when a user connects to a dApp, they present both a Persona and one or more accounts. The dApp sees both, and the linkage between them is explicit and harvestable:
Current flow:
User connects to dApp
→ dApp receives: Persona_X + [account_alice, account_bob]
→ dApp can record: Persona_X ↔ account_alice ↔ account_bob
→ This mapping is trivially known to any dApp operator
→ Aggregating across dApps → near-complete identity graph
This is not a theoretical concern — it is the current state of the system. Any dApp that logs connection data can build a detailed linkage graph over time.
Why this is specifically problematic for our proposal
If we publish stealth_meta_address inside a Persona, and that Persona is routinely linked to real accounts by dApps, then:
dApp has harvested: Persona_X ↔ account_alice
Persona_X contains: stealth_meta_address_alice
Observer can now:
→ Monitor all transactions containing hints
→ Test each hint against stealth_meta_address_alice
→ Identify all stealth payments received by Alice
→ Completely defeats the purpose of stealth addresses
The stealth_meta_address being public is only safe if the Persona itself cannot be linked to a real account. The current design breaks this assumption.
The “new primitive” suggestion is sound
Your instinct to avoid overloading Personas is architecturally correct. Instead of attaching stealth_meta_address to an existing Persona, a cleaner approach would be a dedicated Stealth Identity primitive — a new on-chain object whose sole purpose is to publish stealth receiving capability, with no connection to any Persona or account by design:
New primitive: StealthIdentity
On-chain object containing:
scan_public_key : "02abc..."
spend_public_key : "03def..."
version : 1
created_epoch : N
Explicitly NOT linked to:
→ Any Persona
→ Any account
→ Any transaction history
→ Any dApp connection
Published via:
→ A dedicated registry contract
→ Or a well-known address derivation scheme
→ Or shared directly peer-to-peer (QR code, messaging...)
This object exists independently. Bob shares his StealthIdentity with Alice through whatever channel they choose — it has no on-chain connection to his real identity. Use of the persona for this task was primarily because it was already available and unlinkable to the account -granted you don’t link them inside a Dapp-, but this would be a better approach.
The trade-off this introduces
The Persona approach had one practical advantage: discoverability. If Bob’s stealth_meta_address is in his Persona, Alice can find it automatically when Bob is in her contacts. With a standalone StealthIdentity primitive, Bob needs to explicitly share it — there is no automatic discovery path.
This is not necessarily a problem. In fact it might be a feature:
Persona approach:
→ Discoverable by anyone who knows Bob's Persona
→ But Persona is linkable to account → privacy leak
StealthIdentity approach:
→ Shared deliberately, peer-to-peer
→ No automatic discovery
→ But zero linkage to real identity by construction
→ Stronger privacy guarantee
For a privacy system, deliberate sharing is arguably more appropriate than automatic discovery anyway. You share your stealth identity with people you intend to receive payments from — not with the whole world.
A hybrid path worth considering
There is a middle ground that preserves some discoverability without the linkage problem:
Option: Stealth Identity published under a stealth address itself
Bob generates a fresh stealth address S
Bob publishes his StealthIdentity at address S
Bob shares S with Alice out-of-band
Alice fetches the StealthIdentity from S
Alice derives Bob's stealth payment address
Alice sends payment
The registry entry at S has:
→ No link to Bob's Persona
→ No link to Bob's accounts
→ Just a scan_key and spend_key
This bootstraps the discovery problem using the same stealth mechanism recursively — a StealthIdentity is itself discovered via a stealth-like address, making the whole system self-consistent.
Bottom line
The critique is valid and the proposal should respond to it directly in the document. The recommendation would be:
Do not attach stealth_meta_address to Personas in the current Wallet implementation. Instead, introduce a dedicated StealthIdentity primitive that is architecturally isolated from the Persona/account system. This is a stronger design that does not depend on fixing the Persona linkage problem first — it simply sidesteps it entirely.
The Persona integration could be revisited later if and when the Radix Wallet addresses the account/Persona linkage issue at the protocol level. For now, a standalone primitive is the right call.