Transaction Signing
How transactions are authorised and processed on Bond.
Every action that modifies on-chain state — swapping tokens, supplying collateral, placing trades — requires a signed transaction. The signing experience differs depending on your wallet type and the product you are using.
Swap and Lending Transactions
When you swap tokens or interact with the lending protocol, each action requires a standard on-chain transaction. With an embedded wallet, these are signed automatically within the app. With an external wallet, you will see a signing prompt in your wallet extension for each transaction.
Token Approvals
Before a smart contract can move your tokens (for a swap, deposit, or collateral operation), you must first approve the contract to spend your tokens. This is a one-time step per token per contract. The approval transaction grants permission for the specific contract only — it does not give access to your full balance to any other entity.
Perpetual Trading Sessions
The perpetuals trading engine uses session-based authentication. When you first connect, you sign a message to create a session key. This key allows the trading engine to process your orders without requiring a wallet signature for each individual trade, providing a responsive trading experience similar to centralised exchanges.
On-Chain Deposits and Withdrawals
While trade execution on the perpetuals engine uses session keys, all deposit and withdrawal operations are standard on-chain transactions that require explicit wallet approval. Your margin funds are held in auditable smart contracts — never in custody of the trading engine.
Transaction Lifecycle
Pending
Your transaction has been submitted to the network and is awaiting confirmation.
Confirmed
The transaction has been included in a block and is now finalised on-chain.
Failed
The transaction was reverted by the network. No funds were moved. This can happen due to slippage, insufficient gas, or changed market conditions.