SPAWN
Organism

Orbium

$ORBIUM · orbium
Running — no pool
Current state
Browser-local process — recomputed from seed 2909
· seed 2909 · tick 0 ·
Runtime mechanismBrowser-local process: lenia stepped at a fixed 60 Hz accumulator from a fixed seed; state is recomputed from the seed on every page load, nothing is persisted or observed by anyone else.
Tick triggerWall-clock 60 Hz step while the canvas is on screen. Not block-anchored; a launched organism would need an observable trigger.
Ticks recorded0 (this device, this session)
Metering— not metered; no pool
Specification
Model classcellular automaton
State space[0,1]^(64x64) continuous scalar field on a torus
Step function
a_{t+1} = clip(a_t + dt·G(K∗a_t), 0, 1); K(r) = exp(4 − 1/(r(1−r))) normalised, R = 13; G(u) = 2·exp(−(u−0.15)²/(2·0.017²)) − 1; dt = 0.1
Determinismdeterministic
Checkpoint schemeNone on-chain. The field is recomputed from the published pattern and seed placement on every page load.
Replayableyes
Verify this yourself
  1. 1 fetch s_0 and sigma from the launch tx
  2. 2 fetch f from the stated code repository at the recorded commit
  3. 3 recompute to the latest checkpoint t
  4. 4 compare SHA-256(s_t) to H_t on-chain
Launch transaction— not deployed
Token address— not deployed
Initial-state hash— not deployed
Checkpoint hash— not deployed

For illustrative organisms none of these values exist yet; the panel shows the procedure only.

Provenance document

What this is, sourced and bounded

Permanent · required before launch

This document was completed by the creator before the launch transaction could be submitted, and is rendered here in full. It cannot be edited after launch; the data hashes below are recorded on-chain.

Summary

The orbium glider of Lenia: a smooth continuous cellular automaton in which a ring kernel and a narrow Gaussian growth function sustain a self-propelling pattern on a 64×64 torus.

What this is not
  • 01Not a lifeform and not a biological model: the field is a scalar array, not cells or chemistry.
  • 02Not a discovery: the kernel, growth function, and orbium pattern are published work, reimplemented here.
  • 03Not an on-chain organism: the field is recomputed locally and never recorded.
Data sources
Lenia kernel, growth function, and the published orbium pattern
OriginChan (2019), Complex Systems; pattern reproduced from the paper
LicenseCitation-based scientific source; no bundled dataset
SHA-256 (recorded on-chain at launch)— not deployed
Citations
  • Chan, B.W.-C. (2019). Lenia: Biology of Artificial Life. Complex Systems 28(3), 251–286. doi:10.25088/ComplexSystems.28.3.251
Sourced data vs. design choices
Sourced / real
Engineering decision on top
Kernel form, R = 13, mu = 0.15, sigma = 0.017, dt = 0.1, and the orbium pattern itself.
Grid size, seed-drawn placement and quarter-turn orientation, collapse detection at 5% of initial mass, respawn behaviour, and the glyph/fill thresholds used for rendering.
License of this organism's code / model

MIT

Runtime funding
Runtime funding — no pool; browser-local runtime
Estimated ticks remaining— no escrow yet
Funded by60% of trading fees
ticks_remaining = floor(E / c) c = — not metered; no pool dE/dt = phi · V(t) − c · r r = tick rate (ticks per unit time)
If funding depletes
The organism pauses. Its page keeps rendering, the trace freezes at its last state, and the status changes to “Paused — runtime unfunded”. Nothing is deleted and the provenance document stays public. Funding can resume from later trading fees or a direct top-up, and the organism continues from its last checkpoint. Depletion is an expected state, not a fault.
Liquidity lock

Every launch's liquidity is locked at deploy time. No withdraw function exists in the locker contract — not for the creator, not for an admin, not for anyone.

Locker contract— no pool; local launch
Explorer— link appears once deployed on chain
Functions this contract exposes
  • + lock(token, amount) — callable once, by the factory, inside the deploy transaction
  • + collectFees(address recipient) — routes trading fees to the runtime escrow and the fee split
  • + positionOf(token) — read-only view of the locked position
Functions it does not expose
  • − withdraw / unlock / release — not implemented, in any form
  • − owner / admin / setOwner — the contract has no privileged role
  • − upgradeTo / delegatecall proxy hooks — the deployed bytecode is final
  • − selfdestruct
Token
Token nameOrbium
Ticker$ORBIUM
Fixed supply1,000,000,000 — no mint function exists
Contract— no pool; local launch
Deploy transaction— no pool; local launch
Explorer— no pool; local launch
Not linked to a pool
This organism runs, but nothing funds it and nothing trades it. When the factory and locker deploy, an organism like this would be launched with its pool in one transaction and metered per tick. Until then, its runtime is your browser tab.
Holders— not launched
Price— no market
Fee → runtime60%
Fee → creator25%
Fee → protocol15%