Overview of MEP
MEP is a blockchain system that operates as a cache layer and authentication infrastructure for dApps. Its dApp-facing components are as follows:
• a user-defined interface for developers that lets them describe which types of message they want to transfer. This allows MEP to store only data necessary for message transfer rather than the whole chain.
• a service that dApps can query for information about accounts on multiple chains. For example, a Wallet dApp may want to access all tokens on all chains of a certain user.
• an authentication service that signs a given requested message
• verification services in the form of smart contracts on each underlying blockchain (such as Ethereum), which can verify the authentication issued by MEP
Figure 4 illustrates the steps involved in the delivery of a message through MEP.
Step 1: dApp and MEP contracts are deployed on chains.
Step 2: dApp defines the type of message to transfer to MEP
Step 3: MEP begins to listen and fetch these types of messages on the chains.
Step 4: dApp triggers a transaction on chain A.
Step 5: When dApp wants to transfer this message, it sends a request to MEP. MEP returns the message and authentication.
Step 6: dApp can send the message and authentication anytime before expiry.
Step 7: dApp contract on Chain B verifies the authentication to check if this message is valid. If so, it should proceed with processing the message.