Steam Rewards

Proof of Game for Steam players

KMCoin can reward Steam players without requiring them to join a KMCoin network server. A Steam source account publishes deterministic blocks from its friend list, and validators verify the selected player before the block enters the network.

Player Flow

Add the Steam source account

Players join the Steam reward pool by friending the KMCoin Steam source account (KittyMineCoin - SteamID:76561198779127606). If the player exposes their current game activity, their SteamID64 can be selected for rewards while they are playing any Steam game.

Identity

SteamID64 is the player name

Steam rewards use the player's 17 digit SteamID64 instead of a legacy server player name. This gives Steam players a stable identity that cannot be changed inside a game server, reduces duplicate-name spam, and lets validators connect rewards to a public account that Steam can independently report.

Phase I

Friend-list commitment

A Steam source block commits to the source account, the ordered friend-list hash, and an initial deterministic candidate. Validators rebuild the friend-list hash from Steam's API before accepting the block; if the list was changed after seeing network data, the hash no longer matches and the block fails instead of becoming a crafted winner.

Phase II

Verified winner

Before winner selection, validators detect a Phase I Steam block, salt it with the most recent network consensus, and use the salted candidate in the normal KMCoin winner calculation. If it wins, validators verify the friend list and active Steam game through Steam's API, then send the verified Phase II block back through the normal queue for presence verification.

Verification

What validators check

  • The friend-list hash can be independently recomputed.
  • The source Steam account is included in the block.
  • The final winner is derived from deterministic public data.
  • The winner must return an active Steam game ID before Phase II is accepted.
Limits

What Steam must expose

  • Steam must expose the player's current game activity through its API.
  • Private game details or hidden presence can prevent reward verification.
  • Steam profile metadata can help future transaction checks, but game presence still depends on Steam's game ID field.
Network Role

Steam blocks still settle through KMCoin

Steam verification does not replace KMCoin consensus. Verified Steam blocks re-enter the same network queue used by server blocks, then settle by majority across validators. This keeps Steam rewards compatible with the existing blockchain flow.

Next Layer

Steam is the first verification layer

Steam gives KMCoin a massive first identity network: Steamworks lists more than 132 million monthly active Steam users. The same verification model can expand beyond Steam wherever player identity or activity can be independently checked, including Minecraft, Activision, Blizzard, Xbox, PlayStation, and other public gaming identity systems.

This approach removes blind trust from server blocks by moving KMCoin toward independently verifiable game data. Validators can check game activity, block source, and transaction identity before accepting claims into the network. If validators can independently confirm the player, source, and activity, KMCoin can use it.

Final Layer

Deterministic game verification

Instead of relying on hosted servers as trusted block producers, KMCoin can move toward auditable game API block generation. Validators can independently check whether the player, source, timestamp, and activity match the expected public data. If the data does not match exactly, the block fails.

This is KMCoin's proof-of-game model: not proof-of-work, but deterministic verification that game activity happened as expected.