Multisig Transaction Builder
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
Multisig Transaction Builder is a developer tool for interacting with multisignature wallet contracts. Enter a multisig wallet address and choose an action — propose a new transaction, confirm an existing pending transaction, or execute a transaction that has reached the required number of confirmations. For proposals, specify the target contract address, value in ETH to send, and the calldata (hex-encoded function data) for the transaction. The tool encodes the transaction, submits it to the multisig contract, and displays the result with transaction hash and confirmation status. This is essential for teams using multisig wallets for treasury management, contract upgrades, or administrative actions that require multiple approvals.
HOW TO USE
Connect your wallet using the BGWallet bridge (MetaMask or any Web3 wallet). Ensure you are on the same network as the multisig wallet — Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, or any EVM chain. Enter the multisig wallet address in the input field. Select the action: "Propose transaction" to submit a new transaction to the multisig, "Confirm transaction" to approve an existing pending transaction, or "Execute transaction" to finalize a transaction that has enough confirmations. For proposals, fill in the target address, value in ETH, and the calldata (hex string). For confirmations and executions, enter the transaction nonce. Review the transaction details in the summary card, then click "Submit transaction" to sign and broadcast through your wallet. Results appear with transaction hash and confirmation status.
TECHNICAL MECHANISM
The tool uses ethers.js to interact with Gnosis Safe-style multisig contracts. The contract ABI includes the core functions: submitTransaction(address to, uint256 value, bytes data) for proposing new transactions, confirmTransaction(uint256 nonce) for approving pending transactions, and executeTransaction(address to, uint256 value, bytes data, uint256 nonce, bytes[] signatures) for finalizing transactions that have reached the threshold. For proposals, the tool validates the target address, converts the value to wei using ethers.utils.parseEther(), and accepts the calldata as a hex string. The transaction is sent through signer.sendTransaction() with the contract call encoded using the ABI. After sending, the tool waits for 1 confirmation and displays the receipt status. The nonce for confirmations and executions is the transaction index in the multisig's queue. The tool does not manage signatures or off-chain approval collection — all confirmations happen on-chain through the contract's confirmTransaction function.
WHAT IT CANNOT SEE
The tool cannot automatically detect which multisig standard the contract uses — it assumes Gnosis Safe-style multisig contracts and may fail with other implementations like MultiSend, Gnosis Safe with different versions, or custom multisig contracts. It cannot simulate transaction execution to predict success or failure — you only know the result after the transaction is mined. It cannot manage signatures or off-chain approval collection (EIP-1271, off-chain signatures, or Gnosis Safe's signature collection flows) — all confirmations must be submitted on-chain individually. It cannot recover or replace lost transactions that are stuck in the multisig queue. It cannot fetch pending transaction details automatically — you must know the nonce for confirmations and executions. It cannot detect if a transaction has already been confirmed or executed without checking the contract state separately.
PLEASE NOTE
This tool works exclusively on EVM-compatible chains (Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche C-Chain, Fantom, and others). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool assumes Gnosis Safe-style multisig contracts (version 1.1.1 and later). Different multisig implementations may have different function signatures. Ensure you understand the transaction you are proposing — incorrect parameters may result in failed transactions and lost gas. Always test on testnets before using on mainnet. The tool is provided as-is with no warranty or liability. Review all transaction details carefully before signing.