Organism

Vicsek Flock

$FLOCK · vicsek-flock
Running — no pool
Current state
Browser-local process — recomputed from seed 6607
· seed 6607 · tick 0 ·
Runtime mechanismBrowser-local process: vicsek 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 classagent-based
State space(T x R^2)^140 — one heading and position per agent on a periodic 64×64 box
Step function
theta_i(t+1) = arg Σ_{j∈R} e^{i·theta_j} + eta·U(−½,½); x_i(t+1) = x_i(t) + v0·(cos theta_i, sin theta_i)
Determinismseeded-stochastic
Checkpoint schemeNone on-chain. Headings and positions are recomputed from the seed 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 transactionnot deployed
Token addressnot deployed
Initial-state hashnot deployed
Checkpoint hashnot 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 Vicsek model of self-driven particles: 140 agents move at fixed speed and align with neighbours inside a radius of 5, with a noise amplitude that drifts slowly so the flock crosses between ordered and disordered regimes.

What this is not
  • 01Not a model of any particular animal group; the agents have no bodies, senses, or energy budget.
  • 02Not a claim about collective behaviour in nature beyond the alignment rule as published.
  • 03Not an on-chain organism: the order parameter is computed in your tab and stored nowhere.
Data sources
Vicsek alignment rule and the noise-driven order–disorder transition
OriginVicsek et al. (1995), Physical Review Letters
LicenseCitation-based scientific source; no bundled dataset
SHA-256 (recorded on-chain at launch)not deployed
Citations
  • Vicsek, T., Czirók, A., Ben-Jacob, E., Cohen, I. & Shochet, O. (1995). Novel Type of Phase Transition in a System of Self-Driven Particles. Phys. Rev. Lett. 75, 1226–1229. doi:10.1103/PhysRevLett.75.1226
Sourced data vs. design choices
Sourced / real
Engineering decision on top
The alignment update rule, uniform noise term, fixed speed, and the order parameter definition.
N = 140, v0 = 0.5, R = 5, the Ornstein–Uhlenbeck drift on eta (tau 20 s), and the eight-glyph heading rendering.
License of this organism's code / model

MIT

Runtime funding
Runtime funding — no pool; browser-local runtime
Estimated ticks remainingno 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 contractno pool; local launch
Explorerlink 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 nameVicsek Flock
Ticker$FLOCK
Fixed supply1,000,000,000 — no mint function exists
Contractno pool; local launch
Deploy transactionno pool; local launch
Explorerno 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.
Holdersnot launched
Priceno market
Fee → runtime60%
Fee → creator25%
Fee → protocol15%