Wallet Approvals & Signatures — Connection, Allowance and Transfer

Understand the authority requested by each wallet prompt.

Updated 27 October 2026

Connecting reveals a selected account

A site connection makes a public account available to the interface according to the wallet’s permissions. It is not the same action as approving every later transaction. Trusted reconnection can reduce repeated prompts without removing approval for new actions.

Message signatures and transaction signatures

A message signature can authenticate a request. A transaction signature authorizes the transaction presented to the wallet. Read the context and content; do not assume every signature is a harmless login because no transfer amount is obvious.

Token allowance

On EVM networks a contract can need an allowance to spend a token. Check the token, spender and authorized amount. Disconnecting a site does not revoke an allowance that already exists on-chain.

Separate setup from the trade

A token-account creation or protocol-account initialization may require its own transaction and costs. Completing setup does not guarantee a quote, route or order fill and does not mean the trade has already executed.

When transaction validation stops the flow

Bitpont compares the signed transaction with the reviewed operation and rejects unsupported changes. If a wallet-change diagnostic repeats, preserve the error and version and contact support. A guard should not be bypassed merely to make a transaction proceed.

Wallet troubleshooting → · Wallet safety → · Reconnection and browser storage →