A New Web3 Wallet Paradigm: MPC Wallets and AA Smart Contract Wallets

Why Do Web3 Wallets Need New Technology?

Traditional Web3 wallets are generally controlled by a private key. Users sign transactions with the private key, and the blockchain network then verifies whether the signature is valid.

To make backups easier, wallets usually represent the private key as a seed phrase. Anyone with the correct seed phrase can restore the account in a compatible wallet.

This model is simple, but it has several clear drawbacks:

• A wallet may be impossible to recover if the seed phrase is lost;
• An attacker may gain full control if the seed phrase is exposed;
• Users must take responsibility for backups and safekeeping;
• A compromised device may expose the private key;
• Complex account recovery rules are difficult to configure;
• Each on-chain action usually requires a separate signature;
• Users need to hold the native gas token for the relevant network.

MPC wallets and AA smart contract wallets approach these problems from different directions. MPC mainly changes how private keys are generated, stored, and used for signing, while AA encodes account authorization rules in a smart contract.

For an introduction to the relationship between Web3, wallets, and on-chain accounts, see What Is Web3? A Complete Guide to the Next Generation of the Internet.

What Is an MPC Wallet?

MPC stands for Multi-Party Computation.

In an MPC wallet, the critical material controlling an account is divided into multiple key shares. These shares are stored on different devices, servers, or with different participants. When a transaction is signed, multiple shares jointly perform the computation without reconstructing the complete private key in one place.

Common share distribution arrangements may include:

• One share stored on the user's phone;
• One share stored in the cloud or on a secure server;
• One share stored on a backup device;
• Multiple shares held separately by different company administrators.

The number of shares, signing threshold, and recovery method vary between MPC wallets. Users should not assess a wallet's security from the “MPC” label alone. They also need to understand how the specific product distributes and manages its key shares.

How Does an MPC Wallet Complete a Transaction?

For an MPC wallet involving two or more parties, a transaction may follow this process:

1. The user enters the recipient address and transfer amount in the wallet;
2. The wallet creates the transaction data to be signed;
3. The key share on the user's device participates in the signing computation;
4. Shares on a server or other authorized devices also participate;
5. The system confirms that the required signing threshold has been met;
6. The parties jointly produce a signature that the blockchain can verify;
7. The signed transaction is broadcast to the blockchain network;
8. The network verifies the signature and processes the transaction.

The complete private key does not need to appear on a single device or server. Even if an attacker obtains one share, they may not be able to create a valid signature independently.

However, assets may still be transferred if an attacker controls enough shares or successfully bypasses device authentication and recovery procedures.

What Are the Benefits of MPC Wallets?

4.1 Reduced Single-Point Exposure Risk

In a traditional wallet, the complete private key is usually stored on one device or in one seed phrase backup. MPC distributes signing capability across multiple shares, requiring an attacker to breach more security controls at the same time.

4.2 A Better Account Recovery Experience

Some MPC wallets let users reconfigure shares through a backup device, identity verification, or a recovery service, reducing the risk created by losing a single seed phrase.

Recovery depends on the specific wallet. Not every MPC wallet can restore an account under all circumstances.

4.3 Multi-Device Management

Users can distribute key shares across a phone, computer, and backup device. Companies can also assign shares to different departments or administrators.

4.4 Greater Multi-Chain Compatibility

MPC signing usually occurs off-chain and ultimately produces a standard signature recognized by the target blockchain. It can therefore work with multiple blockchains without requiring a dedicated multisig contract on each one.

4.5 Hidden Internal Authorization Structure

The blockchain generally sees only the final signature. It may not reveal how many devices or participants jointly approved it.

What Are the Risks of MPC Wallets?

5.1 Server Dependency

Some MPC wallets require a service provider's server to participate in signing. If that server fails, shuts down, or restricts access, users may temporarily be unable to initiate transactions.

5.2 Recovery Mechanism Risk

Recovery features improve convenience but can also create an attack surface. An attacker may try to steal access to an email account, SIM card, cloud account, or identity credentials and then use the recovery process to take over the wallet.

5.3 Opaque Implementations

Different products may all market themselves as “MPC wallets,” but technical documentation is needed to determine whether shares are truly independent, whether the service provider can sign unilaterally, and whether the recovery mechanism is secure.

5.4 Simultaneous Device Compromise

If multiple key shares are stored on devices or accounts that are not properly isolated, an attacker may obtain enough shares at once.

5.5 Unclear Backup Methods

Some MPC wallets do not use a traditional seed phrase. Users should understand in advance how recovery works after a service interruption, device loss, or phone replacement.

How Is MPC Different from On-Chain Multisig?

Both MPC and multisig can reduce the risk of one key controlling all assets, but they operate in different places.

MPC is a cryptographic key-management method, while multisig is generally an on-chain account authorization method. They are not the same concept.

What Is an AA Smart Contract Wallet?

AA stands for Account Abstraction.

Traditional Ethereum accounts are primarily divided into externally owned accounts and smart contract accounts. An externally owned account is controlled by a private key and can initiate transactions. A smart contract account is controlled by code but traditionally cannot initiate transactions in the same way as a standard externally owned account.

Account abstraction aims to give user accounts programmable validation and execution logic. With AA, a wallet can be implemented as a smart contract and use code to define signing, recovery, spending limits, and gas-payment rules.

An AA smart contract wallet may support:

• Joint authorization across multiple devices;
• Social recovery or guardian-based recovery;
• Passkey login;
• Daily transfer limits;
• Transfers restricted to allowlisted addresses;
• Multiple actions executed as a batch;
• Gas paid by an application or third party;
• Transaction fees paid with another token;
• Temporary session permissions for games or applications.

Not every AA wallet supports all these features. Its actual capabilities depend on the wallet contract and supporting infrastructure.

How Does ERC-4337 Work?

ERC-4337 is an important Ethereum account abstraction standard. It introduces a transaction-processing flow for smart accounts without directly changing Ethereum's consensus layer.

The flow includes the following key roles.

8.1 Smart Account

A smart account is the contract account that actually holds assets under the user's control. Its contract can define custom signature validation, recovery, and execution rules.

8.2 User Operation

A user operation describes an action the user wants the smart account to perform, such as a transfer, swap, or approval.

It resembles a traditional transaction but enters a dedicated processing flow.

8.3 Bundler

A Bundler collects multiple user operations, checks their basic validity, and packages them into an on-chain transaction.

8.4 EntryPoint Contract

EntryPoint is the central contract in the ERC-4337 flow. It coordinates smart accounts, Bundlers, and Paymasters, validates user operations, and executes transactions.

8.5 Paymaster

A Paymaster is an optional gas-sponsorship contract. An application can use it to pay network fees for users who meet specified conditions.

“Gas sponsorship” does not mean that an on-chain transaction has no cost. It means another account or contract covers the fee.

How Is an AA Wallet Transaction Completed?

Using an ERC-4337 smart account as an example, an operation may follow this process:

1. The user initiates an action in a wallet or DApp;
2. The wallet creates a user operation;
3. The user authorizes it with a device key, passkey, or another method;
4. The user operation is sent to a Bundler;
5. The Bundler simulates the operation and checks whether it is valid;
6. If a Paymaster is used, the system also checks the conditions for gas sponsorship;
7. The Bundler packages multiple valid operations;
8. The packaged transaction is sent to the EntryPoint contract;
9. EntryPoint calls the smart account to validate authorization;
10. After successful validation, the transfer or contract interaction is executed;
11. The blockchain records the final result.

The user may see only one confirmation in the interface, but contract validation, Bundler processing, and network execution still occur behind the scenes.

What Are the Benefits of AA Smart Contract Wallets?

10.1 Account Recovery

A smart account can use backup keys, guardians, or a delayed recovery mechanism. If the primary key is lost, the user may be able to replace it according to predefined rules.

10.2 Batched Transactions

A traditional wallet may require a token approval first and a separate swap transaction afterward. Where supported, an AA wallet can combine several actions into one flow.

Batching can reduce the number of confirmations a user must make, but it does not necessarily reduce every on-chain fee.

10.3 Gas Sponsorship

An application can use a Paymaster to pay gas for eligible users, reducing the barrier for new users interacting with a DApp for the first time.

10.4 Flexible Validation

A smart account can support multisig, passkeys, device keys, and other validation methods instead of being limited to one private key.

10.5 Permission Controls

Users can set per-transaction limits, daily limits, allowlisted addresses, and session keys. A game, for example, can receive limited permissions without gaining control over all the user's assets.

What Are the Risks of AA Smart Contract Wallets?

11.1 Smart Contract Vulnerabilities

The security of an AA wallet depends on its contract code. If its validation, upgrade, or recovery logic has a vulnerability, an attacker may bypass normal authorization.

11.2 Upgrade Permissions

Some smart accounts allow their contract code to be upgraded. This can help fix vulnerabilities, but it may also let an administrator or other controlling party change account logic.

11.3 Abuse of Recovery Rules

Guardians, backup keys, or social recovery mechanisms can become account takeover paths if configured incorrectly.

11.4 Infrastructure Dependency

ERC-4337 wallets may depend on Bundlers, Paymasters, and RPC services. If a particular service fails, some convenience features may be temporarily unavailable.

11.5 Gas Sponsorship Limits

Paymasters generally impose conditions based on amount, frequency, application, or identity. Users should not assume that every transaction will be free.

11.6 Network Compatibility

Blockchains support account abstraction to different degrees. Smart account addresses, features, and assets may not remain fully consistent across all networks.

What Is the Difference Between an MPC Wallet and an AA Wallet?

MPC and AA address problems at two different layers.

They can be summarized as follows:

MPC primarily answers, “How can private keys and signing capability be stored more securely?”

AA primarily answers, “What validation, recovery, and transaction rules can an account define?”

Can MPC and AA Be Combined?

Yes.

A smart contract wallet can use MPC for its underlying signing or key management while using an AA contract to define account permissions.

A combined wallet may use the following structure:

• The user's device stores one MPC share;
• A secure server or backup device stores other shares;
• Multiple shares jointly produce an authorization signature;
• The AA smart account validates the signature;
• The smart account applies limits, allowlists, or batched operations;
• A Paymaster covers gas fees when its conditions are met;
• If the user loses a device, recovery rules are used to reconfigure the shares.

This combination can improve both off-chain key security and the on-chain account experience, but it also increases system complexity. Users need to understand the MPC service, smart account contract, and recovery rules together.

How Should You Choose an MPC Wallet or AA Wallet?

Consider the following factors when choosing a wallet.

14.1 Is It Truly Self-Custodial?

Determine what permissions are held by the user, service provider, and recovery party. Pay particular attention to whether the provider can sign independently, freeze the account, or block recovery.

14.2 How Is the Account Recovered?

Check what information is required after a device is lost and whether recovery depends on an email address, phone number, cloud account, backup device, or third-party service.

14.3 Does It Provide a Seed Phrase?

Some MPC wallets do not use traditional seed phrases. Users should confirm whether an account can be exported or migrated if the product's service ends.

14.4 Has the Contract Been Audited?

For an AA smart contract wallet, review the contract code, audit reports, upgrade permissions, and administrator controls.

14.5 Which Networks Are Supported?

Confirm which blockchains, tokens, and DApps the wallet supports. Do not assume the same feature works on every network.

14.6 Are the Gas Rules Clear?

Confirm who pays gas, whether sponsorship is limited, and what asset is required when sponsorship is unavailable.

14.7 Does It Support Permission Management?

Check whether the wallet can set limits, guardians, allowlists, session keys, and confirmations for high-risk transactions.

Security Tips for Using New Web3 Wallets

Whether you use an MPC wallet or an AA smart contract wallet, follow basic security practices:

• Download the wallet through an official channel;
• Never give anyone your password, private key, or seed phrase;
• Enable multi-factor authentication for email and cloud accounts;
• Choose guardians and recovery contacts carefully;
• Regularly review signed-in devices and permissions;
• Test with a small amount before transferring substantial assets;
• Check the network, address, amount, and permissions before signing;
• Understand how to migrate the account if the service ends;
• Do not interpret “seedless” as “free from private-key risk”;
• Do not interpret “smart wallet” as “completely secure.”

How Can You Explore On-Chain Features with Hotcoin Web3 Wallet?

Users can visit Hotcoin Web3 Wallet to explore on-chain wallet and Web3 features, or download the Hotcoin App to access the mobile entry point.

Before using a wallet, confirm:

• How the wallet is created and imported;
• Whether it provides a seed phrase or another recovery mechanism;
• Which blockchain networks it supports;
• How signatures and transaction details are presented;
• Which permissions are granted when the wallet connects to a DApp;
• How the account can be recovered or migrated if the device is lost.

Conclusion

MPC wallets and AA smart contract wallets represent two important directions in the development of Web3 wallets.

MPC uses multi-party computation to distribute keys and signing capability, reducing the risks associated with storing a complete private key on one device. AA uses smart contracts to give accounts programmable validation, recovery, spending limits, transaction batching, and gas-payment rules.

The two technologies are not substitutes for each other. MPC mainly improves key management, while AA mainly improves account logic, and they can also be used together.

New wallet models can reduce some usability barriers, but they do not eliminate all risks. Users still need to understand key shares, recovery procedures, contract permissions, and infrastructure dependencies before selecting a wallet based on their asset size and use case.

Visit the Hotcoin website for more information about the platform and its products.