Skip to content

Commit

Permalink
Update mep-2542.md
Browse files Browse the repository at this point in the history
  • Loading branch information
sheenhx committed Aug 3, 2023
1 parent 71e788e commit 7a6f1c8
Showing 1 changed file with 14 additions and 12 deletions.
26 changes: 14 additions & 12 deletions proposals/mep-2542.md
@@ -1,40 +1,42 @@

# MEP-2542: Multi-Token Mining for MEP-1004 Radio Miners

## Abstract

This proposal introduces a mechanism for MEP-1004 radio miners to engage in multi-token mining, anchored on the concept of MEP-1002 hexagons. It defines the rules and conditions under which these miners can claim rewards, and the operational parameters which influence the mining capabilities.
This proposal introduces a mechanism for MEP-1004 radio miners to engage in multi-token mining using the structure of MEP-1002 hexagons. It defines the rules, conditions, and operational parameters influencing mining capabilities and reward structures.

## Motivation

Given the limited resource capacity of each MEP-1002 hexagon, there's a need to regulate and allocate mining resources efficiently. This MEP aims to achieve this balance, setting a cycle of 489,600 blocks to minimize resource competition. Further, with the introduction of the Low-Scale-Certification, a new token mining potential of up to 10x has been identified, necessitating the establishment of clear rules.
With the limited capacity of each MEP-1002 hexagon, an efficient regulation and allocation of mining resources is essential. The introduction of $Sensor tokens and changes in fueling mechanisms necessitates the establishment of a revised protocol for mining operations.

## Specification

1. **Hexagon Operational Time**: Each MEP-1004 will have a limited operational time within a MEP-1002 hexagon. Once an interaction via MEP-2542 is initiated using MEP-1004, a count of 489,600 blocks is set. Upon reaching this limit, the MEP-1004 will be removed from the MEP-1002 due to slot limitations.

2. **Reward Claiming**: During the period of 489,600 blocks, radio miner manufacturers must introduce a reward-claiming function. This function will allow MEP-1004 miners to claim MXC tokens from the LPWAN contract treasury.

3. **Token Choice Before Consensus**: Prior to the formation of a miner consensus group in Low-Scale-Certification, MEP-1004 miners can choose up to 2 tokens to mine. Additionally, they have the flexibility to change their token preference every epoch (epoch duration to be defined).
2. **Reward Claiming**: During the period of 489,600 blocks, radio miner manufacturers should implement a reward-claiming function, enabling MEP-1004 miners to claim $Sensor tokens.

4. **MXC Mining Limitation**: MXC is the exclusive token that can be mined for 489,600 blocks due to its limited quantity in the LPWAN treasury. For other tokens, mining can resume if MEP-1004 re-enters a MEP-1002 hexagon for another 489,600-block cycle.
3. **Token Choices**: All MEP-1004 miners can now mine up to 3 tokens, with xMXC serving as the sole fuel tank for their operations. The main mineable token for these miners will be $Sensor.

5. **Token Mining Cap**: Every new token introduced has a daily mining cap of 100,000 tokens. This amount will be distributed amongst the MEP-1004 miners based on their respective fuel tank capacities. Governance decisions hold the authority to adjust this cap as necessary.
4. **Fueling Mechanism**: The $Sensor token acts as an initial fuel tank for new miners. However, for refueling purposes, miners are required to purchase $xMXC. The conversion rate between $Sensor and $xMXC for boosting purposes is set at 1:1. It's noteworthy that while $Sensor is the primary fuel for new miners, any subsequent refueling will mandate the acquisition of $xMXC.

6. **MXC Scarcity Maintenance**: Upon claiming MXC, 3% of the claimed tokens will be burnt to ensure the scarcity of MXC is preserved.
5. **ISO Token Role**: To engage in ISO token mining, an ISO token is essential for boosting the fuel tank. The mechanics and rate of this boost should be further defined based on the dynamics of the ISO token.

## Rationale

- **489,600 Block Cycle**: Starting from a cycle of 489,600 blocks provides a balanced approach to resource competition, ensuring that no miner monopolizes a hexagon, thereby promoting fairness in resource allocation.
- **Multi-Token Mining**: With the capability to mine up to three tokens, miners have increased flexibility in their operations, potentially maximizing their rewards based on prevailing market conditions and token values.

- **Token Mining Cap**: The cap of 100,000 tokens for new introductions takes into account the capabilities introduced by the Low-Scale-Certification design. This design magnifies the mining potential by 10 times. By setting an initial cap, we aim to stimulate miners to expand, validate, and cover more areas, thereby promoting the decentralization and reach of the network.
- **$Sensor Role**: Introducing $Sensor as the primary mineable token and an initial fueling mechanism promotes its adoption and utility. The two-tiered refueling process, involving both $Sensor and $xMXC, balances the token dynamics and ensures sustained mining operations.

- **ISO Token Utility**: The introduction of ISO tokens for boosting the fuel tank when mining this token adds an additional layer of utility and demand for the ISO token.

## Backward Compatibility

This proposal doesn't introduce backward incompatibilities with existing standards. However, manufacturers and miners will need to adjust to the new regulations and integrate the necessary functions to claim rewards.
While the proposal introduces significant changes to the fueling and reward mechanism, it does not inherently disrupt existing standards. Manufacturers and miners, however, must adjust and adhere to the new regulations and integrate the requisite functions for claiming rewards.

## Implementation

Further technical details, including possible code snippets or detailed flow mechanisms, should be added in this section to guide developers and manufacturers.
Further technical details, including potential code snippets or detailed flow mechanisms, should be outlined here to guide developers and manufacturers.


## References

Expand Down

0 comments on commit 7a6f1c8

Please sign in to comment.