keicoin.org use cases docs examples status llms.txt

Examples

One example, running, that exercises every primitive in the SDK. More get written when somebody asks for one, not before.

Status: M1 of eleven. The SDK is real and runs end to end. The chain underneath it is an in-memory mock — there is no public network yet, and nothing anywhere holds value.

What Button demonstrates

PrimitiveWhere it shows up
issueThe game creates its coin on startup
commit / claimBanked presses become one issuer block; your wallet writes the claim
transferYou pay the shopkeeper in coins, signed by you
mintThe shopkeeper delivers the upgrade — only once the chain says the coins landed
itemsEvery upgrade is a supply-N item in your wallet
balanceOfThe screen on the pole, and the price check in the shop
payThe optional exchange desk: Kei in, coins out

The source is the documentation. It is written to be read, and the interesting file is the one holding every line of Kei in the client — about two hundred lines, comments included.

What is not true yet

  • The hosted copy runs against a mock chain that resets. It is a demo, not a service, and nothing in it holds value.
  • It counts its own presses, because in single-player nothing else can see them. That is a real trust hole with a ceiling on it, and it is written down in the source rather than hidden.