KMCoin

/trigger goFarm for the potato farm and use your special hoe to break and collect them. They will reappear every minute.

While holding a poisonous potato...

/trigger gethash64 to obtain "hashtrys"

/trigger tryhash to make a block hash attempt

/trigger queue for random hash attempt selection

Before hashing your first block in the server please read below!

https://github.com/tinhatcat/KMC047.git for KMC047.jar download.

The player obtains hash attempts by holding poisonous potatoes (trigger gethash64). Once a hash is attempted (trigger tryhash), the sum of the player's X and Z positions are summed while randomly teleporting in a closed area of bees. (The area is situated so each player position is 0 or -1.) The player can choose either odd or even during the hash attempt. If no selection is made then odd is automatically selected. If the player chooses correctly, then their position is stored a second time while randomly teleporting in a larger area of bees. (This area is situated so the player positions are single digit, positive whole numbers.) These positions are added into four, nine digit numbers (newhash) which are posted on one of five acacia signs on the blockchain. The rest of the signs contain the output from the successful hash attempt, including the player's UUID, the game time, day time, day number, block number, total hash attempts, total hash fails and consecutive hash fails. The datapack saves all Minecraft Block information within the server and players can (trigger lookyes) to visit the in-game blockchain and view their hash and player UUID.

Once a block is found, KMCoin0.4.7 retrieves the Minecraft Block (MCBlock), playername and the "player's block hash" which is calculated as...

player's block hash =  sha256^2002(MCBlock+PrivateKey)

PrivateKey = sha256(sha256(Password)) = sha256^2(Password)

Note: KMCoin Password should be different than Minecraft password and never shared with anyone.

The total process is set to require 30 seconds per attempt, with a 50 percent chance of successfully hashing a block, forever... yielding an average of 1,440 blocks/day. 

The halvings will occur roughly every 4 years or 2,100,000 blocks.

The first KMC block reward is 100,000,000,000,000 KMCoins, which is 2,000,000,000,000 more than bitcoin, making 1 Satoshi equal to 20,000 KMCoins (in terms of units of currency) and omitting decimals completely. All subsequent block rewards also follow the exact same structure as BTC and are as follows...

Reward 1 = 100,000,000,000,000

Reward 2 = 50,000,000,000,000

Reward 3 = 25,000,000,000,000

Reward 4 = 12,500,000,000,000

.

.

.

This gives a total supply of 42 sextillion KMCoins

                         (2,000,000,000,000 more than BTC, just like the block reward)

Transactions are also built into the server. The Java program generates the formatted transaction hash for the player using the Tx Panel. Each transaction hash is calculated as...

                         tx hash = sha256^(2002-tx number)(MCBlock+PrivateKey+batch)

(2002 minus the tx number iterations of the sha256 algorithm of the player's first block mined in the Minecraft server plus their private key and batch number)

Each transaction the player sends retrieves the sha256 solution to the last sent tx hash. All other players read the transaction hash/tx number and compare with the players "PublicKey" listed on the "player_info.log" document found in the "ledger_KMC" folder where all ledger information is stored.

If sha256^(tx Number)(tx hash) equals the players PublicKey, then the txing players tx number is incremented and their transaction is added to "latestTx4.log" found in "Program_Files".

Once a block is found and the player's block hash is received, KMCoin will process 100 transactions per block in order of Gas (1KMC minimum). If there are less than 100 pending transactions on the block, then the transaction will be processed regardless of Gas amount. "latestTx4.log" lists all pending transactions for the next block and can be referenced in the case of high volume.

Once the MCBlock, playername, block hash and all transactions are processed and appended to "ledger_current.log", KMCoin0.4.7 performs 

                         ledger_current_HASH = lcHash = sha256^2("ledger_current.log")

                         player_info_HASH = piHash = sha256^2("player_info.log")

                         ledgerhashes_HASH = lhHash = sha256^2("ledgerhashes.log")

                         consensus_HASH = sha256^2(lhHash+piHash+lcHash)

If "ledger_current.log" is greater than 100 Megabytes, then it is copied to the first empty file located in one of the 100 folders found in "ledger_KMC" and ledger_current_HASH (lcHash) is appended to "ledger_hashes.log". Then, "ledger_current.log" is cleared as it has been stored forever in "ledger_KMC".

Finally, the consensus-HASH is appended to "ledger_current.log".

The ledger is built so that it will rarely exceed 25,600 bytes per a block whilst receiving up to 100 transactions per block (roughly 1/3 BTC average volume).

*See below for a special note regarding transactions

KMCoin0.4.7 is programmed to build the first Terabyte of the ledger, which at max transaction volume for 24 hours a day would take 74 years to fill. So, in theory a player could run the program endlessly without upgrade for a lifetime.

Syncing is as fast as downloading 200Megabytes or less! The consensus hash is calculated only by the ledger hashes, player info page and the current ledger. These files are sourced from trusted players within the server and soon to be updated directories hosted by independent validators.

Players may still mine blocks with KMCoin running, they just won't match the consensus hash until they can download the files.

Once the files are downloaded, simply place them in the "ledger_KMC" folder while in the Minecraft server and click 'Replace All' if prompted. After a block is found you will be synced and able to do transactions. Welcome to TheKittyMine!

Note: The first block mined by the player and their PrivateKey are used for all tx hash and PrivateKey generation. Therefore, you may never change your password after you mine your first block with it. Make the password long and complex, write it down, etc... KMCoin by design allows no one else knowledge of your personal info.

Note: Do not alter the field containing the NewPublicKey when sending 1000th transaction with a valid transition hash.

A player must mine their first block with KMCoin0.4.7 running  to generate their public key for the player_info page. Once this is complete, the player will always be rewarded for their efforts when mining in the server with or without KMCoin running. We have worked hard to develop a user-friendly approach to cryptocurrency.

For more information please email TheKittyMine@proton.me