# Mimir-EVM Introduction

Mimir will provide a Multisig-As-A-Service (MAAS) solution, offering an end-to-end service for any EVM chain or Layer2 chain that requires it. This service includes contract deployment, frontend pages, module deployment, and continuous operations and maintenance.

### Introduction

Mimir is your ultimate multisig wallet, engineered to deliver an exceptional multisig experience. Mimir's key features include the creation of multisig accounts, comprehensive transaction lifecycle management, secure third-party application login, and versatile security policy configuration.

**For blockchains:** Mimir enables the rapid deployment of robust multisig applications. It offers end-to-end services, from contract deployment to frontend interfaces, along with continuous maintenance and upgrades.

<figure><img src="https://lvaum5an0ad.feishu.cn/space/api/box/stream/download/asynccode/?code=NzJmMjI1MjgyYWRiZTRlN2Y2ZDU2NDgyMDlkODIyMDZfTHcyU3loczFEem1SZHFRTFQ2SmlWRDI1UWo5UUFDbExfVG9rZW46VUNUb2JiOWFhb0ducVp4ajRFOWN5VXVUblhmXzE3MTgzNDgxNjY6MTcxODM1MTc2Nl9WNA" alt=""><figcaption></figcaption></figure>

**For applications:** Mimir provides an SDK that allows multisig users to interact with the application's visual interface directly. This simplifies onboarding and supports a wider variety of account structures.

**For institutional users:** Mimir offers a secure asset management solution with complete account ownership, similar to MPC wallets. It is highly efficient and gas-saving, particularly for complex organizations.

<figure><img src="https://lvaum5an0ad.feishu.cn/space/api/box/stream/download/asynccode/?code=NDY3YTI0MzQwOGQyNzRkMzBjNDk3ZmE5NGU0YjIwMjhfZTlONVk5Q0dlS3c4WkRabzkyWEFPN0lkWXptVmExakpfVG9rZW46TGFnWGJvRzljb3pVUkJ4ZXJWU2NRbFN1bjN0XzE3MTgzNDgxNjY6MTcxODM1MTc2Nl9WNA" alt=""><figcaption></figcaption></figure>

**For regular users:** Mimir delivers a flexible and convenient multisig experience. It also includes easy-to-configure security policy features, making it accessible and user-friendly.


# Mimir Features

## High Compatibility with Safe

Mimir uses the same contracts as Safe

### **Account Compatibility**

All basic features available in Safe can also be implemented in Mimir, with the added capability of loading various types of Modules.

### **Application Compatibility**

Interaction between multisig accounts and third-party applications is a core feature of Safe, facilitated through the Safe SDK and WalletConnect. Mimir is already compatible with the Safe SDK, so applications that have integrated the Safe SDK need no additional changes.For applications not yet adapted to the Safe SDK, a one-time adaptation will allow them to support both Safe and Mimir. Furthermore, you can use WalletConnect to interact with third-party applications.

<figure><img src="https://lvaum5an0ad.feishu.cn/space/api/box/stream/download/asynccode/?code=OWFiZTk1MDhmOGYwZWUzZDQyNzAxOWRjZDc3ZWJkYmNfM3VnZVFrUkNaTU1MZlgyVFYzdGE1MkFYV2NXTkRPQVFfVG9rZW46VjVHWGJrWjBtb0d3bFV4R01UU2M2Z0tmbjdkXzE3MTgzNDgxNjY6MTcxODM1MTc2Nl9WNA" alt=""><figcaption></figcaption></figure>

## Enterprise-Level User Friendliness

### **Nested Multisig Adaptation**

Mimir continues to support complex multisig capabilities. For enterprises, institutions, DAOs, etc., that might use multisig accounts as members of other multisig accounts, Mimir allows for seamless operation. Users only need to select their account for signing without using WalletConnect to log into Mimir for signatures within complex account structures.

### **Policy Rules**

A key feature of MPC wallets is the flexible setting of Policy Rules to grant or restrict specific privileges for certain members, Mimir introduces this into multisig account. This functionality significantly enhances the efficiency and security of enterprise fund management.Currently, we offer two rules:

* Easy Expense: Allows flexible spending without multi-signatures.
* Recovery: Helps recover accounts during emergencies.

In the future, we will provide more practical features such as multisig weights and tiered thresholds.

<figure><img src="https://lvaum5an0ad.feishu.cn/space/api/box/stream/download/asynccode/?code=OGEyZGQzN2EwMWM5MzkyNzQ4YmE1NGFmY2M4MDhlNzhfMVZlbU8yQWdRNzE4YTZqR0lnOHBHa3pZZ3RTOU9MYjNfVG9rZW46VXlxVWJPZVVpb1VXbDd4VWRmcmNFYVJEblNmXzE3MTgzNDgxNjY6MTcxODM1MTc2Nl9WNA" alt=""><figcaption></figcaption></figure>

### **Most Gas-saving Solution**

Mimir can consolidate multiple approval transactions into a single transaction, regardless of account hierarchy and complexity, significantly reducing transaction costs.


# Accounts

## Supported Accounts

In Mimir, users can create and use the following types of accounts:

### **1. Multisig**

A standard multisig account typically refers to accounts with more than one member (e.g., 2/3, 2/2, 1/2) and a threshold of at least one. All members are EOAs, adhering to the original design of multisig accounts where multiple individuals share asset management permissions for the same address.

### 2. Advanced Multisig

Advanced multisig accounts currently include:

* **1/1 Multisig Account**

A 1/1 multisig account has one member and a threshold of one. This type of account helps users achieve a certain degree of risk isolation and account privacy protection. Even if the private key is compromised, some assets remain relatively secure, while the operator and user accounts are isolated to provide privacy protection.

* **Nested Multisig Account**

A nested multisig account is a multisig that includes other multisig members. Our research indicates that there are about 8,000 nested multisig accounts on Ethereum within Safe, controlling around 21% of ETH assets in Safe. These accounts typically belong to large institutions, DAOs, or organizations such as MakerDAO, Lido, and Bankless.

<details>

<summary>Multisig Accounts</summary>

A multisig is composed of one or more addresses and a threshold. The threshold defines how many signatories (participating addresses) need to agree on submitting an transaction for the call to be successful.

For example, Alice, Bob, and Charlie set up a multisig with a threshold of 2. This means Alice and Bob can execute any call even if Charlie disagrees with it. Likewise, Charlie and Bob can execute any call without Alice. A threshold is typically a number smaller than the total number of members but can also be equal to it, which means they all have to agree.

Multi-signature accounts have several uses:

* Securing your stash: use additional signatories as a 2FA mechanism to secure your funds. One signer can be on one computer, and another can be on another or in cold storage. This slows down your interactions with the chain but is orders of magnitude more secure.
* Board decisions: legal entities such as businesses and foundations use multisigs to govern over the entity's treasury collectively.

*Referral:* [*https://docs.safe.global/home/what-is-safe*](https://docs.safe.global/home/what-is-safe)

</details>


# Transaction

## 1. Transaction Steps

Multisig account transactions can be divided into three steps:

### 1. Initiate Transaction

Any member of the multisig can initiate a transaction for approval. The initiator must sign the transaction to indicate they have proposed it.

### 2. Collect Signatures/Approvement

During the signature collection stage, only multisig members can participate. Other members, besides the initiator, need to review the transaction details and decide whether to approve it.&#x20;

If they approve, they must provide their signature. At this stage, a transaction can also be canceled by sending a blank transaction to occupy the nonce, thus invalidating the unwanted transaction.

### 3. Execute Transaction

Once enough signatures are collected, the transaction can be executed by the multisig. At this point, anyone (not just multisig members) can pay the gas fee and execute the transaction.

## 2. Nonce

Like EOAs, multisig accounts follow a nonce rule, where transactions must be executed in a sequential order, starting from nonce #0 and incrementing by one for each subsequent transaction. Members can specify the nonce when initiating a transaction, deciding whether they want it to be executed immediately or at a future point in the sequence.

Only one transaction per nonce can be executed. If multiple transactions are in the signature collection stage with the same nonce, executing one will invalidate the others. To cancel a transaction, a blank transaction can be sent to occupy the nonce, thereby executing the blank transaction instead of the original one.


# Dapps

## 1. Wallet Connect

Since multisig accounts do not have private keys, they cannot be directly imported into MetaMask or other plugin/mobile wallets. As a result, they cannot interact directly with other applications through these wallets.

Mimir supports Wallet Connect, allowing users to use all applications that support Wallet Connect with their multisig account, including Mimir itself.

{% content-ref url="/pages/RjSQnqZrajvw95jDeqDw" %}
[Connect to Dapps](/guide/connect-to-dapps)
{% endcontent-ref %}

## 2. Third-party Dapp

Third-party applications can integrate Mimir's EVM-SDK. This allows users to directly open third-party applications from Mimir's Dapps page using their multisig identity, enabling quick interactions.

## 3. Tools

Tools are a series of utility mini-applications created by Mimir to help users perform basic operations, such as transfers, batch transactions, and Contract Builder.


# Policy Rules

## Easy Expense

In the Safe application, this feature was originally called Spend Limit. It allows an address (which can be a member or a non-member) to use a certain amount of funds without needing approval. The limit can automatically replenish after a specified time interval.

{% content-ref url="/pages/3tFy4EiRvpLZuoVKihEB" %}
[Set Easy Expense](/advanced/set-policy-rules/set-easy-expense)
{% endcontent-ref %}

## Recoverer

The Recover feature authorizes an address (which can be a member or a non-member) to initiate the reset of multisig members and thresholds in emergencies. This reset requires that during the Review Window, members not reaching the threshold do not oppose and execute a cancel transaction, and the reset transaction is completed before the Expire Period.

{% content-ref url="/pages/SJycY0d03BxPmbWQB5ju" %}
[Set Recoverer](/advanced/set-policy-rules/set-recoverer)
{% endcontent-ref %}


# Modules

Modules are a concept designed at the inception of Safe's Smart Account in 2018. This modular architecture allows Safe Smart Accounts to add additional features over time without requiring users to migrate to a new account.

## What is Modules?

To draw an analogy, it’s like Chrome and its extensions. With extensions, Chrome can connect you to the Web3 world, block annoying ads, check for spelling errors, and provide security tips. One of the advantages of Chrome’s development is its powerful and comprehensive extension ecosystem. You either use Google to enjoy a complete and timely updated extension experience or use a bare-bones browser.

In Safe, Modules serve a similar function to extensions. The Smart Account created by the user is essentially a contract account, which means it can be programmed to have various functionalities. This includes executing transactions according to the rules of the Module. A Module is a new smart contract associated with the Safe Account, containing highly customizable logic determined by the Module’s developer. It can even allow transactions to be executed without meeting the threshold of member approvals.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FFa0LEU4BifzftNnZ9N7A%2Fimage.png?alt=media&amp;token=b0d56a8b-815a-4419-8e14-69fa5c623840" alt=""><figcaption></figcaption></figure>

## What can Modules do?

Once installed, they enable a variety of additional functionalities for multisig accounts, including but not limited to:

1. **Gas Payment** - Use any type of token or even credit cards to pay gas fees.
2. **zkLogin** - Log in to your multisig account using various social media accounts, making it as simple as Web2.
3. **XAccount** - Ensure your address remains consistent across multiple chains.
4. **Vesting Pool** - Make your multisig account a more secure reward pool, releasing rewards to users.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2F7ox9UxVG0PICUOc1hSmR%2F5b99c1ac-3e75-478b-bca3-ecd25f26b742.png?alt=media&amp;token=78aad7b8-87bd-4938-991b-61fdd3dc0d01" alt=""><figcaption></figcaption></figure>


# Create Multisig

After entering Mimir, you can create a multisig wallet. If you don't create one at the beginning, you can also create it later under the account selection.

## Create Multisig

{% hint style="info" %}
You can create a multisig for any address, and it doesn’t necessarily have to include the address you used during the creation as a member.
{% endhint %}

Click "Create Multisig" to enter the multisig creation page.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FPCCgCM1vQzWCFAaacYQ6%2Fimage.png?alt=media&amp;token=97040b0c-5a8b-4fa5-91e1-e8c2964c9a0d" alt=""><figcaption></figcaption></figure>

Enter the following parameters to complete the creation:

* **Name**: The name that will be displayed and synced among all members of the multisig account.
* **Members**: You can select locally connected addresses, multisig accounts, and address book entries as members. You can also add other addresses as members.
  * **Nested Multisig**: If you want to create a nested multisig, simply select a multisig account as a member.
* **Threshold**: The number of member signatures required to execute a transaction. We strongly recommend setting the threshold to greater than 1 if there are more than one member, to better protect the security of the multisig.

A fee is required to create a multisig, so please ensure your account has sufficient balance to cover this cost.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FTcBtpRj11rRvNRtBJJBe%2Fimage.png?alt=media&amp;token=add1d4af-ae4a-41f4-afcd-3baa0d47c0f7" alt="" width="375"><figcaption></figcaption></figure>

After setting up, please make sure to keep the page open. Once all the steps are completed, the multisig account will be successfully created.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2Fs2yASjpdoBADakmJwfCY%2Fimage.png?alt=media&amp;token=aab4c6b8-1572-49f1-8871-1ee72a4f6d44" alt="" width="375"><figcaption></figcaption></figure>


# Import/Export Multisig

Mimir will synchronize the multisigs associated with the Extension Wallets you've authorized locally.&#x20;

However, during this process, there may be some edge cases that require you to manually import the multisig.

## Import through configuration file

<figure><img src="https://content.gitbook.com/content/fYktjzAQubX4SAAWG6sc/blobs/Wmeo6hWRLQW811lzLEzu/image.png" alt=""><figcaption></figcaption></figure>

You can ask other members to click 'Export' on the multisig's setting page to download the multisig configuration file and send it to you.

&#x20;

<figure><img src="https://content.gitbook.com/content/fYktjzAQubX4SAAWG6sc/blobs/pLdtKJ56OccId0a4AFgW/image.png" alt=""><figcaption></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/fYktjzAQubX4SAAWG6sc/blobs/doQUGIbtpkf7p9XEqKs7/image.png" alt=""><figcaption></figcaption></figure>

If your local Extension Wallet is indeed a member of this multisig, you can recover it by importing that file using the 'Import' button on the Create page.


# Initiate Transactions

When users execute any on-chain operations with a multisig identity, the process follows the flow of initiating the transaction, approving the transaction, and then executing the transaction.&#x20;

## How to initiate transaction?

Let’s take transferring as an example.

In the Transfer Dapp, we use a multisig account to transfer 0.01 ETH to a single-signature account. Click the submit button to enter the transaction initiation page.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FxtQ8ZgYnKSvHdkhwSzcv%2Fimage.png?alt=media&amp;token=008c6ea3-93ad-419e-8d1c-c3128730bd80" alt="" width="375"><figcaption></figcaption></figure>

On the transaction initiation page, you will see the following information:

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FKMKoAuoikWD2I2UwgALn%2Fimage.png?alt=media&amp;token=7feb5c68-a135-4a18-b818-b6cca6eca9fc" alt=""><figcaption></figcaption></figure>

* **Sending From**: The initiator of the transaction, usually the multisig wallet.
* **Interact With**: The contract being interacted with. For native token transfers, this will show the recipient's address.
* **Transaction Details**: Details of the transaction, including relevant parameters.
* **Safety Check**: We have integrated some third-party applications to help you assess the security of the transaction.
  * **Simulation**: We use Tenderly to simulate the transaction, helping you check if the transaction can be executed smoothly and how it will affect the account’s assets if successful.
  * **Risk**: We use Redefine to monitor transaction risk activities, helping you identify financial or fraud risks associated with this transaction.
* **Signer**: Defaults to your current address. If your multisig account is a nested multisig and the current address appears in multiple layers, you can choose the layer you wish to use.
* **Nonce**: Multisig account transactions follow a sequential order. We will recommend some options, but you can modify them according to your needs.
  * **Next Execute**: Selecting Next Execute will place the transaction at the top of the queue.
  * **In Order**: Selecting In Order will place the transaction after the one with the highest nonce in the queue.

You can also manually enter an existing transaction nonce, but this will cause the transaction under that nonce to be discarded.


# Manage Transactions

After accessing the Transaction page, users can view the list of pending transactions for the selected account in the Pending section.

All members can view the transaction details and progress, and decide how to handle it.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2F506ug8m3wTrUBeCKQmDk%2Fimage.png?alt=media&amp;token=f4a3045a-4e3b-45b9-9b8f-820fb7229dad" alt=""><figcaption></figcaption></figure>

## Function

### Approve

If you are a multisig member and the required number of approvals for a multisig transaction has not yet been reached, and you believe a transaction should be executed, you can select the transaction and click Approve or ✅ to approve it.&#x20;

{% hint style="info" %}
This action only requires collecting your signature and does not send the transaction.
{% endhint %}

### Cancel

If you are a multisig member and do not want a transaction to be executed, you can click Cancel or ❌ to cancel the transaction. Canceling the transaction will initiate a blank transaction that shares the same nonce as the original transaction. If the blank transaction (i.e., the cancel transaction) is executed first, the original transaction will automatically be voided and will not be executed.&#x20;

{% hint style="info" %}
Canceling a transaction also requires approval and execution by others to take effect.
{% endhint %}

### Execute

If a transaction has obtained the required number of signatures and its nonce is in the Next Execute position, anyone (not just multisig members) can perform the Execute operation to send the transaction on-chain.&#x20;

{% hint style="info" %}
Transactions in the Queuing cannot be executed until their nonce comes up.
{% endhint %}

## Information

### Process

The 'Process' section shows the current progress of the transaction, displaying the approval status of multisig members.&#x20;

<figure><img src="https://content.gitbook.com/content/fYktjzAQubX4SAAWG6sc/blobs/uXmPKNsCQYY7TaC7vN9M/image.png" alt=""><figcaption></figcaption></figure>

If this transaction involves nested multisig accounts, users can click on "overview" to view the details.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FUWWLeE7njIoKIdO2tRsO%2Fimage.png?alt=media&amp;token=6b601c64-09cb-4c77-b1d6-2edbb43c8335" alt=""><figcaption></figcaption></figure>

### Transaction

It includes the specific details of the transaction, the method called, and its parameters.


# Connect to Dapps

Since multisig accounts do not have private keys, they cannot directly use third-party applications like plugin wallets do. \
Mimir provides two interaction methods, allowing multisig users to directly interact with third-party applications (e.g., Uniswap, AAVE, etc.).

{% content-ref url="/pages/Yg2Bn2BFdc6FGQGdCaXS" %}
[WalletConnect](/guide/connect-to-dapps/walletconnect)
{% endcontent-ref %}

{% content-ref url="/pages/jqCN7uosw9ba9YyooMtp" %}
[Apps](/guide/connect-to-dapps/apps)
{% endcontent-ref %}


# WalletConnect

Mimir supports connecting multisig accounts with other Dapps via Wallet Connect. As long as the Dapp supports Wallet Connect login, you can log in and perform various operations with your Mimir multisig account.

### **Step 1**&#x20;

First, open the Dapp you wish to log in to with your multisig account, such as Uniswap, and select WalletConnect as the login method:

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2F8B4dOChBKiXA1ttLqPRE%2Fimage.png?alt=media&amp;token=9b7f585f-d946-46ae-be75-15b5ecdb65cd" alt="" width="360"><figcaption></figcaption></figure>

### **Step 2**&#x20;

In the WalletConnect page, click the copy button to copy the Pairing Key.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FKpkvPfgJTPuecB27Lg4U%2Fimage.png?alt=media&amp;token=e6e0d274-9fef-4e44-badf-45da24efa515" alt="" width="346"><figcaption></figcaption></figure>

### **Step 3**&#x20;

In Mimir, click the WalletConnect button on the top bar, paste the Pairing Key, and click Confirm.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2F7uE8IYMi8eNDoWEq1Ysf%2Fimage.png?alt=media&amp;token=3cca4ed6-144f-4d1e-b7e3-8833bc3859d7" alt="" width="350"><figcaption></figcaption></figure>

### **Step 4**&#x20;

Verify that the Dapp information is correct. If everything is correct, click Approve. Ensure that the network selected in the Dapp matches the network of the multisig address.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2Fi7F9LsFJg6lsPjIvcSKs%2Fimage.png?alt=media&amp;token=1c559dd7-4ef8-4207-9157-c600506d254d" alt="" width="375"><figcaption></figcaption></figure>

### **Step 5**&#x20;

After initiating a transaction in the Dapp, return to Mimir to review and sign the transaction. Once signed, the transaction will be successfully initiated, and the subsequent steps are the same as for a normal transaction.


# Apps

After entering the application interface, you will see a list of available applications.&#x20;

## Listed Apps

Click on an application to enter its interface. \
Once inside, you will find that you are already logged into the application with your multisig account.

## Unlisted Apps

Some applications, although they support Safe's SDK, are not listed.

You can add these applications manually by clicking the add button in the Customized Apps section and entering the application's address. If the application supports Safe's SDK, you can start using it directly.


# Batch Transaction

When performing operations like bulk transfers, users prefer to bundle transactions into a single batch rather than sending them one by one to save on gas fees. The Cache Transaction feature helps you achieve this.

You can see the "Add to Cache" button when initiating any transaction.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FYW7cjkoW0ZuqOXVL5PD3%2Fimage.png?alt=media&amp;token=44cadcf4-8251-4ff7-a11d-b6f1f649a784" alt=""><figcaption></figcaption></figure>

Clicking it will add the transaction to the Cache queue.

Click the Cache button to expand the sidebar with the Cache transaction queue.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FMpR2RtrVDI8sNfB1R3Jf%2Fimage.png?alt=media&amp;token=45357630-ee0b-4f63-8555-e1edbf0a5e80" alt=""><figcaption></figcaption></figure>

You can sort, delete, add, and select transactions here.&#x20;

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2F1vzOA8MRqHyN9uHygWOP%2Fimage.png?alt=media&amp;token=27c50c80-ec7f-4352-8143-ffa408d20967" alt=""><figcaption></figcaption></figure>

After selecting the transactions, click Confirm Cache to bundle them into a single transaction and send it.

## Follow Transaction

If you see someone else's transaction and want to repeat it, you can use this feature by clicking **Add New**.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FTf2SnuZRVT3Onkdq7WNh%2Fimage.png?alt=media&amp;token=b0f44146-2c1a-4c56-8742-fbb0032972af" alt=""><figcaption></figcaption></figure>

Then, you can paste transaction hash or explorer link to copy transaction.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FNbiJYXzfIZY2si47nyIc%2Fimage.png?alt=media&amp;token=7a19957c-392e-45c7-b122-f496379bc470" alt=""><figcaption></figcaption></figure>


# Set Policy Rules

Setting Policy Rules allows your account to have a more flexible structure and a higher level of security. You can click on Policy Rules in the sidebar to enter the settings page.

Currently, we offer the following two Policy Rules for configuration:

{% content-ref url="/pages/SJycY0d03BxPmbWQB5ju" %}
[Set Recoverer](/advanced/set-policy-rules/set-recoverer)
{% endcontent-ref %}

{% content-ref url="/pages/3tFy4EiRvpLZuoVKihEB" %}
[Set Easy Expense](/advanced/set-policy-rules/set-easy-expense)
{% endcontent-ref %}


# Set Easy Expense

## 1. **Setting Easy Expense**&#x20;

After selecting a multisig account, go to the multisig account settings page and choose the Easy Expense tab to configure Easy Expense. You need to set three parameters:

* **Beneficiary**: Enter the address of the beneficiary. The private key holder of this address will benefit from the Easy Expense limit.
* **Token Limit**: Specify a token and its limit, which is the maximum amount the beneficiary can use without needing signatures.
* **Reset Time**: The period after which the Token Limit resets. If set to "Once," the limit will not reset after it is used up.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FQSWg9l4qmjJGm05bInAM%2Fimage.png?alt=media&amp;token=d504a927-e6b5-4543-916a-be3369d4cedb" alt=""><figcaption></figcaption></figure>

## **2. Using Easy Expense**&#x20;

The private key holder of the beneficiary address can open the Mimir page for the multisig address and click the Transfer button on the homepage.&#x20;

The beneficiary can then toggle the Use Easy Expense switch to use the Easy Expense limit for the transaction. The transaction will be executed immediately and will not use a nonce.

## **3. Deleting Easy Expense**&#x20;

If you want to delete an Easy Expense, go to the account settings under Easy Expense, find the previous settings record, and click the delete button. This will initiate a transaction that needs to be approved and executed by the required number of members to be officially deleted.


# Set Recoverer

## 1. **Setting Recoverer**

After selecting a multisig account, go to the multisig account settings page and choose the Recover tab to configure the Recoverer. You need to set three parameters:

* **Recoverer**: Enter an address that can initiate an account reset Proposal. Each multisig account can only have one Recoverer, so choose a trusted partner to avoid losing funds.
* **Review Window**: Select a period during which, after the Recoverer successfully initiates a reset Proposal, the multisig account can initiate a cancellation operation. If the cancellation is approved, the Recover Proposal becomes invalid.
* **Expire Period**: Select a period. If the Recover Proposal is not canceled after the Review Window, the account reset transaction must be executed within the Expire Period after the Review Window ends; otherwise, the Recover Proposal becomes invalid. Setting a Recoverer requires approval and execution by the required number of members before it can be officially used. There can only be one Recoverer.

<figure><img src="https://951185950-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfYktjzAQubX4SAAWG6sc%2Fuploads%2FN3DiZY4qT5EAlSqJGz7u%2Fimage.png?alt=media&amp;token=dc8917ec-be9e-430d-9b89-d5a2e8227054" alt=""><figcaption></figcaption></figure>

## **2. Initiating Recovery**&#x20;

If there is a security risk with your account members (though we hope this never happens), the Recoverer can go to the homepage of the address, where a prompt will indicate that the Recoverer can initiate a reset Proposal.&#x20;

Upon entering, the Recoverer can reconfigure the members and the threshold of the multisig account.&#x20;

After completing the configuration, click submit to enter the Review Window stage.&#x20;

If a user wants to oppose the reset, they can find the transaction in Pending Transactions and initiate a cancel transaction. If the cancel transaction is successfully executed, the Recoverer Proposal will be canceled.&#x20;

If no one opposes during the Review Window, the user needs to execute the transaction before the Expire Period ends to officially modify the account members and threshold configuration.

## **3. Deleting Recoverer**&#x20;

If you want to delete the Recoverer, go to the account settings under Recover, find the previously set Recoverer, and click the delete button. This will initiate a transaction that needs to be approved and executed by the required number of members to be officially deleted.