# Developer Docs

Welcome to the MAP Protocol developer documentation. This documentation is designed for advanced developers who want to understand the technical details of MAP Protocol's cross-chain infrastructure.

## What is MAP Protocol?

MAP Protocol is a peer-to-peer cross-chain infrastructure that enables secure and decentralized interoperability between heterogeneous blockchains. It provides two complementary cross-chain solutions:

* **Protocol 2.0**: TSS (Threshold Signature Scheme) based decentralized custody
* **Protocol 1.0**: Light client-based trustless verification

## Documentation Structure

### [Overview](https://mapo.gitbook.io/dev-docs/overview/introduction)

Introduction to MAP Protocol, architecture overview, and comparison between v1 and v2.

### [Protocol 2.0](https://mapo.gitbook.io/dev-docs/protocol-2.0/overview)

TSS-based cross-chain solution: architecture, maintainer roles, TSS mechanism, MStack, cross-chain flow, gas mechanism, security, and slashing.

### [Protocol 1.0](https://mapo.gitbook.io/dev-docs/protocol-1.0/overview)

Light client-based cross-chain solution: light client design, MOS layer, and chain integration guides.

### [Relay Chain](https://mapo.gitbook.io/dev-docs/relay-chain/architecture)

MAP Relay Chain (Atlas) technical details: architecture, consensus mechanism, genesis contracts, and precompile contracts.

### Fundamentals

Core blockchain and smart contract concepts:

* [Blockchain](https://mapo.gitbook.io/dev-docs/fundamentals/blockchain/accounts): accounts, transactions, blocks, gas, MPT, RLP, oracle
* [Smart Contracts](https://mapo.gitbook.io/dev-docs/fundamentals/smart-contracts/evm): EVM, development, testing, security

### Appendix

* [BTC Layer2](https://mapo.gitbook.io/dev-docs/appendix/btc-layer2/overview): BTC Layer2 and BRC-201

## Quick Links

| Topic                                                                                        | Description                 |
| -------------------------------------------------------------------------------------------- | --------------------------- |
| [Architecture](https://mapo.gitbook.io/dev-docs/overview/architecture)                       | Overall system architecture |
| [v1 vs v2](https://mapo.gitbook.io/dev-docs/overview/v1-vs-v2)                               | Comparison of two solutions |
| [TSS](https://mapo.gitbook.io/dev-docs/protocol-2.0/tss)                                     | Threshold signature scheme  |
| [Light Client](https://mapo.gitbook.io/dev-docs/protocol-1.0/light-client/overview)          | Light client design         |
| [Consensus](https://mapo.gitbook.io/dev-docs/relay-chain/consensus/pos)                      | Proof of Stake consensus    |
| [Genesis Contracts](https://mapo.gitbook.io/dev-docs/relay-chain/genesis-contracts/overview) | Genesis contract design     |

## For Users and Operators

If you're looking for:

* Node operation guides
* API/SDK usage
* Running Compass-TSS

Please visit the [User Documentation](https://github.com/mapprotocol/developer-docs/blob/dev-docs-en/docs/README.md) instead.

## Contributing

We welcome contributions to improve this documentation. Please submit issues or pull requests to our GitHub repository.

## Resources

* [GitHub](https://github.com/mapprotocol)
* [Website](https://mapprotocol.io)
* [Discord](https://discord.gg/mapprotocol)


---

# Agent Instructions: 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:

```
GET https://mapo.gitbook.io/dev-docs/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.