--- title: MPC Signing & Operations | Frequently Asked Questions description: "Explore io.finnet MPC signing FAQs: approvals, thresholds, live signing, and request expiration." --- [Skip to content](https://support.iofinnet.com/helpcenter/mpc-signing-operations-frequently-asked-questions#main-content) English Show submenu for translations [Submit a request](https://support.iofinnet.com/helpcenter/kb-tickets/new?hsLang=en) [Customer portal](https://support.iofinnet.com/tickets?hsLang=en) ![logo #7 - no bg-1.png\]](https://support.iofinnet.com/hs-fs/hubfs/logo%20%237%20-%20no%20bg-1.png?height=40&name=logo%20%237%20-%20no%20bg-1.png) Open main navigation Close main navigation - English Show submenu for translations - [Submit a request](https://support.iofinnet.com/helpcenter/kb-tickets/new) - [Customer portal](https://support.iofinnet.com/tickets) - [Back to iofinnet.com](https://www.iofinnet.com/) [Back to iofinnet.com](https://www.iofinnet.com/?hsLang=en) Hello. How can we help you? - There are no suggestions because the search field is empty. 1. [io.finnet Help Center](https://support.iofinnet.com/helpcenter?hsLang=en) 2. [Support & Resources](https://support.iofinnet.com/helpcenter/support-resources?hsLang=en) 3. [FAQs](https://support.iofinnet.com/helpcenter/support-resources?hsLang=en#faqs) # MPC Signing & Operations | Frequently Asked Questions ### **What type of requests require signing?** io.vault uses **Multi-Party Computation (MPC)** to secure every operation that changes your vault’s state, permissions, or assets. These actions must be **approved or declined** by authorized signers before execution. ### **Operations requiring MPC signing** #### **Vault & Access Management** - **Vault creation** — Approving or declining the creation of a new vault. - **Vault reshare** — Approving or declining redistribution of signing power and/or modification of the vault threshold. #### **Asset & Transaction Actions** - **Outgoing transactions** — Approving or declining any asset transfer initiated from the vault. - **Minting a token (io.network)** — Approving or declining a token mint request. - **Burning a token (io.network)** — Approving or declining a token burn request. #### **Smart Contract Interactions** - **Smart contract executions**— Approving or declining contract calls or dApp interactions. Check our page [Technology Background](https://support.iofinnet.com/helpcenter/get-started/technology-background?hsLang=en). ### **How long does it take for the request to expire?** Requests expire after **15 minutes** by default, **except** for **vault creation requests**, which can be approved within **24 hours**. If a request hasn't reached the required threshold of approvals within this period, a new request will need to be created from the dashboard. ### **Does io.vault support background signing?** Background signing is not supported at the moment. Each signer must keep the io.vault app open and active in the foreground until signing is complete. If the app is put in the background, the connection between the devices is interrupted. All signers will then need to come back online on the app so the MPC connection can be re-established and the signing process can resume where it left off and be completed, without having to be signed again. However, if the connection between the devices is interrupted too many times, the signing can eventually fail and a new request will need to be created from the dashboard. The request will also expire if the signing process can’t be finalized during the operation’s lifetime. In both cases, a new request will need to be created from the dashboard. ### **Do all signers need to be in the app at the same time when signing an operation?** Yes, with io.vault, signing only works while every required signer’s device is connected at the same time. Each signer must keep the io.vault app open and active in the foreground until signing is complete. Switching to another app, locking the phone or minimizing the app can interrupt the connection between devices and cause the signing to fail. - All required signers must be available together within the request’s expiry window (15 minutes by default, 24 hours for vault creation requests). - Make sure your device has a stable internet connection during signing, and avoid switching between Wi-Fi and mobile data or turning a VPN on or off. - Approvals can’t be collected over the day: if the threshold isn’t reached before the request expires, a new request must be created and all signers approve again. For more guidance on setting up and operating your vault, see our [Best Practices](https://support.iofinnet.com/helpcenter/support-resources/best-practices?hsLang=en). ### **Why does the io.vault app show "Signing service disconnected – MQTT is reconnecting"?** ![MQTT is reconnecting](https://support.iofinnet.com/hs-fs/hubfs/IMG_0321.jpg?width=527&height=106&name=IMG_0321.jpg) This message means the app has lost its connection to the io.vault signing service. MQTT is the channel the devices use to exchange messages during signing, so a pending request can't progress until the connection is back. Make sure all signers: - are using a stable internet connection - are not using a VPN - are not in a [restricted location](https://support.iofinnet.com/helpcenter/platform-access-restrictions-questions?hsLang=en) - have the io.vault app open in the foreground This lets communication go through between the signers. If the signing process still doesn’t progress, or the MQTT connection doesn’t recover, quitting the app and reopening it may help restart the signing process between devices. If it still doesn’t recover, restarting the device may also help. The devices will keep trying to communicate until the request expires or fails. If that happens, a new request will need to be created from the dashboard. ### **How long does it take for a transaction to move from signing to broadcast?** Once the approval threshold has been reached and the transaction has been signed the completed transaction is immediately submitted to our network node and broadcast to the network. This can be verified by viewing a 3rd party network explorer. However, a signed transaction may still fail once broadcast to the network for other reasons, even while displaying broadcast on the dashboard so care should be taken to ensure completion. ### **Can I cancel a signature e.g. I made a mistake and did not want to sign?** No, you cannot cancel a signature. You should review the transaction details very carefully before completing the signing process. In the case where you may have made an erroneous approval, immediately close the application (which will prevent your device from signing) and contact any other members of the vault signing party.​ ### **A request was not executed and failed. What could be the issue?** There are two main reasons why a request (transaction or reshare) might fail: - Signer Availability: One or more required signers were not online and logged-in with their registered devices simultaneously to approve the request. All signers need to be present and logged-in in the app. at the same time to complete the action. - Time-Out Limit: The request was not approved and completed within the 24-hour time-out limit. Actions must be completed within this time frame to be successfully executed. ### **Can a single signature sign more than one transaction?** Each transaction must be signed individually. While we support signing multiple transactions in parallel, they still need to be queued and broadcast sequentially if they are on the same network. ### **Is batch transaction approval possible?** Batch transaction capabilities may be supported in certain systems, like smart contracts in the EVM world, but this would still rely on a single signature and may not be feasible for cross-chain use cases. ### **What happens if I force close the io.vault app after approving or rejecting a request?** If you force quit the io.vault app while signing a request, the process will be interrupted, causing the transaction to fail. You will need to initiate a new request and approve it again to complete the transaction. ### **I rejected a transaction while holding enough signing power to meet the threshold. Why wasn’t it rejected immediately?** Even if your rejection carries enough power to **meet or exceed the threshold**, the system still checks whether other participants could collectively approve. For example, if two other users each hold +1 signing power, their combined approval would still satisfy a threshold of 2. So in this case: Your rejection did **not eliminate all possible approval paths** — so the transaction remained **pending**. Only after another participant **also rejects**, preventing the remaining group from reaching the threshold, will the system update the transaction status to **Rejected**. This behavior is intentional: io.vault’s logic ensures that transactions are only rejected when absolutely no valid approval combination remains. It prevents accidental rejections in multi-user environments and reinforces the principle that **rejection requires blocking all remaining paths to approval**, not just a strong individual vote.   - [General](https://support.iofinnet.com/helpcenter/general?hsLang=en#main-content) - [About io.finnet FAQs](https://support.iofinnet.com/helpcenter/general?hsLang=en#about-io-finnet-faqs) - [Whistleblower User Guide](https://support.iofinnet.com/helpcenter/general?hsLang=en#whistleblower-user-guide) - [Get started](https://support.iofinnet.com/helpcenter/get-started?hsLang=en) - [Account Management](https://support.iofinnet.com/helpcenter/account-management?hsLang=en) - [Vault Management & Transactions](https://support.iofinnet.com/helpcenter/vault-management-transactions?hsLang=en) - [Network Management](https://support.iofinnet.com/helpcenter/network-management?hsLang=en) - [Apps & Integrations](https://support.iofinnet.com/helpcenter/apps-integrations?hsLang=en#main-content) - [Dapps](https://support.iofinnet.com/helpcenter/apps-integrations?hsLang=en#dapps) - [Reporting](https://support.iofinnet.com/helpcenter/reporting?hsLang=en) - [Support & Resources](https://support.iofinnet.com/helpcenter/support-resources?hsLang=en#main-content) - [FAQs](https://support.iofinnet.com/helpcenter/support-resources?hsLang=en#faqs) [![Chill listening crop-3](https://support.iofinnet.com/hs-fs/hubfs/logo%20%236-3.jpg?width=123&height=39&name=logo%20%236-3.jpg "Chill listening crop-3")](https://iofinnet.com?hsLang=en) Copyright © 2026, io.finnet