A purchase pays 60% into the animal's vault, 15% to metabolism, 15% to the pool, 10% to the parent's vault. A resale pays 90% to the seller, 5% and 5% to metabolism and pool; the vault travels with the animal.

—

sign in to see the flies you keep

—

The CLI verifier (scripts/verify-epoch.mts) replays the world from a snapshot at native speed in Node and compares the epoch hash with the World account on chain; the operator can post its result to the journal, and that is what the line above reports. The buttons do the same replay here, in a Web Worker: it downloads the graph (~82 MB) and the world's snapshot (~0.7 GB after inflation, streamed straight into the engine's memory), holds about 1 GB at its peak (measured on this build: the worker held 0.68 GB, the 611 MB engine image plus the graph tables it keeps to check the restore; the whole tab, cage and all, reached 1.4 GB), and takes a minute or more. “The next epoch” replays from the latest snapshot to the next boundary and then waits for the world to post it, so the chain is read after the operator has written it, not before; “a posted epoch” uses the snapshot the world kept from just before an epoch it has already posted. A phone cannot do it, so the buttons are only offered on a desktop browser reporting at least 4 GB of memory.

select a fly to watch its neurons

Neurons that fired at the world's last tick, by role group, as a share of the group's neurons (log scale, so one firing among twenty-four shows next to nine hundred among twelve thousand). Groups are the engine's, from Janelia's annotations.

—