MAP Protocol: The Omnichain Network for An Interoperable Web3

[MAP-ED-VC]

MAP Protocol

Grant category

Please select one or more of:

• [ ] Open source maintenance
• [x] Developer tools / services
• [ ] Educational material

Description

MAP Protocol is the omnichain network for an interoperable web3 world. MAP Protocol provides the underlying infrastructure for converting single chain dApps into omnichain dApps with two easy steps: 1) Build inter-chain messenger using MAP's SDK 2) Interact with on-chain vault and data through MAP's API.

MAP Protocol stands as the only omnichain network with the following advantages:

• Security-Finality: Guarantee blockchain-level security through an independent self-verification network formed by light clients on every public blockchain.
• All-Chain Coverage: Embed heterogeneous chains' signing and hashing algorithm into the EVM layer of the MAP Relay Chain to ensure seamless communication between all chains.
• Instant Confirmation: Inter-chain communication programs and on-chain smart contracts work together efficiently to ensure that speed is only related to each chain's block time.
• Minimum Cost: MAP Protocol only charge the gas fee of MAP Relay Chain and other related chains with no additional cost.
• Developer-Ready: Through MAP Omnichain Service (MOS) deployed on and between public chains, dAPPs can share the liquidity of MOS's Vaults on different chains, and customize the entry threshold and incentive model of inter-chain program: messenger. Alternatively, we can use the MOS open source code to build dAPP-related Omnichain components.

Problem statement

• Target audience
  • dApps on other EVM and non-EVM chains that would like to expand to Flow ecosystem
  • Flow developers who would like to build omnichain dApps on top of MAP Protocol's technology
  • Residents from other chains that would like to join the Flow ecosystem
• Evidence for the need
  • There are many cross-chain solutions in the market, but most solutions focus on solving one of the following problems: security, gas efficiency, or confirmation speed. None of the solutions is a one-for-all protocol satisfying all three needs.
  • EVM <> EVM chain interoperability protocols are abundant, but EVM <> non-EVM solutions have high complexity and poor security.

Proposed solution

Architecture

MAP Protocol uses a three-layer approach to solving the ominchain interoperability problem: MAP Protocol Layer, MAP Ominichain Services Layer(MOS), and Application Ecosystem Layer. 1. MAP Protocol Layer MAP Protocol Layer constructs the CORE of the omnichain network infrastructure: Verification Finality Network. It consists of MAP Relay Chain, Light-Client deployed on each chain, and inter-chain Maintainer Program to update and maintain Light-Client status.

• MAP Relay Chain proactively extends and supports heterogeneous blockchains' features in virtual machines, which construct a gas-efficient Light-Client verification network.
• Light-Client deployed on each chain has the characteristics of independent self-verification and verification finality, which becomes the verification network for cross-chain assets and data.
• The Maintainer is an independent inter-chain program responsible for updating the status of Light Clients. The mechanism of the Light-client assures the invalidity of malicious attacks from maintainer.

2. MAP Omnichain Services Layer (MOS) MAP Omnichain Services Layer facilitates dApp developers to build applications, similar to Google Mobile Services. It consists of Vault and Data deployed on each chain, and Messenger Program to transmit messages between chains.

• Vault and Data contracts are deployed on each chain, developers can utilize Vaults and Data in MOS and share Vaults and Data liquidity with other applications.
• Messenger Program is an SDK deployed, operated, and maintained by dApp developers. DApp developers can also independently and flexibly incentivize messenger contributors for transmitting cross-chain messages for the dApp.

3. Application Layer DApps can achieve interoperability using MOS. The finality of cross-chain data and asset verification network by MAP Protocol Layer empowers DApps to grow limitless.

Impact

• In what ways does this benefit the broader Flow developer ecosystem? 1) Connecting Flow with all EVM and non-EVM chains securely with blockchain-level security of MAP Protocol. 2) Flow’s developer can build an omnichain application directly or upgrade their existing single-chain application to an omnichain application effortlessly through MAP’s SDK and API. 3) Omnichain network allows residents from other chains to participate in Flow’s ecosystem, which drives new traffic and assets to Flow.

Milestones and funding

Note: You can leave the USD proposal empty / "TBD". Please consider adoption and/or maintenance milestones at the end of your project.

Milestone	Deliverables	Timeline	Risks	USD proposal
1 - Light Client and Transaction Verification	a. Flow Light Client, written in Solidity, will be deployed on EVM chains. Through Flow Light Client, smart contracts on EVM chains can easily verify transaction vailidation on Flow. b. BN254 Contract on Flow, support addtion and scalar multiplication ont the elliptic curve BN254. It is importante for verifying zkSNARKs and aggregate signature. c. MAP light client on Flow, witten in cadence. d. Maintainer program, update chain status between Flow and MAP Relay chain.	2 months	-	$40K
2 - MOS	a. Omnichain service contract on Flow, archive interoperability between Flow and other chains. b. Messenger program, transmit the cross-chain message between Flow and MAP Relay chain.	2 months	-	$25K
3 - SDK	Provide SDK, support for developes to interact with other chains.	1 months	-	$10K

Team

Name	Role	Bio	Contact
James Cheng	Co-founder	Serial Entrepreneur. Previously built successful Fintech and SaaS companies. Part-time Blockchain researcher in Tsinghua University during 2018-2020. Crypto native since 2017.	james.cheng@maplabs.io
Frank Wen	Chief Architect	PhD in Cryptography. Former Core Developer of Bitcoin Cash. Former Blockchain Researcher at Bitmain and Matrixport. 6 years of R&D experience in DeFi and underlying layer of blockchain.	frank.wen@maplabs.io
Phil Lau	Head of Engineering	Graduated from Tsinghua University. Board Member of the Technical Board of IEEE Computer Society Blockchain and Distributed Ledger Standards Committee, responsible for reviewing IEEE blockchain technology standard. * 5 years R&D experience in underlying layer of blockchain.	phil.lau@maplabs.io
Michelle Law	Chief Operation Officer	Graduated from The Hong Kong University of Science and Technology. Former Investment Banker and lawyer on global capital markets. 7 years of Investment banking and project management experience. 2 years experience of operation and business development in blockchain industry.	michelle.law@maplabs.io
Moore Li	N.A. Tech Lead	Graduated from University Of Waterloo. Previous Senior Software Engineer at a machine-learning company - RSVP, originated from Tsinghua University and the Artificial Intelligence Laboratory of University of Waterloo. * 3 years R&D in underlying layer of blockchain and DeFi.	moorelee@maplabs.io

[alxflw]

thanks for the submission @MAP-ED-VC! we'll review and get back to you soon

[alxflw]

hey @MAP-ED-VC: the emails in the table aren't reachable it seems - could you please share an email that I can use to discuss some details? thanks!

[MAP-ED-VC]

Hello @alxflw, feel free to send your questions to vincent@maplabs.io

[chrisackermann]

Hello @MAP-ED-VC! Thanks for your patience, I wanted to let you know that we've accepted your proposal and will be following up over email on next steps. In the meantime, please update the milestone table in the proposal here to reflect the USD amounts against the milestones.