Use this only when you cannot drive the interaction from the CLI — i.e. the dapp is hard or impossible without connecting a wallet to its frontend. Prefer tail calls or transact-raw whenever you can build the calldata yourself. See Using Dapps for the full preference order.
# Flow
- Unshield to a fresh address (
--next) - Export only that account’s key:
kohaku export-private-key --address 0xYourFreshAddress
- Install / open a browser wallet such as Ambire in a clean profile — no other seed, no other imported accounts, no shared history with your daily wallet
- Import the exported private key into that clean extension
- Use the dapp(s) you need. Prefer a VPN or Tor where possible, and treat the dapp website as potentially adversarial to your privacy
- When finished, remove the account / key from the extension (and close the profile if you created one just for this)
Note:
export-private-keyprints raw key material. Treat the terminal like a safe: no screenshots, no paste into random sites, no leaving it in scrollback on a shared machine.
# Why a clean extension matters
Browser wallets often reuse one seed and many accounts. If you import a freshly unshielded key next to your doxed daily accounts, you risk linking them through extension sync, UI mistakes, or simply using the wrong account on a dapp.
One key, one clean wallet, then delete it when done.
# Privacy while using the dapp
Every approval, swap, mint, and transfer on that address builds a public graph. The more you do from the same post-unshield account, the easier it is to characterize “who this is.” Prefer short, purposeful sessions — then stop.
If you need another private chapter later: shield again from a fresh receive address, wait, unshield to a new fresh address, repeat.