One wallet.
The right proof.

01 / Before sending

Find your existing wallet first.

Look up your SteamID64, Xbox XUID or historical player name in Player Info. Use that exact identity to log in. A gamertag is not an XUID. A new player must receive a network reward before a wallet record exists; this website cannot create one on demand.

For API mining, join a participating producer’s friend list and make the required friends/profile/game information readable to validators. The network selects eligible in-game players. Friendship and playing do not guarantee a reward.

If your wallet still has the placeholder public key, use “Set up key” with a password you can keep safely. Follow the account-specific publishing instructions, then wait for Player Info to show the new key before sending a spend. Keep your password and private key out of every profile, skin and message.

The console displays exact integer ledger units: 100,000,000,000,000 raw units = one block's worth for bridge sizing. Transfers deduct the amount plus gas. Check the receiver wallet carefully; a transfer to an unassigned wallet can burn the coins.

02 / Supported routes

Your wallet identity decides the proof.

Xbox is also a transaction board for existing Steam and Minecraft wallets. It does not move those balances into a different identity. The network starts with the sending wallet’s ledger record to determine which account must prove the transaction.

Minecraft server mining and chat are being retired; existing Java wallets retain the skin route. The operator-supported Rust path remains temporarily available for historical records. A player name without an identifiable Steam account or matching Java UUID does not automatically qualify for an API route.

03 / Steam wallets

A short field, two different uses.

Initial setup and native bridges

For the first key, copy the generated 63-character public-key prefix into your Steam profile’s public real name field. Initial Steam setup is accepted only through Steam.

For a native bridge, choose “Bridge through Steam API” after login and publish the value it generates. The producer infers the largest whole-block bridge your balance supports: minimum 10, maximum 67, with gas 69 raw units and the native path’s one-unit remainder. This route cannot carry a transfer or later key renewal.

Full transactions through Xbox

1. Generate a transfer, full bridge or key renewal in the console.
2. Copy the Steam transaction commitment shown beside it into the linked Steam account’s real name. This is the first 63 lowercase hex characters of SHA-256 of the entire transaction, including the final semicolon.
3. Put the full transaction on its own line in an Xbox Bio observed by a producer. Publish the Steam proof first; leave both in place until confirmation.

Do not copy the first 63 characters of the transaction itself. The console computes the commitment for you. Changing any part of the transaction requires a new commitment.

Native setup leaves one public-key character to be resolved. The first accepted spend can correct that character, whether it is a native Steam bridge or a full transaction through Xbox; you do not need an extra bridge just to initialize it.

04 / Xbox wallets

Publish the complete transaction in your Bio.

1. Generate the transaction for your Xbox wallet in the console.
2. Copy the full line, including its final semicolon, into the Bio on the Xbox account identified by your wallet’s XUID.
3. Keep the Bio readable to validators and visible to a producer’s friend-list watcher. Leave it unchanged until the transaction is confirmed.

Use exactly one transaction on its own line. The whole Bio must fit within 500 characters. There is no DM submission step. The network checks the Bio owner against the wallet, then verifies the key proof, counter, balance and transaction type.

When relaying a Steam or Minecraft wallet, the Xbox account carries the submission, while the ledger-linked Steam profile or Java skin supplies the additional proof. The account names do not have to match.

You do not sign your gaming account into KMCoin or share its password. Publish the transaction and required proof through your normal profile settings. Validators use their own API access to check the public evidence.

05 / Existing Minecraft Java wallets

The skin carries the entire transaction.

The console reads your Java UUID from the wallet's first-mined block. You do not need to enter it or include it in the Bio. Validators resolve the same ledger identity before fetching the skin; an Xbox account claiming another identity cannot replace it.

1. Generate your full transaction.
2. Use the skin tool to encode that exact line into a copy of your 64×64 PNG skin. Upload the result to the Java account whose UUID matches the wallet. Keep the correct slim/classic model.
3. Publish the full transaction on its own line in an Xbox Bio observed by a producer. Keep the skin and Bio in place until ledger confirmation.

wallet*amount_receiver,gas$txHash~metadata%newPublicKey;

Both the skin and Bio contain the same full transaction, including its final semicolon. The skin is processed locally and changes pixels on the right leg. Save your original skin. The website does not upload it or change your gaming profiles.

python -m pip install Pillow
python minecraft_skin_tx.py encode original.png transaction-skin.png
python minecraft_skin_tx.py decode transaction-skin.png

06 / Every 1,000 transactions

Renew the key before the next spend.

At stored counter 999, the next accepted transaction must be a key renewal. It proves the old key, installs the replacement and advances the counter to 1000. Your following spend advances it to 1001. The same boundary repeats at 1999, 2999 and so on.

The console prepares renewal automatically in Transactions when it is due. Keep using the same wallet password. No amount or gas is deducted for initial key setup or renewal; the 1 amount and gas values in these messages are format markers.

Steam wallets must publish a full renewal through Xbox, with its Steam commitment. The short native Steam bridge field cannot renew a key, and bridges stop at the renewal boundary. Xbox and Minecraft wallets use their normal Bio evidence routes. Failed renewals do not advance the counter; correct the evidence and retry.

07 / KMC on Solana

A bridge and its claim are separate steps.

A full bridge burns 10–67 whole KMCoin, in one-KMCoin increments, plus 69 raw units of gas. At the current conversion of 64 KMC per KMCoin, that corresponds to 640–4,288 KMC. These are protocol amounts, not market-value estimates.

After the bridge is accepted, wait for its claim to become available. Open Bridge in the player console, choose the matching bridge, connect your Solana wallet and complete the claim. You need SOL for the Solana transaction fee. Being queued on KMCoin does not mean the payout is ready.

08 / Confirmation and retry

Wait for the ledger, not just a changed profile.

The console refreshes through the player-data feed at its permitted interval, normally one minute for a small network. It shows the snapshot time and pauses preparation if data is stale or unavailable. Check transaction history for the exact accepted transaction, plus the updated balance and counter. Initial key setup changes the key without advancing the counter. API checks and two network phases take time; there is no guaranteed profile-update grace period. Publish supporting proof before the Bio.

If an admitted Phase I block loses the winner test, its transaction candidates remain pending for a later winner. You do not need to change your Bio just because that block lost. An actual failed transaction-evidence check consumes that attempt and requires a manual retry.

To retry, remove or change the submission, leave that change visible until the producer has scanned your account, then restore the corrected submission. Xbox scans 20 friends at a time, so a one-minute change may be missed. Allow a full scan cycle for each change; with 100 friends, that is about 5 minutes, longer if requests fail or the watcher is paused. An unchanged Bio is not repeatedly submitted.

Before retrying, refresh your wallet state and confirm the earlier transaction was not accepted. Generate a fresh transaction if the counter changed. Keep only one pending transaction per wallet.

Player console · Explorer · Working protocol