What Is MAP Protocol (MAP)?
MAP Protocol Since the birth of the Bitcoin in 2009, thousands of public chains have been produced by using blockchain technology and those are widely used in multiple application fields such as IoT, finance, governance, identity management, and traceability. In the early 2010s, there are only few blockchain. And the terminology blockchain inter operation mostly refer to the cross-chain technology of transferring coins between these blockchains.
In 2016, Vitalik Buterin summarizes the ways of reaching interoperability into three primary categories of strategies. Hash locking setting up operations on two chains with the same trigger, e.g., the preimage of a particular hash. Centralized or multisign notary schemes where a party or a group of parties agree to carry out an action on one chain should some event on another takes place. Side chain/relays. where one blockchain can validate and read events and/or state in other blockchains.
MAP Protocol Storage Key Points
|Coin Name||MAP Protocol|
|Circulating Supply||1.76B MAP|
|Source Code||Click Here To View Source Code|
|Explorers||Click Here To View Explorers|
|Twitter Page||Click Here To Visit Twitter Group|
|Whitepaper||Click Here To View|
|Official Project Website||Click Here To Visit Project Website|
Accompanied with cryptographic
MAP Protocol Analogously, chain interoperability means one blockchain (active chain) can read/write to another blockchain (passive chain). Most current chain interoperability solution suggest using SPV technology for cross-chain read. By reading with SPV technology, all information is accompanied with cryptographic proof and the receiver need a way to get “trusted” or “real” block header of the corresponding chain. In this way, the receiver can verify the cryptographic proof against the info contained in the “trusted” header.
In the cross-chain write scenario, the receiver is the passive chain. If the passive chain can verify that certain things happened on the active chain, it can change its on-chain state to respond to such awareness. Of course, any state changes on the passive chain must be triggered by valid transaction. In this context, someone must construct a
valid transaction containing the things happened on the active chain as well as the related cryptographic proof and submit the transaction to the passive chain. Once this transaction is committed to a confirmed block of passive chain, the cross-chain write is complete.
MAP Protocol Then another problem pops up, how can the passive chain get the aforementioned “trusted” block header of the active chain? Some solutions introduce “the trusted relayer” to guarantee the truthfulness. Once again, to maintain the trust less property of MAP protocol, we don’t take this road, but employ a dedicated blockchain – MAP chain – to maintain light clients of all interested blockchains.
The validator on the relay chain
MAP Protocol defines a complete cross-chain interoperability underlying protocol. It has a complete cross-chain read and write specification, and through this protocol, it built a complete cross-chain interoperability ecosystem. The characteristic of Polkadot is to communicate and coordinate the cross-chain interoperability of all para chains through a relay chain. The validator on the relay chain will be allocated to each para chain to work with its collator, and the para chain block header provided by collator will be synced to the relay chain.
After that, the XMCP protocol  is used to transfer cross-chain messages. Of course, the cross-chain status needs to be obtained through the SPV solution after obtaining the block header from the relay chain, and the cross-chain write operation needs to be customized through the para chain. The smart contract system parses the specification information defined by XMCP and executes it.
Map protocol aims
MAP Protocol aims to be the secure end-to-end solution for any blockchain resident to move and exchange assets. The chain itself can achieve lightweight arbitrary interaction without the need to relay through a relay chain under the independent self-verified consensus mechanism. And for the non-independent self-verified consensus mechanism, the chain can achieve lightweight arbitrary interaction through the relay anchoring mechanism.
The reason for the difference here is that blockchains of independently self-verified consensuses (e.g., POW, POS, etc.) can independently verify the legitimacy of individual blocks. However other consensus mechanisms such as DPOW, DPOS, which need to be anchored to other relay chains because additional electoral representation information is required to verify the legitimacy of blocks.