Multisig Wallets
Themultisig/wallets endpoint retrieves multisig wallet contracts from the TON blockchain. Multisig wallets require multiple signatures to execute transactions, providing enhanced security for shared funds.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
TON pricing is the same for full, archive, v2, v3There’s no difference between a full node an archive node in data availability or pricing.
All data is always available and all node requests are consumed as 1 request unit.
Parameters
address(string, optional) — Filter by multisig wallet address.proposer_address(string, optional) — Filter by proposer address.limit(integer, optional) — Maximum number of wallets to return. Default:10.offset(integer, optional) — Number of wallets to skip for pagination. Default:0.
Response
-
multisig_wallets(array) — Array of multisig wallet objects:address(string) — Multisig wallet address.seqno(integer) — Current sequence number.threshold(integer) — Required number of signatures.signers(array) — List of signer addresses.proposers(array) — List of proposer addresses.orders_count(integer) — Number of pending orders.
-
address_book(object) — Address book mapping.
Use case
Themultisig/wallets endpoint is essential for managing multisig wallets:
- Treasury management interfaces displaying wallet configuration.
- DAO tools showing governance wallet status.
- Security audits reviewing multisig setup and signers.
- Wallet applications supporting multisig functionality.
- Organization tools managing shared funds.
Query Parameters
Multisig wallet address
Filter by proposer address
Maximum number of wallets to return
Number of wallets to skip