The layers underneath.

GreyWallet is built as a hierarchy: HD wallets, accounts, and addresses — with derivation, custom paths, and high indices available during create and import.

Private Vaults sit behind a pattern. Everyday Home, Assets, and Activity stay a standard wallet until that pattern is entered.

Why both: a leaked phrase on default index 0 is a common failure. A phone left on the table is another. Derivation and vaults attack different mistakes.

During create and import, GreyWallet exposes phrase length, chain family, custom derivation path, and account index.

Why: the phrase opens the tree. Path and index choose the account. A high index is a PIN-like coordinate — casual restore scanners try 0, 1, 2.

Use it to restore an existing account, or to sit off the family default on purpose. Record the numbers with the phrase.

A pattern unlocks a separate space. Wallets stored there do not appear in Home, Assets, or Activity until that pattern is entered.

Why: shared phones, travel, a glance over the shoulder. Everyday UI should not advertise every wallet you hold.

It is device-level privacy — not undetectability. A different pattern is a different space. Never share the pattern, including with support.

Create new HD wallets or import wallets you already hold. Each wallet contains accounts; addresses derive from those accounts.

Why: one phrase can back many accounts. Without explicit path and index, import looks empty even when the words are right.

Path, index, and structure stay in setup — the full HD hierarchy, not a simplified subset.

Bitcoin, Litecoin, Dogecoin, Solana, Aptos, Sui, Movement, XRP, Tron, and a full EVM set including Cronos — each with its own key space, in one product.

Why: picking a network in the app is not the same as restoring the right family. An EVM path will not find a Bitcoin, XRP, or Tron account.

Ethereum, supported L2s, and Cronos share a signing model. Bitcoin UTXO, Solana, Move, XRP, and Tron do not.