> For the complete documentation index, see [llms.txt](https://midl.gitbook.io/midl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://midl.gitbook.io/midl/users/supported-wallets.md).

# Supported Wallets

Midl supports integration with popular wallets to provide users with seamless interaction using their preferred Bitcoin wallets. Currently, Midl supports:

●   Unisat.

●   MetaMask (via BTC Snap).

Requirements for wallet integration:

For wallets to support Midl and be added to our frontend app connectors, they must meet the following requirements in addition to basic Bitcoin network functionalities:

1\.  Signature support:

●   Ability to support secp256k1 signatures.

2\.  Transaction handling:

●   Capability to read and broadcast transactions on Testnet V4

3\.  Runes support:

* Taproot address generation: Ability to generate Taproot addresses.
* Runes balance indexing: Index the Runes balance of public addresses.
* Runes transfer: Enable the transfer of Runes.

4\.  Message signing:

* Implement the signMessage() function for BTC wallets using the BIP322 format.

Future support:

* Ledger: Integration with Ledger hardware wallets is planned for future updates to expand wallet compatibility.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://midl.gitbook.io/midl/users/supported-wallets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.