Wallet EVM Bermuda Overview

Use @bermuda/wdk-wallet-evm-bermuda to derive Bermuda shielded accounts from a WDK EVM wallet. A shielded account can deposit supported tokens into a Bermuda pool, transfer shielded balances to another Bermuda account, and withdraw to a public EVM address.

Upgrading from 0.1.x

The current address is 0x followed by 2,496 hex characters. Replace stored recipient addresses, change transaction note fields to memo, and review native versus wrapped deposits and fee accounting. Withdrawal now defaults to targeting the requested recipient amount, with fees added to the sender's spend. See the maintainer's migration guidance and the updated operations guide.

Choose This Module

Use Bermuda when your application needs a separate shielded account on Plasma testnet and can handle token allowances, proof generation, SDK services, and confirmation after submission.

For ordinary EVM transfers, use Standard EVM. Deposits are sent from a public EVM account, and withdrawals expose a public EVM recipient. Shielded-account support does not establish anonymity, production readiness, or availability on other EVM chains.

Two Account Roles

WalletManagerBermuda extends the EVM wallet manager and adds getBermudaAccount(). Its ordinary account getters continue to return public EVM accounts.

The Bermuda account is not an EVM account and does not implement the full generic WDK account interface. Its getAddress() returns a string synchronously. Use a Bermuda address for a shielded transfer and an EVM address for a withdrawal.

Account Capabilities

All three fund-moving methods return a transaction hash. A hash is not a successful receipt. Confirm the transaction and reconcile the relevant balances before displaying completion or retrying an interrupted operation.

Integration Requirements

• An application-managed BIP-39 mnemonic or seed bytes. The examples use a seed-backed manager; do not infer shielded support for hardware or custom signers.
• A Plasma testnet RPC endpoint, a supported testnet token, and the matching Bermuda pool. The operations guide shows public-chain checks for the USD₮0 testnet example.
• A Node.js or Bare runtime with network access and writable storage for the prover's downloaded setup data. WDK worklet bundles are unsupported. See runtime setup.
• Access to the Bermuda SDK's relayer, chain-state, policy/compliance, and proof-artifact services. The manager forwards the wallet RPC to the SDK by default; a nested bermuda configuration can override SDK routing. RPC configuration alone does not replace the other service endpoints.
• Native gas for public EVM transactions and any required token allowance covering the deposit and its applicable protocol and lifetime fees. transactionMaxFee rejects an EVM operation when its estimated network fee exceeds the configured threshold; it does not bind final network fees or cap protocol token fees. EVM fee caps do not bound shielded transfer or withdrawal fees. See Configuration.

These pages use the standalone manager. Directly retrieved Bermuda accounts do not automatically pass through WDK core's registered policies or middleware. The SDK's separate issuer-policy checks are part of its own proof and service flow; they are not a substitute for application authorization.

Next Steps

---

Need Help?