# MAP Protocol

> Omnichain infrastructure for BTC, stablecoin, and tokenized asset swap

MAP Protocol is a cross-chain interoperability protocol for swapping BTC, stablecoins, and tokenized assets. It uses light client verification and MPC-based threshold signatures to connect Bitcoin with multiple blockchain networks.

MAP Protocol is a cross-chain interoperability protocol that provides infrastructure for swapping Bitcoin, stablecoins, and tokenized assets across blockchain networks. It connects the Bitcoin network with EVM and non-EVM chains, allowing value to move between ecosystems without relying on a centralized intermediary. The protocol targets developers building cross-chain applications as well as users who want to move assets such as BTC and stablecoins between networks.

The protocol addresses the trust and security challenges common to bridging solutions by combining light client verification with a multi-party computation based threshold signature scheme. Light clients verify transactions from the source chain in real time, while validators collectively manage the signing process used to lock and release assets, reducing reliance on any single party. This architecture is built around an EVM-compatible relay chain paired with omnichain service middleware that coordinates cross-chain requests.

Beyond its core swap infrastructure, MAP Protocol offers developer tooling, including software development kits and standard interfaces, for building applications spanning decentralized finance, payments, and tokenized real-world assets across multiple blockchains. Its native token, MAPO, is used within the network for staking and other protocol functions. The protocol is used by developers building omnichain applications and by validators and node operators supporting the network.

- Type: Protocol
- Sector: Infrastructure
- Status: Active
- Founded: 2022-08-31
- Profile: https://thegrid.id/profiles/map_protocol

## Products

- [MAP Protocol](https://thegrid.id/profiles/map_protocol): MAP Protocol is cross-chain infrastructure for peer-to-peer BTC, stablecoin, and tokenized asset transfers across EVM and non-EVM blockchains. The protocol uses light client technology to verify source chain transactions on-chain and an MPC-based threshold signature scheme (TSS) to secure cross-chain asset custody without trusted third parties. Its architecture consists of three layers: the MAP Relay Chain as the relay hub and verification center, MAP Omnichain Service (MOS) for cross-chain messaging and asset transfers, and an application layer for omnichain dApps. Supported networks include Ethereum, BNB Chain, Polygon, Arbitrum, Base, NEAR, Solana, and Tron. Bitcoin network security mechanisms reinforce the relay chain against long-range attacks. (Cross-chain Infrastructure, Live, Main Product)
- [MAP Relay Chain](https://thegrid.id/profiles/map_protocol): MAP Relay Chain (Atlas) is an EVM-compatible proof-of-stake blockchain using Istanbul BFT consensus with ~5 second block times and instant transaction finality. Operating with Chain ID 22776, it serves as the relay hub and verification center within MAP Protocol's architecture, hosting light client contracts for connected blockchains and TSS contracts for cross-chain asset custody. MAPO is the native gas and staking token. Validators must stake a minimum of one million MAPO to participate in block production, with users able to delegate stake to active validators. (L1, Live)

## Assets

- [MAPO (MAPO)](https://thegrid.id/profiles/map_protocol): MAPO is the native token of the MAP Relay Chain, MAP Protocol's EVM-compatible cross-chain infrastructure network. It is used for paying transaction fees, securing the network through staking, and participating in DAO governance. The relay chain uses Istanbul BFT consensus with instant finality and applies Bitcoin's security mechanisms to protect against long-range attacks. (Native)

## Links

- [Main](https://mapprotocol.io)
- [Documentation](https://docs.mapprotocol.io)
- [Blog](https://www.mapprotocol.io/blog)
- [Whitepaper](https://files.mapprotocol.io/pdf/mapprotocol_whitepaper_en.pdf)
- [Forum](https://forum.mapprotocol.io)
- [Governance](https://forum.mapprotocol.io/c/governance/6)
- [Media Kit/branding](https://mapprotocol.io/brand-assets)
- [Terms of Service](https://forum.mapprotocol.io/tos)
- [Privacy policy](https://forum.mapprotocol.io/privacy)
- [Twitter / X](https://x.com/MapProtocol)
- [Telegram](https://t.me/MAPprotocol)
- [Medium](https://medium.com/mapprotocol)
- [YouTube](https://youtube.com/@MapProtocol)
- [GitHub](https://github.com/mapprotocol)

## Legal

This data is provided under two licensing models.

Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation.

Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service.

The following applies to both licensing models.
- All data is provided AS IS with no guarantees of accuracy.
- The Grid does not provide investment, legal, or tax advice, and
- a project's presence in The Grid's data does not imply endorsement.


- [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers
- [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service.
- [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service.
- [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services.
- [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures

## Optional

- [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model
- [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships
- [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type
- [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types
- [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP