KVM1

The KVM is the end of the question that Kohi asked in 2021. A work is stored on chain as a short program and one seed. Any copy of the machine draws the same picture from them: the contract on Ethereum, the TypeScript machine in a browser, and the WebAssembly build that a token’s metadata hands to a marketplace.

The machine is a stack machine. Its numbers are Fix64 (Q31.32), the same fixed-point math as Kohi, so every copy gets the same answer on every computer. It has two rasterizers: GraphicsV1 for hard edges and AGG for anti-aliased edges.

Artists do not write KVM bytes. They write a sketch in p5c, a dialect of p5.js, and the p5c compiler changes it into KVM instructions.

A big piece can need more gas than one eth_call allows. The step runner and the tile renderer draw it in many small calls that any node will answer, and the result is the same as one big call.

The KVM, plate by plate takes one program apart, from its bytes to the chain, and runs the mainnet contracts in your browser.

2026-07-20 — The KVM1 instruction set is frozen

From this date, opcodes are never redefined, only appended. A change in meaning needs a new container version, so a minted KVM1 program draws the same picture for as long as Ethereum runs.

2026-07-24 — KVMRunner on mainnet