hush.
TwitterTelegram

DApp Wallets

DApp wallets are standalone wallets for connecting to Solana dApps. The goal is to prevent companies from linking your IP address (and thus identity) to your main wallets. Unlike shard wallets, dApp wallets are fully independent — you control the keypair and can export it for use in other wallet apps. Fund them from your shielded balance and reshield any unused SOL when done.

Hush dApp wallet interface

Creating a DApp Wallet

Tap "Create DApp Wallet" and provide a custom name. A new keypair is generated automatically — the wallet is immediately usable. No on-chain account exists until you fund it. You can export the private key anytime from the wallet details screen.

Funding

SOL is withdrawn from your shielded balance to the dApp wallet address. Enter the amount you want to receive in the dApp wallet — Hush calculates the withdrawal amount needed to cover privacy pool fees.

  • Fee: 0.006 SOL + 0.35% (privacy pool withdrawal)
  • Minimum: ~0.0001 SOL (constrained by 0.0065 SOL minimum withdrawal)
  • Maximum: Your shielded balance minus fees

Funding runs in the background — track progress in your transaction history.

Reshielding SOL

Return unused SOL from a dApp wallet back to your shielded balance. The dApp wallet pays the shielding transaction fees, and ZK proof generation takes 10-30 seconds.

  • Minimum balance: Over 0.003 SOL (fee reserve for shielding)
  • Amount shielded: Balance minus 0.003 SOL fee reserve

Track reshielding progress in your transaction history.

Deletion

When you delete a dApp wallet, it moves to the trash can (soft delete). Unlike shard wallets, dApp wallets can be deleted regardless of balance.

Warning: Any remaining SOL or tokens in the wallet will be lost. Reshield your SOL before deleting. Trash is emptied manually or automatically after 7 days.

Flow Statuses

Track funding and reshielding operations in your transaction history:

  • Initiating — Preparing transaction
  • Broadcasting — Sending to network
  • Confirming — Waiting for confirmation
  • Confirmed — Operation completed successfully
  • Failed — Error occurred (up to 3 retries)