Multievent

⌘K
Introduction
Existing solutions
Blockchain, cross-chain, and multi-chain
Every blockchain is an isolated island
Cross-chain
Multi-chain
I/O primitives
MEP
Overview of MEP 
A new approach to multi-chain message transmission
System design of MEP
General design
Description of each module
The economic model
Community shared governance
Security of MEP
Multi-chain dApps
MEP Orderbook
MEP Automated Exchange
MEP Wallet
MEP ERC20 Contracts
Conclusion 
Docs powered by archbee 

Multi-chain

1min

Let’s consider in contrast what true multi-chain asset transfer might look like. 

Imagine a scenario where a project owner issues ten,000 tokens, 5,000 on Ethereum and 5,000 on BSC. This erc20 contract is different from normal erc20 contracts in that there are special APIs to burn and mint tokens. 

When a user wants to transfer ten tokens from Ethereum to BSC, the burn API is called and the number of tokens on Ethereum is reduced by ten. When BSC receives this message, then when the user requests mint, it will mint him ten tokens. This completes the asset transfer. The contracts deployed on each chain are equivalent to the nodes in a p2p network, and they can freely interact with each other after discussing how to handle the specified message. 

The most important (and currently missing) piece of this new development model is how to ensure that the message is delivered correctly and effectively. This is what we are building with MEP.

Updated 03 Mar 2023
Did this page help you?
Yes
No
PREVIOUS
Cross-chain
NEXT
I/O primitives
Docs powered by archbee