Player
Receives rewards and authorizes transactions from a ledger wallet. A gaming identity connects the account to evidence validators can query.
Working protocol / October 2026
KMCoin uses gaming APIs to discover players and verify public account evidence. The network decides which proposed blocks and transactions become part of its shared ledger.
This draft describes the Steam and Xbox API adapters, cross-platform transaction verification and the remaining protocol work. For practical submission steps, use the player transaction guide.
01 / Participants
Receives rewards and authorizes transactions from a ledger wallet. A gaming identity connects the account to evidence validators can query.
Queries a source account, discovers candidates and submits a local block. Its source ID is encoded in the block so validators know which account to check.
Runs the queue and winner rules, independently checks API evidence, and applies accepted results to ledger and player state. A node can also be a producer.
The website is an interface and explorer. Its oracle reports a node’s state; it does not replace validator agreement. Becoming someone’s friend does not itself grant a new validator slot.
02 / Account state
Each record stores a player identity, numeric wallet, balance, accepted transaction counter, first-mined block and public key. Amounts are integer ledger units. The first-mined block also preserves historical identity information, including Minecraft UUID data and linked Steam identities.
To verify a spend, start with the sending wallet number and read its ledger record. A supplied account name, Bio or UUID hint cannot substitute a different identity. Public keys follow KMCoin’s hash-chain authorization rules; public profile evidence supplements those checks.
A new record’s dummy key is not a player-selected spending key. Initial setup and later renewal are distinct. At stored counter 999, then 1999 and so on, the next accepted transaction must prove the old key and install the replacement. The running counter continues. Initial setup and boundary renewal do not debit the marker amount or gas. Setup leaves the counter unchanged; renewal advances it once.
The player data feed exposes public fields for the desktop player and other local tools. It never needs the player’s password or private key.
03 / Acceptance
The producer obtains its friend list, applies the source’s canonical ordering and hashes that list. The local block carries the commitment, a source block number, source account ID and initial player candidate. Transaction candidates travel alongside it.
The sender stamps the outgoing API block. Its embedded timestamp must match the first queue timestamp. The shared majority queue orders candidates and waits for maturity—currently about 149 seconds—before the network winner test.
For a winning Phase I candidate, validators query the source account named in the block. When transactions are present, they first obtain a stable working copy of player-info and check each transaction's current key, counter, type and balance before calling its evidence API. They reproduce the friend-list commitment, apply source-history gates, and check game presence. From the deterministic starting position, selection walks the ordered list and wraps to the first eligible in-game friend.
The verified candidate carries the selected player, accepted transaction candidates and retained Phase I proof. It passes through majority and maturity again. Majority determines the exact included transactions; a validator's missing or different local API receipt does not override that result. Phase II is tied to prior Phase I evidence; a salt or non-dummy proof is not sufficient authorization.
Finalization checks replay identity and transaction authorization against current account state, applies accepted rewards and transactions, and updates ledger and state hashes. The transaction path enforces one transaction per sending wallet per block.
Friend-list changes and unexpected source-height jumps have warmup rules. The defined maximum-to-minimum height wrap is allowed. These checks constrain source changes; they do not make an external API an immutable historical record.
Game presence means the platform reports an eligible game session. It does not prove continuous button presses, a unique human, or a game purchase. Validators may observe different profile versions; only agreeing, eligible results can proceed.
04 / Audit evidence
The current Phase I network winner calculation hashes the concatenated normalized previous network block body and proposed local block body:
auditHash = SHA256(previousBodyNormalized + proposedBodyNormalized)
For Steam and Xbox bodies, normalization removes the timestamp prefix and any ten-digit Phase II salt, while retaining the local block number. The previous ledger ordinal is retained. Separate player/proof tokens and transactions are not included. The consensus hash is not appended to this winner-hash input; it still supplies the separate selection salt.
Winner difficulty adjusts with the configured validator count. The network checks the beginning of the audit hash for a zero; a shorter search window makes a proposal harder to qualify. Every validator applies the same rule to the same inputs. Passing this test allows verification to continue; it does not finalize the block.
| Configured validators | Hash characters checked | Estimated pass rate |
|---|---|---|
| 1 | Winner test bypassed | 100% |
| 2 | First 11 | 50.83% |
| 3 | First 6 | 32.11% |
| 4-5 | First 4 | 22.75% |
| 6 | First 3 | 17.60% |
| 7-10 | First 2 | 12.11% |
| 11-16 | First 1 must be zero | 6.25% |
For a window of w hexadecimal characters, the estimate is 1 - (15/16)^w, assuming evenly distributed hashes. The schedule approximates a lower pass rate as the network grows; it is not exactly 1/N at every size.
At both 15 and 16 validators, a proposal must start with zero: one of sixteen possible hexadecimal characters. With one proposal per validator per minute, the model gives about 0.94 or 1 winning proposal per minute, respectively, before API checks. Actual outcomes can cluster or leave gaps.
Beyond 16 validators, the planned extension follows the same pattern: require a leading zero, then tighten a second zero-check window as participation grows. At 256 validators, two leading zeros give an estimated 1-in-256 pass rate. Further leading zeros can extend the pattern again. This extension would be activated through a coordinated protocol update.
The finalized API block preserves the Phase I audit-hash prefix and appends the network height at which that decision was calculated, keeping the proof field at 64 characters. That anchor is not the later Phase II ledger height. Reconstructing the full decision requires the original Phase I candidate and anchor state, especially when API selection changes the final rewarded player.
The body identifies the source, local sequence, timestamp and committed friend data. The next token identifies the rewarded player. The following token carries audit evidence. Transactions and the trailing ledger hash follow. The explorer labels player proof, ledger suffix hash and observed node consensus separately.
Inspect indexed blocks →05 / Spending
A full transaction identifies the sender wallet, amount, receiver, gas, hash-chain proof and optional fields. Exact bytes, including the final semicolon, matter when committing it through a profile or skin.
wallet*amount_receiver,gas$txHash~metadata%newPublicKey;
For an established key, the transaction proof must solve the current authorization rule. Renewal still requires that old-key proof; transition metadata does not replace it. The new key must be covered by verified evidence. Balances, counters, permitted types and duplicate checks remain ledger decisions.
Native Steam supports abbreviated initial setup and inferred bridges through its short profile field. It cannot carry a complete renewal bundle. The Xbox Bio watcher carries full transactions for Xbox identities and relays them for ledger-linked Steam and Minecraft identities. Steam wallets initialize through native Steam first; subsequent transfers, bridges and renewals can use Xbox.
Only the accepted transaction advances the wallet state. If competing submissions use the same hash-chain step, accepting one invalidates the other against the new counter. A candidate reaching Phase I or Phase II is not a completed spend.
The player transaction guide lists the supported routes, key-renewal rules and claim steps.
Native Steam candidates stay on the Steam path; Xbox Bio submissions stay on the Xbox path, including those spending Steam or Minecraft wallets. Candidates admitted from a losing Phase I block remain pending for a later winner of that source type. A block losing the draw is different from a transaction failing its evidence check.
Publish the Steam commitment or Minecraft skin before its Xbox Bio submission, and retain the evidence through verification. Xbox discovery rotates through up to 20 friends per minute; a 100-friend list takes about 5 minutes to revisit. Failed transaction attempts require an explicit retry: the watcher must observe a changed or cleared Bio and then the restored submission. See the confirmation and retry guide.
06 / External sources
A useful source lets validators locate the producer’s collection, reconstruct its commitment and check the selected player. Friends lists have been the simplest discovery mechanism so far. Transaction transport can be a different platform from the identity authorizing the spend.
| Path | Evidence | Use |
|---|---|---|
| Native Steam | Producer friend list, game presence and abbreviated real-name field | Mining, initial setup and inferred bridges |
| Xbox identity | Source friend list and presence; full Bio transaction from the ledger-linked XUID | Full transaction evidence |
| Steam through Xbox | Full Xbox Bio transaction plus the first 63 hex characters of its SHA-256 in the linked Steam real-name field | Full transaction evidence |
| Minecraft through Xbox | Full Bio transaction plus the exact transaction decoded from the ledger-linked Java UUID’s skin | Full transaction evidence |
Steam-linked wallets initialize through native Steam first. Subsequent full transactions and renewals can use Xbox. Xbox identities support mining, initial setup, transfers, bridges and renewal. For Minecraft, the wallet record supplies the UUID through its first-mined block; decoding must identify one valid UUID before the skin is fetched. Players do not need to supply a UUID. No Xbox-to-Minecraft account lookup is assumed.
Validators use their own API access to read public evidence. The Xbox adapter uses Microsoft sign-in to obtain a token stored locally on the validator. Players never give KMCoin their gaming-account passwords: they publish a valid transaction and the required public proof. The wallet secret used to generate transactions stays on the player's device.
For developersAdding an API to KMCoin →Discovery, canonical data, identity proofs, failure handling and tests.Request budgets and scaleDeveloper notes →Steam batching, rotating Xbox Bio scans, and verification budgets.07 / Agreement and recovery
Deterministic parsing and state updates let nodes compare results from the same agreed inputs. Majority agreement does not establish that every result is correct: validation, membership, replay protection and consistent rules still matter.
Checkpoint rollback is proposed work, not an automatic recovery guarantee. A policy must establish the same checkpoint and restart rules across validators. It may discard later transactions and require players to resubmit; collecting transactions alone cannot guarantee a shared outcome.
KMC on Solana is separate from the KMCoin ledger. Rolling back a bridge burn cannot retrieve an already claimed Solana payout. Recovery must preserve those burns or reconcile them before restored balances can be spent. Contract replay checks alone do not solve that cross-chain accounting problem.
08 / Scope
This release covers Steam and Xbox source adapters, full Bio submissions and public Steam/Java-skin verification. Players still publish evidence manually. The player console resolves identities, generates profile text and prepares Minecraft transaction skins locally. Automatic profile editing and a downloadable wallet application remain future work. Timestamp observations are local diagnostics; they do not enforce a new clock or latency rule.
Timestamp acceptance windows, automatic checkpoint recovery, dynamic validator admission and larger topology remain development work. Timestamp equality is already checked for API queue entries; it is not a complete defense against withheld blocks or clock manipulation.
This is a working specification for review. Protocol changes need matching implementations and test vectors across participating validators before activation. API availability, privacy settings and provider policy remain external dependencies.