About Project

MSIG.app is a web interface for multisig proposals on Antelope chains, acting as a user-friendly frontend for the eosio.msig system contract. One account prepares a transaction and publishes it as a proposal. The transaction does not execute immediately; instead, it remains in the eosio.msig system contract until the accounts listed in the proposal provide their approvals. Once enough approvals are collected, the proposal can be executed. Alternatively, if it should no longer run, it can be cancelled.

The account creating the proposal sets its name and expiration time, adds the action, and specifies the required signatories. Actions can range from token transfers and permission key changes to smart contract updates or other contract calls. Each requested account then opens the proposal, reviews the action, and approves or rejects it. This ensures no single private key needs to hold unilateral power, as the threshold strictly follows the account's existing permission structure.

Jungle Testnet serves as the ideal environment to test proposals before deploying them to mainnet. On msig.app/jungle, users log in with a Jungle account and publish proposals to Jungle's own eosio.msig table for approval and execution. Because the interface and approval workflows are identical to those used for Vaulta, EOS, WAX, XPR, Telos, and Libre, testing on Jungle provides a full end-to-end rehearsal on a test network rather than a simplified demo. MSIG.app is built and maintained by CryptoLions.

The Telegram MSIG bot is another core component of the dApp. New Jungle proposals are automatically posted to t.me/msig_jungle, and the bot (t.me/msigapp_bot) allows users to subscribe to and track proposals for any account across supported chains, check live proposal statuses, and more.

Potential Use Cases

• Try a treasury payment or a contract update on Jungle accounts before a DAO runs it on mainnet
• Change the owner or active permission of a Jungle account that can be discarded if the result is wrong
• Show a new signer how to approve and execute, without using a production account.

How a proposal is created

1. Open msig.app/jungle and log in with the Jungle account that will propose
2. Choose a proposal type, or start from Create With Wizard or Upload JSON
3. Set the proposal name and the expiration, add the action, and name the accounts that must approve
4. Confirm and sign
5. The proposal is then waiting in eosio.msig until those accounts approve it and someone executes it.

What you can create

• Transfer Tokens, Deploy Contract, Change Permissions, Vote for a BP, Buy / Sell RAM, Delegate CPU / NET, and a custom action for anything else the contract accepts
• Create With Wizard builds one of these on the page
• Upload JSON imports a proposal that was already prepared

What Tested On Jungle

1. The whole path on live Jungle eosio.msig: propose, approve from a second account, execute, then open the proposal again after it is no longer in the table
2. Permission changes on a Jungle test account
3. Login with Anchor
4. Switching to another Jungle API endpoint when the current one is slow or does not answer
5. And many more cases

Website