SPL tokens don't live in the vault itself. They live in associated token accounts (ATAs) whose addresses are a PDA of <code>(vault, token program, mint)</code>. A single <code>getTokenAccountsByOwner(vault)</code> call returns every token and balance you hold, and the same applies to NFTs and compressed assets through DAS indexers. A passkey vault makes this worse, not better: every token account points back to one long-lived owner that is itself linked to your public key.

Associated token accounts are derived from the vault address and are public.

Your token holdings are one RPC call away

Every Solana account must hold a rent-exempt minimum of lamports. The first transaction that creates your vault PDA, and each ATA after it, transfers that SOL from a payer account. If that payer is your exchange withdrawal address or your old wallet, the new vault is linked to it from the moment it exists. The same happens in reverse when you close accounts: the rent refund goes to a destination you choose, which links the closed account to that destination.

Creating a vault and its token accounts needs rent-exempt SOL from somewhere.

Funding the vault reveals where the money came from

The 37-byte <code>authenticatorData</code> is part of the signed message, so it sits inside the precompile instruction: • <code>rpIdHash</code>: SHA-256 of the domain. Hash a list of likely wallet domains and compare. • flags: backup-eligible and backed up usually separate an iCloud or Google synced passkey from a hardware key. • <code>signCount</code>: synced passkeys report <code>0</code>, while hardware keys increment it. An increasing counter shows how often the key is used and orders your transactions across vaults.

rpIdHash, backup flags, and signCount are signed, so they go on-chain too.