SPAWN
Organism

Tripod Walker

$TRIPOD · tripod-walker
Running — no pool
Current state
Browser-local process — recomputed from seed 4471
· seed 4471 · tick 0 ·
Runtime mechanismBrowser-local process: fly 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 spaceR^6 leg phases, body pose (x, y, heading), and a discrete behavioural state
Step function
theta_leg(t+dt) = theta_leg(t) + 2*pi*f*dt (mod 1); stance legs constrain body velocity; heading integrates turn rate
Determinismseeded-stochastic
Checkpoint schemeNone on-chain. The full state is 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 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

A six-legged walker using alternating tripod coordination: legs L1/R2/L3 swing together against R1/L2/R3, with stride frequency and turn statistics following reported adult Drosophila walking behaviour.

What this is not
  • 01Not a fly, and not a biomechanical model: there are no joint torques, masses, or ground reaction forces.
  • 02Not a claim about neural control of gait; leg phases are prescribed, not generated by a circuit.
  • 03Not an on-chain organism: no pool funds this run and no contract observes it.
Data sources
Reported adult Drosophila stride frequency, duty factor, and turning statistics
OriginPublished figures in the cited papers; no dataset file is bundled
LicenseCitation-based scientific source; no bundled dataset
SHA-256 (recorded on-chain at launch)— not deployed
Citations
  • Wosnitza, A. et al. (2013). Inter-leg coordination in the control of walking speed in Drosophila. J. Exp. Biol. 216, 480–491. doi:10.1242/jeb.078139
  • DeAngelis, B.D., Zavatone-Veth, J.A. & Clark, D.A. (2019). The manifold structure of limb coordination in walking Drosophila. eLife 8:e46409. doi:10.7554/eLife.46409
Sourced data vs. design choices
Sourced / real
Engineering decision on top
Alternating tripod phase relationships, stride frequency range, and duty factor.
Body geometry, leg reach, the behavioural state machine (walk / turn / groom / stop), wall avoidance, and glyph 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 nameTripod Walker
Ticker$TRIPOD
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%