The rules, in full.

A vault is a seed and a rule. The seed is a string — usually a Solana address, but any text works. The rule is the Hénon map, x' = 1 − a·x² + y and y' = b·x, with a, b and the starting point derived from the seed by a fixed hash.

Everything a vault contains follows from those two things. There is no artwork file, no metadata record, no server-side generator, and no row in a database that says what you own. Given the seed, the contents are recomputable by anyone, forever, with or without this site.

ATTRACTOR — the orbit never repeats and never escapes. It traces a strange attractor with a measurable fractal dimension, typically between 1.1 and 1.3.

CYCLE — the orbit falls onto a small finite set of points and repeats them forever. Run it for a billion steps and it visits the same handful of places. The reading shows how many.

VOID — the orbit runs to infinity. There is no figure, no dimension, nothing to draw. About one address in five lands here, and its page says so plainly rather than substituting a decoration.

A vault holds between 6 and 10 states, fixed by the seed. State 0 uses the vault's own a and b; each later state walks a small committed distance away from them. The walk is derived from the seed too, so state 4 was already determined before anyone looked.

A vault cannot gain states later. If it holds 7, it held 7 the day the address was created and will hold 7 after this project is forgotten.

Box-counting. The orbit's bounding box is divided into a grid at five resolutions — 16, 32, 64, 128 and 256 — and the number of occupied cells is counted at each. Plot log(cells) against log(resolution) and the slope is the dimension.

A line gives about 1. A filled area gives about 2. The classic Hénon attractor is known to sit near 1.26, and feeding a = 1.4, b = 0.3 into this engine returns 1.266. That agreement is the reason to believe the number on your vault page.

Rarity here is a count of what real addresses actually got. The station walks mainnet blocks, takes the account keys it finds, and runs each through the engine. The tally lives on the census.

No percentage is quoted anywhere until 500 addresses have been read, and the sample size is printed next to every figure. Percentages count appearances in blocks, not unique wallets — an active address can be counted more than once, and saying so is part of the number.

HENON does not mint anything. There is no token contract behind a vault, no marketplace, no treasury wallet, and no purchase of any kind. Nothing here can be bought, and nothing you do on this site changes what a vault contains.

HENON never asks for a signature. Connecting a wallet reads your public key so you do not have to paste it; pasting it does exactly the same thing. No transaction is ever constructed.

HENON stores no artwork. Every image you see was drawn by your own browser in the moment you looked at it.

Two things, and they are worth naming rather than burying.

The census. You can verify any single reading yourself, but you cannot watch us walk the blocks. If the counts were fabricated you would have no way to tell from the outside. This is why the sample size appears beside every percentage and why the gate exists at all.

That the two engines agree. The browser copy and the server copy are separate files and could drift. Verify exists to catch exactly that: it runs the published test vectors through the copy on your machine and compares every field.