flop-lab
← All tools

Devnet workbench / Conformance harness

Claims meet
observations.

Inspect repeatable protocol checks. Trace a result to its source. Copy the command and test it yourself.

Runner guide ↗
Network labelFLOP Devnet
Genesis hashUnavailable
Spec versionUnavailable
Reported spend0 FLOP

Hosted health and indexer do not expose a verifiable genesis hash or runtime spec version. Network identity remains incomplete. Read from mcp.flop.network and api.flop.network.

01 / Claim catalogue

Every result has a reason.

A pass checks the named predicate. An unavailable check establishes nothing. Select a claim to compare its evidence.

64 of 64 claims

Showing 12 of 64

02 / The recorded run

From request to evidence.

Reading progress follows this section. The bars below show recorded request durations.

  1. Started100 request ceiling
  2. Observation59 recorded requestsResponses retain their source and timestamp.
  3. ConfirmationFailures re-run oncemcp-agent-pack-manifest: 2 attempts
  4. Finished52,007 ms elapsed
First request → last requestRelative duration / peak 8,579 ms

03 / Reproduce it

Bring your own observation.

From a checkout with Node 22 and pnpm installed. These commands read public devnet surfaces.

git clone https://github.com/zkasuran/flop-lab.git
cd flop-lab && pnpm install --frozen-lockfile
pnpm --filter @flop-lab/harness start run --class read-only --max-requests 100 --max-flop 0

The CLI writes JSON and Markdown. The page reads the committed package recording. To refresh it, run pnpm --filter @flop-lab/harness record and review the recorded files before committing.

What this does not verify

No consensus finality, miner inference or cryptographic proof is established here. Missing genesis and runtime identifiers are left unavailable. Spend scenarios need prerequisites and are not executed by this page.

Separate public API reads are not an atomic snapshot. The devnet can reset. Schema agreement is not proof of service correctness. See the runner limits.