Skip to main content

IoT LPWAN Protocol

Businesses can establish and manage their own Low Power Wide Area Network (LPWAN) server, which eliminates the need for an administrator for the LPWAN Protocol. This self-operated system requires the locking of six million MXC tokens, which functions similarly to popular blockchain marketplaces like OpenSea or any other protocol.

To ensure seamless functionality, any brand of miner that wishes to participate must run its own customized version of the LPWAN Protocol. In addition, any sensor or Internet of Things (IoT) non-fungible token (NFT) utilizing this system will be required to pay for the services provided by the miners.

By implementing this decentralized network architecture, businesses can have greater control over their LPWAN server while maintaining the necessary security and operational standards. This approach offers a more secure, flexible, and cost-effective solution for businesses looking to streamline their IoT data management processes.

A more detailed illustration is as follows:



MEP stands for MXC Evolution Proposal. Each MEP will be a proposal document providing information to the MXC zkEVM ecosystem and community.

Here is the list of subjects of MEPs:

MEP NumberTitleTypeStatus
MEP-1Purpose and GuidelinesProcessLiving
MEP-20Tokens Standrds on MXC zkEVM ChainStandardsLiving
MEP-721Non-Fungible Token Standard on MXC zkEVM ChainStandardsDraft
MEP-801ISO Application ContractStandardsDraft
MEP-802ISO Provisioning ContractStandardsDraft
MEP-803ISO Sensor Data ContractStandardsDraft
MEP-804ISO Reward Token ContractStandardsDraft
MEP-1002Nestable Non-Fungible Tokens Tied to IoT GeolocationsStandardsLiving
MEP-1004Non-Fungible Tokens Tied to IoT Radio Base Station MinerStandardsLiving
MEP-1759MXC DApp Store Metadata StandardStandardsLiving
MEP-600NFT NFC ContractStandardsDraft
MEP-2542Multi-Token Mining for MEP-1004 Radio MinersStandardsLiving