The design and structure of the omnichain solution system that MAP Protocol designs is unique in a way since it features three different layers. These are the MAP Protocol Layer (Relay Chain), MAPO Service (MOS) Layer, and MAP Application Layer. These three layers function concurrently to provide the seamless experience to the users for all cross-chain transactions.
As a trader and multi-chain supporter myself, solving the cross-chain dilemma requires a well-planned and well-structured framework. This is because of the following:
- Each blockchain network has its own block time, TPS (transactions per second), and block height.
- Not all blockchain networks have the same consensus algorithms. The most common types are Proof-of-Stake (PoS) and Proof-of-Work (PoW).
- Not all blockchains are EVM-compatible. EVM-compatible networks have full support for smart contracts originally created for Ethereum and is now being widely used by chains like Polygon, Binance Smart Chain, and Avalanche.
- Not all blockchains have the same gas fees.
Now, we will briefly explain the three layers in the simplest and not-so-developer way so we can fully understand how the overall MAP Protocol omnichain design works and how interesting its design is.
MAP Protocol Layer
In this layer, we can find the MAPO Relay Chain, the base of all transactions in the MAP Protocol ecosystem. We discussed earlier that not every blockchain are the same, so MAP Protocol needs some kind of software or system that connects it to all those different blockchain networks. The answer is the MAPO Relay Chain and it’s made up of Light Clients.
What are Light Clients? These are also called light nodes in other places and their purpose is to read and transmit newer data (in technical terms, blocks) across a blockchain. Light clients of different chains are “installed” in the MAPO Relay Chain and light clients of MAPO are put in those different chains in return. This connects MAP Protocol to those networks. For example, when light client of Ethereum receives new data, it is also transmitted to the Ethereum light client installed here in MAPO Relay Chain. When the light client of MAPO Relay Chain updates, all MAPO light clients set in the other blockchains update as well. This is to ensure that everything is updated and synced with each other.
Keyword for MAP Protocol Layer/MAPO Relay Chain: Connectivity with other blockchains, intercommunication
MAPO Services Layer
All information transmitted to the MAPO Relay Chain can be found in this layer. That is why in this level, for each connected chain (MAP Protocol and the other networks), there are installed systems referred to as “Vault and Data”.
Vault and Data are this layer’s most important part. We can think of it as the sender/receiver of information for this layer.
When you transfer a token to a different chain, the Vault part of the chain you are sending from will be activated to start the transaction. On the other hand, the Vault from the receiving chain will be activated as well to receive the transfer.
The same scenario will happen when you make a transaction other transfer of assets, the Data part from the sending and destination chains will be triggered to send and receive the transaction respectively.
Keyword for the MAPO Services Layer: Interoperability between the chains; transfer of data and assets
MAPO Application Layer
In a nutshell, this is the layer where we can find and access the dApps on MAP Protocol. We can access all applications that are created on the MAP Protocol and even the ones from other chains, that are integrated with the modules necessary to be omnichain-ready.
Keyword for the MAPO Application Layer: Applications, Interact
Conclusion
Here in this article, we’ve learned a quick overview about the three layers of MAP Protocol, what they are primarily for, and what we can find in each of the layers. We’ve also given keywords for each layer so we can find it easier to get familiarized with these over time. There’s some interesting things to go through further but we’ll save that for another article in the next day.
Follow Map Protocol in the following channels:
Website: https://www.mapprotocol.io/
Twitter: https://twitter.com/MapProtocol
Discord: https://discord.gg/VTcWVPHcTq
Telegram: https://t.me/MAPprotocol
Check my other articles about MAPO:
https://gnonin.medium.com/quick-glance-on-the-map-protocol-website-website-review-cff895c5f8c6
https://gnonin.medium.com/the-three-grants-of-map-protocol-and-where-to-get-them-f4e69c5ec180
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
Gnonin
Into #crypto and #Web3 || Loving Testnets and #airdrops || Long-term Investor doing Day Trades || Ambassador and Community Manager || Exploring Crypto Twitter, Discord, and Telegram 24/7
Find me on: Twitter || Telegram || Instagram || LinkTree
Discord: gnonin#5490 || Business E-mail: gnonin.gg@gmail.com
