Try out the new Re-simulate button for signing requests, now available on both app and web.
This option appears only when a request is in a pending state, allowing users to rerun the transaction simulation before signing. This enables you to better review and verify transaction details, ensuring accuracy and preventing errors before finalizing any action.
You can now view token details and flag spam tokens on the MPCVault mobile app, bringing Web-level control to mobile users.
UTXO represents unspent transaction outputs. In the blockchain, each Bitcoin transaction is split into inputs and outputs, with each output generating a UTXO. When you send BTC, you use previously received UTXOs as inputs and create new UTXOs as outputs for the transaction. These new UTXOs can be used in subsequent transactions. The balance of BTC is composed of multiple UTXOs.
For example: A sends 1 BTC to B. C sends 0.8 BTC to B. At this point, B has two UTXOs on their BTC address, and their balance is 1.8 BTC. B's wallet has two UTXOs that can be used:
UTXOs are like different denominations of paper money in our wallet, representing different amounts of funds. When you receive funds, they become UTXOs, and when you spend funds, you can select and combine UTXOs accordingly to cover the desired amount while creating new UTXOs for any remaining balance.
Continuing with the above example, now B has two UTXOs on their address, which are 1 BTC and 0.8 BTC. Now, B wants to transfer 0.5 BTC to D. In theory, there are two transfer options for B (ignoring transaction fees for simplicity):
If B wants to transfer 1.2 BTC to D, they need to spend both UTXOs, and they will receive 0.6 BTC change. (Transaction fees are not considered for the sake of explanation in the above examples).
When the total available UTXO amount from the sender is insufficient to cover the transaction amount and network fees, a "UTXO Insufficient" prompt will appear when signing the transaction. In this case, you can either wait for pending transactions to confirm 1 block or transfer funds from other addresses to increase the total available UTXO amount.
BTC congestion refers to the congestion of transactions on the Bitcoin network, caused by the number of transactions exceeding the network's processing capacity. Due to the design limitations of the Bitcoin network, each block can only accommodate a limited number of transactions. Therefore, when the number of transactions on the network exceeds the capacity limit of the blockchain, congestion occurs.
Additionally, the speed of transaction confirmation also affects the congestion on the network. In the Bitcoin network, each transaction needs to be confirmed by nodes on the network (6 confirmations) before it can be processed. If the number of nodes on the network is insufficient or if the transmission speed between nodes is slow, it can result in slower confirmation speeds and potential rejection of transactions.
Here are some methods to avoid BTC network congestion:
Set appropriate transaction fees: Paying a reasonable transaction fee can ensure quick confirmation of your transactions. Opting for a reasonable fee incentivizes miners to prioritize your transaction.
Utilize transaction batching: If you have multiple small-value transactions, try combining them into a single larger transaction. This help reduce the number of UTXOs and transactions, thereby reducing network load. MPCVault also supports batch payment. Read more about the Batch Payment here.
Plan transaction timing: If you anticipate network congestion, such as during significant events, try to avoid sending transactions during that time. Instead, opt for sending transactions during times when the network is relatively less congested, enabling faster confirmation.
By implementing the methods mentioned above, you can optimize transaction performance and reduce the likelihood of encountering BTC network congestion.
MPCVault now allows you to set a vault to private, restricting visibility to organization admins and vault members only.
To enable, go to Settings in that vault and toggle on Private Vault. A private label will appear on the Vault page, ensuring tighter control over sensitive assets.
We've added automatic refresh to improve your transaction experience on the mobile app:
This removes the need for manual updates, making the process smoother and more efficient.
When making batch transfers with an EVM wallet, please avoid using contract addresses as recipients to prevent transaction failures. Many smart contract addresses do not support direct transfers and require interaction through specific contract functions. Sending funds directly may result in lost or reverted transactions.
For more information on batch payments, refer to the guide on our website.
Based on user feedback, we are expanding vault policy settings to provide more flexibility and security. Now, you can choose between Simple and Advanced modes:
By default, new vaults are created in Simple Mode with a single manager requirement. These updates ensure better control over your transaction policies while keeping management intuitive.
Introducing the new cross-platform "All Wallets" view — you can now manage all your wallets in one place, whether they were created via API or directly in the app. In this page, you can rename wallets, toggle network settings, and pin up to 20 wallets for quick access.
We are happy to announce that MPCVault has integrated with the Movement Network. Movement is a high-performance, modular L1 built for scalability, security, and decentralization. Start sending and receiving assets including Coin and NFT today.
Explore the complete list of assets supported by MPCVault.
You asked, we listened! Thanks to user feedback, we've made card top-ups more convenient than ever. You can now top up directly from the MPCVault mobile app — anytime, anywhere. For more details on how to use your card, refer to our guide.
