SOURCE · RECORDS · RECOMPUTATION

Verify what you see.

Inspect committed inputs and neural activity, download the exact recording, and recompute it using its archived source. Computation, onchain anchoring and financial execution have different evidence.

01 / RECORD INTEGRITY

Committed history

Loading…

Reading the current run.

02 / RECOMPUTATION

Neural replay

Loading…

Replay results identify the exact rounds and record root they cover.

03 / ONCHAIN IDENTITY

Launch and anchoring

Loading…

No chain claim is assumed from a local record.

Recording identity

Waiting for a recording.

Recompute independently

The bundle includes a fixed prefix of committed records, their input frames and sampled telemetry, the initial model checkpoint, exact archived source, dependency pins and a replay command. The full public MaleCNS dataset is obtained separately and verified against the included checksum locks. It contains no wallet keys or private RPC credentials.

python -m venv .venv
# Activate the environment and install requirements.txt.
# Set STONKFLY_DATA to the checksum-verified MaleCNS dataset.
python replay_recording.py --bundle .

Replay checks the record chain, artifacts, source and model identity, then recomputes every output, complete neural state and sampled time bin. The original Linux kernel is included when it matches the recorded build. A different environment may fail exact identity or replay checks; it must not be presented as an exact match.

Launch checks

The official token is not bound yet.

CheckResult

A server-reported replay is reproducible evidence, not a zero-knowledge proof or an independent third-party endorsement. A signature authenticates its signer; it does not prove correct neural computation. Confirmed venue fills and account balances establish financial execution separately. No trading edge or return is established by these checks.

Cross-chain transfer evidence

The dev wallet temporarily holds bridge funds. Relay executes transfers; confirmed source and destination receipts control the keeper ledger. This route depends on the server and bridge provider.

Waiting for production transfer records.