SPAWN
Organism

Kuramoto Lattice

$KURA · kuramoto-lattice
Not launched
Illustrative example — not live data
Current state
Simulated preview — organism is not deployed
Illustrative patternticks —
Runtime mechanismFixed-step integration of 512 coupled phase oscillators on a seeded small-world graph.
Tick triggerA runtime worker advances every phase and records the order parameter r.
Ticks recorded— no ticks; not deployed
Meteringc_KURA per 512-oscillator integration step
Specification
Model classcoupled oscillators
State spaceT^512, one phase per oscillator on a fixed Watts–Strogatz graph
Step function
theta_i(t+dt) = theta_i(t) + dt·[omega_i + (K/N)·Σ_j A_ij·sin(theta_j−theta_i)]
Determinismseeded-stochastic
Checkpoint schemeAll 512 phases plus order parameter r every 512 ticks; SHA-256 recorded on-chain
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 512-oscillator Kuramoto system on a Watts–Strogatz small-world graph, with Lorentzian frequencies and coupling near criticality.

What this is not
  • 01Not a neural model.
  • 02Not a power-grid model.
  • 03Not a prediction.
Data sources
Kuramoto phase model and Watts–Strogatz graph construction
OriginPublished mathematical literature
LicenseCitation-based scientific source; no bundled dataset
SHA-256 (recorded on-chain at launch)— not deployed
Citations
  • Kuramoto, Y. (1975). Self-entrainment of a population of coupled non-linear oscillators. Springer LNP 39. doi:10.1007/BFb0013365
  • Strogatz, S.H. (2000). From Kuramoto to Crawford. Physica D. doi:10.1016/S0167-2789(00)00094-4
Sourced data vs. design choices
Sourced / real
Engineering decision on top
Kuramoto coupling law and the published small-world graph construction.
N=512, graph k=6 and beta=0.1, seeded Lorentzian frequency draw, coupling K near criticality, and integration time step.
License of this organism's code / model

MIT

Runtime funding
Runtime funding — no pool; browser-local runtime
Estimated ticks remaining— no escrow yet
Funded by55% of trading fees
ticks_remaining = floor(E / c) c = c_KURA per 512-oscillator integration step 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 contract0x0000000000000000000000000000000000000000
ExplorerView contract
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 nameKuramoto Lattice
Ticker$KURA
Fixed supply1,000,000,000 — no mint function exists
Contract0x0000000000000000000000000000000000000000
Deploy transaction— no pool; local launch
ExplorerView token
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 → runtime55%
Fee → creator30%
Fee → protocol15%