eip	title	author	discussions-to	status	type	category	created
<to be assigned>	Mineable Token Standard	Jay Logelin, Infernal_toast, Michael Seiler	[email protected], [email protected], [email protected]	Draft	Standards Track	ERC	2018-03-07

ethereum/EIPs#918

Simple Summary

A specification for a standardized Mineable Token that uses a Proof of Work algorithm for distribution.

Abstract

This specification describes a method for initially locking tokens within a token contract and slowly dispensing them with a mint() function which acts like a faucet. This mint() function uses a Proof of Work algorithm in order to minimize gas fees and control the distribution rate. Additionally, standardization of mineable tokens will give rise to standardized CPU and GPU token mining software, token mining pools and other external tools in the token mining ecosystem.

Motivation

Token distribution via the ICO model and it's derivatives is susceptable to illicit behavior by human actors. Furthermore, new token projects are centralized because a single entity must handle and control all of the initial coins and all of the the raised ICO money. By distributing tokens via an 'Initial Mining Offering' (or IMO), the ownership of the token contract no longer belongs with the deployer at all and the deployer is 'just another user.' As a result, investor risk exposure utilizing a mined token distribution model is significantly diminished. This standard is intended to be standalone, allowing maximum interoperability with ERC20, ERC721, and others.

Specification

Interface

The general behavioral specification includes a primary function that defines the token minting operation, an optional merged minting operation for issuing multiple tokens, getters for challenge number, mining difficulty, mining target and current reward, and finally a Mint event, to be emitted upon successful solution validation and token issuance. At a minimum, contracts must adhere to this interface (save the optional merge operation). It is recommended that contracts interface with the more behaviorally defined Abstract Contract described below, in order to leverage a more defined construct, allowing for easier external implementations via overridden phased functions. (see 'Abstract Contract' below)

interface EIP918Interface  {

    function mint(uint256 nonce, bytes32 challenge_digest) public returns (bool success);

    function getChallengeNumber() public constant returns (bytes32);
    
    function getMiningDifficulty() public constant returns (uint);

    function getMiningTarget() public constant returns (uint);

    function getMiningReward() public constant returns (uint);
    
    event Mint(address indexed from, uint reward_amount, uint epochCount, bytes32 newChallengeNumber);
    
    // Optional
    function merge(uint256 nonce, bytes32 challenge_digest, address[] mineTokens) public returns (bool success);

}

Abstract Contract

The Abstract Contract adheres to the EIP918 Interface and extends behavioral definition through the introduction of 4 internal phases of token mining and minting: hash, reward, epoch and adjust difficulty, all called during the mint() operation. This construct provides a balance between being too general for use while providing amply room for multiple mined implementation types.

Fields

challengeNumber

The current challenge number. It is expected tha a new challenge number is generated after a new reward is minted.

bytes32 public challengeNumber;

difficulty

The current mining difficulty which should be adjusted via the _adjustDifficulty minting phase

uint public difficulty;

tokensMinted

Cumulative counter of the total minted tokens, usually modified during the _reward phase

uint public tokensMinted;

Mining Operations

mint

Returns a flag indicating a successful hash digest verification, and reward allocation to msg.sender. In order to prevent MiTM attacks, it is recommended that the digest include a recent ethereum block hash and msg.sender's address. Once verified, the mint function calculates and delivers a mining reward to the sender and performs internal accounting operations on the contract's supply.

The mint operation exists as a public function that invokes 4 separate phases, represented as internal functions _hash, _reward, _newEpoch, and _adjustDifficulty. In order to create the most flexible implementation while adhering to a necessary contract protocol, it is recommended that token implementors override the internal methods, allowing the base contract to handle their execution via mint.

This externally facing function is called by miners to validate challenge digests, calculate reward, populate statistics, mutate epoch variables and adjust the solution difficulty as required. Once complete, a Mint event is emitted before returning a boolean success flag.

// cumulative counter of the total minted tokens
uint public tokensMinted;
    
// track read only minting statistics
struct Statistics {
    address lastRewardTo;
    uint lastRewardAmount;
    uint lastRewardEthBlockNumber;
    uint lastRewardTimestamp;
}

Statistics public statistics;

function mint(uint256 nonce, bytes32 challenge_digest) public returns (bool success) {
    // perform the hash function validation
    _hash(nonce, challenge_digest);
    
    // calculate the current reward
    uint rewardAmount = _reward();
    
    // increment the minted tokens amount
    tokensMinted += rewardAmount;
    
    uint epochCount = _newEpoch(nonce);
    
    _adjustDifficulty();
    
     //populate read only diagnostics data
    statistics = Statistics(msg.sender, rewardAmount, block.number, now);
 
   
    // send Mint event indicating a successful implementation
    Mint(msg.sender, rewardAmount, epochCount, challengeNumber);
    
    return true;
}

Mint Event

Upon successful verification and reward the mint method dispatches a Mint Event indicating the reward address, the reward amount, the epoch count and newest challenge number.

event Mint(address indexed from, uint reward_amount, uint epochCount, bytes32 newChallengeNumber);

merge

Optional

Operationally similar to mint, except the merge function offers a list of token target addresses intended to be used to merge multiple token rewards.

function merge(uint256 nonce, bytes32 challenge_digest, address[] mineTokens) public returns (bool success);

_hash

Internal interface function _hash, meant to be overridden in implementation to define hashing algorithm and validation. Returns the validated digest

function _hash(uint256 nonce, bytes32 challenge_digest) internal returns (bytes32 digest);

_reward

Internal interface function _reward, meant to be overridden in implementation to calculate and allocate the reward amount. The reward amount must be returned by this method.

function _reward() internal returns (uint);

_newEpoch

Internal interface function _newEpoch, meant to be overridden in implementation to define a cutpoint for mutating mining variables in preparation for the next phase of mine.

function _newEpoch(uint256 nonce) internal returns (uint);

_adjustDifficulty

Internal interface function _adjustDifficulty, meant to be overridden in implementation to adjust the difficulty (via field difficulty) of the mining as required

function _adjustDifficulty() internal returns (uint);

getChallengeNumber

Recent ethereum block hash, used to prevent pre-mining future blocks.

function getChallengeNumber() public constant returns (bytes32) 

getMiningDifficulty

The number of digits that the digest of the PoW solution requires which typically auto adjusts during reward generation.Return the current reward amount. Depending on the algorithm, typically rewards are divided every reward era as tokens are mined to provide scarcity.

function getMiningDifficulty() public constant returns (uint)

getMiningReward

Return the current reward amount. Depending on the algorithm, typically rewards are divided every reward era as tokens are mined to provide scarcity.

function getMiningReward() public constant returns (uint)

Example mining function

A general mining function written in python for finding a valid nonce for mined token 0xbitcoin, is as follows:

def mine(challenge, public_address, difficulty):
  while True:
    nonce = generate_random_number()
    hash1 = int(sha3.keccak_256(challenge+public_address+nonce).hexdigest(), 16)
    if hash1 < difficulty:
      return nonce, hash1

Once the nonce and hash1 are found, these are used to call the mint() function of the smart contract to receive a reward of tokens.

Rationale

A keccak256 algoritm does not have to be used, but it is recommended since it is a cost effective one-way algorithm to perform in the EVM and simple to perform in solidity. The nonce is the solution that miners try to find and so it is part of the hashing algorithm. A challengeNumber is also part of the hash so that future blocks cannot be mined since it acts like a random piece of data that is not revealed until a mining round starts. The msg.sender address is part of the hash so that a nonce solution is valid only for a particular Ethereum account and so the solution is not susceptible to man-in-the-middle attacks. This also allows pools to operate without being easily cheated by the miners since pools can force miners to mine using the pool's address in the hash algo.

The economics of transferring electricity and hardware into mined token assets offers a flourishing community of decentralized miners the option to be involved in the Ethereum token economy directly. By voting with hashpower, an economically pegged asset to real-world resources, miners are incentivized to participate in early token trade to revamp initial costs, providing a bootstrapped stimulus mechanism between miners and early investors.

One community concern for mined tokens has been around energy use without a function for securing a network. Although token mining does not secure a network, it serves the function of securing a community from corruption as it offers an alternative to centralized ICOs. Furthermore, an initial mining offering may last as little as a week, a day, or an hour at which point all of the tokens would have been minted.

Backwards Compatibility

Backwards incompatibilities are not introduced.

Test Cases

(Test cases for an implementation are mandatory for EIPs that are affecting consensus changes. Other EIPs can choose to include links to test cases if applicable.)

Implementation

Simple Example:

https://github.com/0xbitcoin/EIP918-Mineable-Token/blob/master/contracts/SimpleERC918.sol

Complex Examples:

https://github.com/0xbitcoin/EIP918-Mineable-Token/blob/master/contracts/0xdogeExample.sol https://github.com/0xbitcoin/EIP918-Mineable-Token/blob/master/contracts/0xdogeExample2.sol https://github.com/0xbitcoin/EIP918-Mineable-Token/blob/master/contracts/0xBitcoinBase.sol

0xBitcoin Token Contract: https://etherscan.io/address/0xb6ed7644c69416d67b522e20bc294a9a9b405b31

MVI OpenCL Token Miner https://github.com/mining-visualizer/MVis-tokenminer/releases

PoWAdv Token Contract: https://etherscan.io/address/0x1a136ae98b49b92841562b6574d1f3f5b0044e4c

Copyright

Copyright and related rights waived via CC0.