# 2. System

**2.1. Philosophy:**

The goal of MetaPath is to realize the interconnectivity of blockchain ecosystems where users can reliably circulate any digital assets. Essentially, the connectivity of blockchain ecosystems accounts for the integration of smart contracts deployed on different platforms. As the building blocks of blockchain functionalities, reliable communication across different chains depends on the messaging mechanism, eventually the global consensus concerning smart contracts.

![https://lh6.googleusercontent.com/jsQddMRg35YbWQJ2Xjz-ktL4SGcl3MGdRwBuKw0tDbKzgd1wT9mK0AJZP0jli03bVsB4eoBuXJpfOeE0MmVmagJDNQeaY4EnMiP8GiMrusMLx6gxLRIDe6MvcfqzPt5GPQ=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FRIrXpsjFLrYlU2qmhvsk%2F1?alt=media)

MetaPath aims to design an inter-chain smart contract communication protocol where abundant resources will be provided to developers including APIs, documentation, and community support. By following the smart contract communication protocol, developers will be able to create DAPPs achieving inter-platform unity. To be specific, MetaPath designs and implements the interface standard of a communication protocol, which is compatible with various existing asset standards among different blockchains including ERC20 and ERC721. By importing the MetaPath contracts messaging standard, smart contracts of token or NFTs would be able to transfer their assets freely across platforms by invoking the registration and updating mechanism on the MetaPath chain.&#x20;

With the implementation of the MetaPath protocol,

* Users will be able to purchase NFTs with any token possibly from different blockchains as long as the MetaPath smart contract routing protocol is implemented on the smart contract of the token.
* Pairwise exchange of NFTs will also be supported.
* Also supported are the across-chain consensus of operation messages. Desired characteristics include low costs and high speeds, across devices, openness, decentralization, accessibility, etc.

We separate the implementation of MetaPath into two (2) stages.

**2.2. Current Stage:**

**2.2.1. Architecture**

We are archiving MP-Routing-Agent (MPRA) of the mainstream marketplace and swap platforms in a semi-centralized way. MPRA helps users accomplish the exchange transactions of Any-Token-To-Any-Token and Any-Token-To-Any-NFT in a reliable, efficient way. In the meantime, MPRA will build a full path-directed graph and find the optimal option for users according to tokens and amounts.

* The below is the system architecture of the current stage.

![https://lh4.googleusercontent.com/bU8sLtPxpCsUOiZYl5fORNCJwcj\_stGn\_1EjSO8kmjlbtKQrSVdYQb-tc9jEc7bEDALu2EQLFL1\_h-7xcsbVamwqvaGVLB-hBZTlIW-SUzDKHWmKCp7q3aLVW1X5VpouDQ=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FIUhWlvYfkWnGySlQdInr%2F2?alt=media)

**2.2.2. Web3.0:**

While the Web3.0 era has arrived, MetaPath designed a kind of smooth pattern to adapt to Web3.0. MetaPath opens up application interfaces and reward policies to third-party wallets and traffic platforms, to encourage more and more third-party platforms to join MetaPath.

In technical terms, MetaPath has deployed proxy contracts on each target chain to execute user transaction requests, and the execution of proxy contracts is adopted to "call" mode.&#x20;

**2.2.3. Achievement:**

* Until now, MetaPath has integrated mainstream swap platforms and NFT/GameFi marketplace, such as Uniswap, 1inch, Axie, Opensea, etc. The proxy contract has been deployed on all main chains.

![https://lh6.googleusercontent.com/tLnkw6Xy\_Y\_rOyc8AQlppbkEb8-CkzBDd2HzhnyS6VNH4wGi4aFooLg6dhNzsLS-vZLnAuAgG\_JK87uQd4znD3M3re4ZnAc3xTO0NzrxMpKsXL2G7vKywqCNP-VLTx6JDg=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FGFz6LuGBvdpw3hrGYgrM%2F4?alt=media)

**2.2.4. Screenshot Show:**

[Any-Token buys NFTs. Please click to visit  MetaPath](https://www.google.com/url?q=https://www.google.com/url?q%3Dhttps://paths.finance%26amp;sa%3DD%26amp;source%3Deditors%26amp;ust%3D1642596251758666%26amp;usg%3DAOvVaw0b0b-hjqAzqvKjaXq2IuzE\&sa=D\&source=docs\&ust=1642596251794597\&usg=AOvVaw2JIAYL_KBKEwtqu-olKWSR).

![https://lh3.googleusercontent.com/\_N-YZpRo8V2fVgQPwUfm4ofiPEvXyVfBX2L39aeN-DYndN5W6gZwQCa4RPs2TeXTrKpy8ongpP\_znftXwcpRfrnt2aLOcTAFKiqL1dVgQNOyYN0yllZ2PsHU180aoiFR5g=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FoUC2dlTqEY5HGsh6YCEh%2F1647380991333.jpg?alt=media\&token=575f3738-58ae-4f0c-b21d-79b914062516)

![https://lh6.googleusercontent.com/t8Hu4CMlL6GFe7dpX84265EltjHpvmpE3AZAnev0-IbrnPMUUh3EAQPtET2JFVozB\_3FyxsvYtPBvAx5ID707c4Tb4UyIg5aT1SAG260sXmMOfqTo4k8Z\_KVtD1J-rgvxg=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2F0HPfPuMxeoXftKpRdb1K%2F6?alt=media) ![https://lh4.googleusercontent.com/9\_yBgqDMAjUXugtx82ZQ3VZzsJLxK2DZNy3Fh5CwSQvUIF6zn3Y5ILnNteZo4\_5--RDR6TvN3suvEhi3EpVYd2qdWL9\_D-V4WXkhzmRmllHpfrdla2QStfI7BqJa2hQAxQ=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FLv4VUTy5vtO5A1UfgnZ4%2F1647381235264.jpg?alt=media\&token=2cd8eace-e1bc-4214-9f39-6e1bb272b7f9) ![https://lh4.googleusercontent.com/9ixXWK8ZtLxfaERRck9zTrbdrDyhpKfa0Vm5qjTW3MWPeGjQAiSawxsfza2JPrOjY2AJQtXUW7aWJ4skcYaV6eXqrjrJ2oyjfp263O8uWMfiJErbCKIPDme\_9uXqv4nN3w=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FWir4uqjA2kSUVVkbOP4E%2F8?alt=media)

![https://lh6.googleusercontent.com/uID9wvh9fhM5hFaRRXEk-Z-4unfqysUD6Hi5ZBK0lbFg5BLcHRVrB0qdOA5Vcn3eq8ZL5SEOAqQXhxB85nHCzyNRZ7DcM7nRaXeBvr7m4IvnLCoTC9sJOBBZrBT0mO2q6A=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2Fjyq2taUOVv1PFm2IRqY5%2F1647381583389.jpg?alt=media\&token=530bb175-bc03-41e6-a7cd-ad4422efacb6) ![https://lh4.googleusercontent.com/orQP3F5PFWYTCeJ4aqkS\_W24Um-wuXieo4SR4\_8ZNr1UgHUYh44THVd2vZ1jvDdIpqr8lA85Q9em5QTKuI3anVfCK\_KDbT8Ow2Eg40MBGISl89eL8zhrPQjCOb3hIT\_0ng=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2Fm0k60LOlnYu5QP8hzwor%2F10?alt=media)

**2.3. Future:**

In the coming stage, we plan to make part of centralized MetaPath fulfilled with full decentralized technology. In general, the overall system structure in the future would be like the figure below.

![https://lh6.googleusercontent.com/5JGZWhyKw8yiI\_ICPojbD3vWee5NnyhNLsZ0z55UYHutOHh4KayrQ5ogLoritIrdrR-V0mOuX\_oyyINMpKHUTTtJS6lK4dZfulnM\_NPzW6vZ0E26w0GMk69x\_N\_8XYkTLw=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2F2TOGFGV2x0t2lgYmpUFy%2F11?alt=media)

As illustrated in the Figure above, MetaPath is composed of the **Grid-connected Contracts** (deployed on different platforms) and the MetaPath mainnet chain.

The smart contracts of most NFT and digital assets products of Metaverse and GameFi are deployed on mainstream public chains or Layer2 chains. MetaPath will design a family of messaging and routing protocols to enable smart contracts of different NFTs and digital assets, as well as other related contracts, to communicate and reach consensus regardless of the chain they are deployed on. Message routing is achieved by the MetaPath network.

MetaPath protocol proposes and implements a technical standard for any-chain nodes to connect to the MetaPath network incrementally and seamlessly. Nodes from various blockchains could support MetaPath routing functions and join the MetaPath network by embedding the protocol standards. The tokenomics are designed to encourage nodes to join the MetaPath network to boost the ecosystem where efficient connectivity among platforms is achieved. The figure below illustrates a node joining the MetaPath network by implementing the MetaPath protocol.

![https://lh4.googleusercontent.com/pNtGrixcW67j3aSExerD4lKntGV1ar6QFhgv2iZ7hR4rVBIHPrMsfkzKDf2ICXwUYwDhdC5B9R\_hbAjjJl1JZmHq5yU6OgLH9NTJWGjEE7t4VEuuWM6hC-TphrT2hFCYLg=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FBtGzabS2MfFM2LeepKzy%2F12?alt=media)

**2.3.1. Components:**

**Grid-connected Contract**

The standardized smart contract deployed on native Layer1 blockchains.

**MetaPath Chain Pack**

MetaPath Chain Pack (PCP) is the embedded protocol package. After adopting the PCP, users join their native blockchain as well as the MetaPath chain by forking.

A PCP is an open-source implementation of the MetaPath core protocol stacks. Third parties could join the MetaPath network by forking or developing their own PCP.

![https://lh3.googleusercontent.com/IcMir2WV3XyGs0gvilHtj6Es8PvLd\_1jko1f1qMHfKm3uQHqJHJZxAGDHTek01yToWMzUOes24nFQx2W9wT\_51TCfEDI93yJl721HDKU9DbrmZz9Aww3GjjnX0un95t-Zg=s800](https://2206151930-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0IiInwiM4M18NK0ZFzYk%2Fuploads%2FV3AFuHqOZ5cLvqZBHi8i%2F13?alt=media)

**MetaPath Relayer**

Responsible for the communication of the Eth Grid-connected Contracts and the MetaPath chain. Synchronization of state and data is achieved by the MetaPath relayer network.

**MetaPath Chain**

The mainnet of MetaPath. Responsible for data updating and smart contract routing.



