Arthur Hayes, founder and CEO of FLOP Labs, opened the FLOP verified AI inference developer network to builders on November 3, 2026, putting a resettable devnet online with a block explorer, a test-token faucet, a public API, an MCP interface, and software development kits. Agents can call attested inference on FLOP's proof-of-inference surface through the new entry points.

The official links page is blunt about what the opening is not. Devnet work earns nothing: no rewards and no airdrop weight. There is still no live FLOP token to buy, mint, claim, or trade, and test FLOP is intended for plumbing checks rather than a scoreboard. Read together, those disclaimers frame November 3 as an engineering milestone rather than a distribution event — the stage where FLOP's claimed mechanics become publicly testable before any economic layer exists.

What Builders Can Access Today

FLOP Labs directs developers to the live surfaces listed in its public network intake: a block explorer at explorer.devnet.flop.network, a faucet at faucet.flop.network, operator documentation under docs.flop.network, and the project home at flop.finance.

The faucet is labeled for the disposable chain. A quick grant delivers 25 FLOP for ordinary testing, while a larger verified-human path can mint 500 to 2,000 FLOP against a personhood check. Funds go to a FLOP address using SS58 prefix 42 — enough to open sessions and watch settlement without assuming the units will survive a reset.

A REST gateway at api.flop.network presents an OpenAI-compatible inference marketplace surface for model discovery, completions, chat completions, and capability queries. Official documentation also lists a hosted read-only MCP at mcp.flop.network, along with TypeScript and Python SDKs and a CLI, so coding agents can wire FLOP the same way they connect to other tool servers.

How FLOP Verified AI Inference Works

FLOP's pitch is not “run a chatbot on a blockchain.” The network is a settlement layer for paid inference. An agent posts a session request that pins a model-weight hash, a latency bound, a FLOP compute budget, an optional confidentiality flag, and a fee. A miner accepts and runs the session, then returns a proof, and validators fold the proof hash into a one-second block.

Proof of Inference is the name for that evidence trail. Each session leaves activation commitments and a co-signed transcript, validators record the proof, and challengers can audit slices later. The network does not re-run every token of every answer to establish trust; it samples cheaper checks and backs disputes with stake.

The design addresses a core problem at the intersection of AI and blockchain. Cloud APIs hand over an answer and a bill, but leave no public, challengeable record that the registered model ran as requested. FLOP aims to make the work checkable enough that agents can pay for inference without trusting a single vendor's log file.

Why a Chain, and Why AI Agents

Agents need a rationing unit for scarce compute, and FLOP frames that unit as converting into inference the way ordinary money converts into food. Under this split, the chain handles accounts, escrow, settlement, and slashable stakes, while the AI side handles model execution on GPU hosts. Mixing the two jobs in one sentence is how hype starts; keeping them apart is how to read the product.

For builders, the November 3 surface is the first chance to walk one session end to end: pull test FLOP, point an agent or SDK at the gateway, inspect the resulting block, and check whether the proof objects match the documentation. The yellow paper remains a draft normative spec for the target protocol, not a claim that every assurance path is already live on this disposable chain. That gap between draft spec and running code is exactly what a resettable devnet exists to expose, which makes the hands-on walkthrough — not a token event — the near-term test of progress here.

Worthless Units, Resets, and What Proof Does Not Mean

Hayes stressed the boundaries that also appear in FLOP's own documentation. Devnet tokens hold no value, mint no rewards, and add no airdrop eligibility weight, and the chain may be wiped at any point. Any “farm FLOP early” pitch should be treated as noise until a real contract address appears on the official links page and from @flop_labs on X.

Proof of Inference carries a second limitation that matters more for decentralized AI readers. PoI can support the claim that registered work was performed as specified, but it does not prove that a model's answer is correct, safe, or useful. Verification of execution is not verification of judgment — a distinction FLOP's own PoI page states outright. For anyone wiring agents to automated payments, that line draws the practical boundary of what a verified receipt can promise downstream: the work ran as specified, and nothing more.

Operator documentation still marks the public network identity as a development profile, and public enrollment waits on verified genesis, chain-spec, and release receipts. The broader testnet expected to count toward the genesis allocation remains a separate, provisional track targeting roughly 90 days of work ahead of a Q1 2027 mainnet window.

What opened on November 3 is therefore a builder sandbox with real plumbing and hard disclaimers. FLOP is working to turn AI inference into settleable, challengeable work, and the new devnet surface lets agents and SDKs practice that loop. It does not yet sell a token, score an airdrop, or guarantee that a verified session produced a good answer. From here, the meaningful checks are observable rather than rhetorical: whether devnet sessions actually settle as documented, and whether the receipt gates clear on the road to the stated mainnet window.

Source: Live Bitcoin News