MEP ERC20 Contracts

in section 2 2, we introduced the example of a project owner who wants his token supported on multiple chains – for instance, ethereum and bsc the project owner would be able to deploy on each chain a mep erc20 contract, which is a standard erc20 contract with two additional functions for adding and deleting assets – burn and mint function burn(address account, uint256 tochainid, uint256 amount) function mint (address account, uint256 amount, uint256 fromchainid, uint256 nonce, bytes memory signature) when a user wants to transfer some mep erc20 token from chain a to chain b • the user calls the burn function on chain a • mep monitors and reaches consensus on the event • the user requests authentication for the event from mep • the user takes this authentication and the relevant information to call the mint function of the token contract on chain b to claim the token • during the mint process mep will internally call the signature verification function to verify the validity of the signature • this model offers asset transfer natively and does not require the provision of a resource pool using this model, other resources can be directly transferred among chains