keicoin.org use cases docs examples status llms.txt

What actually works

Published early and updated as it changes, including the parts that say "not yet". A page that only becomes honest at launch was never honest.

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.

Kei is at M1 of eleven. The SDK is real, complete against its specification, and runs end to end. The chain underneath it is an in-memory mock.

State
The SDKComplete and running. Wallet, send, receive, issue, mint, burn, transfer, balanceOf, items, commit and claim all work, with types published.
The chainA mock, in memory. It enforces the real ledger rules — one chain per account, derived asset ids, receivable arrivals, work tiers, the issuance burn, supply caps, transfer policy, and the double-claim index — so the SDK is written against real semantics.
The networkNone. There is no public testnet and no mainnet.
The demoPlayable. Press a button, bank presses, claim them, buy upgrades that live on the chain.
The marketSpecified, not built.
WalletsThe headless summary exists. The in-game panel and the standalone wallet are not built.
The MMO templateNot started.

What this means for you

Do not

  • Put real value anywhere near this. There is no mainnet, and until the validator set is meaningfully distributed there should not be.
  • Ship a production economy on it. Build against it, and expect the chain under the API to change.
  • Assume the market or the wallets exist because the design for them does.

What you can do today is build a complete game economy against the API and have it work, because the mock enforces the real rules rather than pretending. When the node lands, the transport changes and the API does not.

Known and stated plainly