Action wallets

Create, back up and fund

In Actions, give the wallet a label and choose New wallet. Its index and address are saved in the encrypted vault before funding. Download a fresh encrypted backup.

Enter Fund from private balance, choose Review funding, then Confirm private funding. Funding is a separate pool withdrawal with a relay fee. Later transactions pay gas from the action wallet's own BNB. A failed later action does not undo funding.

Choose the action

• BNB payment: recipient and BNB value.
• Token transfer: token contract, decimals, recipient and token amount. Use Read token to check decimals.
• BNB → token swap: exact tokens to receive and maximum BNB input through the supported PancakeSwap V2 route.
• Exact token approval: spender and amount; avoid unintended permissions.
• Revoke approval: set the selected spender's allowance to zero.
• Contract call: destination, function ABI, JSON arguments and BNB value.
• Advanced calldata: only encoded calls you understand.

ABI token amounts often use base-unit integer strings. BNB value is separate from a token amount and should be zero unless the destination requires native BNB.

Simulate before signing

Prepare transaction displays the destination, BNB value and calldata. Review recipients, spender permissions, minimum outputs and external app documentation. Acknowledge the review, then simulate the current state to receive a gas quote.

Confirming signs on your device and broadcasts the unchanged envelope. A simulation is not a security audit or a guarantee of success. Quotes expire and a changed nonce, gas quote or locked wallet can require a new review.

Return unused BNB

Choose Return unused BNB to private balance for the selected wallet. This uses the pool return route and its quoted relay fee. It returns BNB, not arbitrary token holdings. Tokens remain at the public wallet address until you transfer or sell them through a supported route.

Read the limits

There is no dedicated integration for every BNB dapp or a universal WalletConnect session here. DeFi, NFTs and bridges require correct app-specific calls. Some calls will fail simulation or be outside supported transaction limits. Encoded data can contain permissions or recipients beyond what visible-address screening detects.

Keep pending transaction hashes. If confirmation is uncertain, inspect the original hash before attempting the action again. Transactions, token balances and approvals are public.