Where each FLOP network really stands, read from the official docs and dated. Then a hardware check against the strictest published spec, run entirely in your browser.
A public devnet RPC already answers: rpc.devnet.flop.network, chain “FLOP Devnet”, block 2,179,535 on 2026-10-26.
Emission: 96 FLOP per 1 s block. 75% miners, 10% validators, 10% agents and brokers, 5% stakers.
| Field on docs.flop.network | Devnet | Testnet | Mainnet |
|---|
A node can join a network only once these fields are published. Each value reads “Unavailable — no verified public value”, or “None verified” for releases.
Reads CPU, memory, disks, NIC link speed and NVIDIA GPUs. It changes nothing and needs no root.
A miner's sr25519 seed lives on the GPU host and signs chain operations. A validator's account seed also seeds its DA worker. Compromising the host means losing the stake and, for a validator, the seat.
On devnet a miner joins FLOP's private Tailscale network, where FLOP operators can reach every port on the machine. Use a dedicated host with nothing else on it.
One page says an offline miner is never slashed. Another slashes 1–5% of stake for downtime, and a missed calibration job expires after 600 blocks and is slashed. Plan for the strict reading.
FLOP identifies an agent by a did:key, the same key it uses on TechnoCore. Create one in your browser, or in code.
breizhnode.com/flop: generate, sign and publish, the seed stays in your tab.
flop-key: the same in one JavaScript file, with the FLOP devnet address.
TechnoCore DID guide: a throwaway identity from an Ubuntu sandbox.
EasyNode runs 0G alignment nodes as a service: deployment, maintenance and updates.