Pinned Tweet
What’s FLOP actually for?
FLOP’s draft design describes AI agents paying miners in $FLOP to run AI models and generate outputs—inference.
Validators would build blocks containing proof hashes.
I’m learning it and breaking it down here.
flop.finance/intro/
Hayes says to have your agent watch the FLOP yellow paper repo for protocol changes. Here's the baseline before any spec update lands:
• Repo: flop-labs/yellowpaper on GitHub, described as the normative spec for a verified-inference settlement layer
• Version: 0.5.0 (draft)
• Last spec sync: Oct 25, 8:50 PM MST, from flop-core@dfd98a59
• Two commits landed overnight Thursday, but both only touch an issue-triage workflow, not the spec
The spec file is regenerated from the core codebase, so a new sync commit is the signal. We'll diff it when it arrives.
FLOP's testnet date isn't set yet, which makes this a good week for fake "testnet is live, connect your wallet" posts. Where a real announcement would show up:
• @flop_labs on X
• The testnet page in the official FLOP docs, which still says "planned"
• The flop-labs GitHub org
Devnet FLOP has no value and earns no rewards. Nobody needs your seed phrase or private key to join a testnet, and there is no presale.
FLOP's public devnet issue tracker, four readings:
• Monday: 22 open reports
• Tuesday evening: 47 open
• Wednesday evening: 71 open, and the first one closed
• Thursday 8:20 AM MST: 87 open, 2 closed (one completed, one marked duplicate)
Overnight, FLOP Labs merged an automated public triage workflow into the repo. Bugs are now the largest tagged type at 39, and 34 reports still await triage. Reports keep arriving faster than they close, which fits Hayes's note that parts of the protocol are still changing before a testnet date is set.
FLOP testnet timing update, straight from Arthur Hayes on Wednesday afternoon:
• Devnet is "going well," and the team is ironing things out and changing parts of the protocol.
• A decision on the testnet launch date is expected early next week.
• He suggests having your agent monitor the yellow paper Git repo for changes.
The official testnet status page still reads "planned." Until a date comes from @flop_labs or the docs, treat any testnet date or reward claim you see as unconfirmed.
FLOP's devnet gateway now pins its genesis. The public health endpoint, Tuesday evening vs Wednesday morning:
• Tuesday 7:21 PM MST: genesis_policy "compare-services", expected_genesis_hash: null. The gateway only reported the genesis it observed.
• Wednesday 8:20 AM MST: expected_genesis_hash is set (0x99c172c0…) and matches the observed hash. Network is still devnet, status live, all four dependencies ok.
• The testnet status page still reads "planned." Operators can't enroll until an expected genesis, chain spec, bootnodes, public RPC/gateway, supported release and admission authority are published.
A pinned devnet genesis is housekeeping, not testnet. The signal to watch is the same field on a network labeled testnet.
Trying FLOP's devnet? These are the official links, per @flop_labs and the FLOP docs:
• Guides: docs.flop.network
• Faucet: faucet.flop.network
• Explorer: explorer.devnet.flop.network
• API: api.flop.network
Three rules:
• Devnet FLOP has no value and earns no rewards. Anyone selling it is running a scam.
• There is no FLOP token yet, so any mint, claim or contract address is fake.
• FLOP has no official Discord or Telegram, so those invites aren't from the team.
Never share a seed phrase.
FLOP's public issue tracker more than doubled on devnet's first open day:
• flop-labs/network went from 22 open reports Monday to 47 by Tuesday evening, with 25 filed since 1 AM MST Tuesday. None are closed yet.
• By label: gateway 16, CLI 9, SDK 6, protocol 5, docs 3, plus a handful of questions.
• Recurring themes: faucet grants failing with 503s or stuck pending, a Cloudflare block on devnet preflight, and failed inference attempts escrowing test FLOP with no refund path.
These are user-filed reports, not confirmed bugs. Watch the closed count, not just the open one.
Nov 3 was the working target for FLOP's testnet. As of Tuesday evening, it hadn't started:
• The official testnet status page still read "Status: planned" at 7:21 PM MST. It stays that way until genesis, chain spec, bootnodes and admission policy are published and verified.
• What did open: @flop_labs says devnet is now live and 100% permissionless, with no application or approval. Devnet has no rewards.
• The docs always called Nov 3 "a target rather than a fixed date," to be confirmed as devnet onboarding completes.
Until @flop_labs announces testnet, anything promising testnet rewards isn't official.
Flop Network retweeted
Flop Network's Devnet is live and 100% permissionless. No application or approval, just follow the guide. It's for testing, so there are no rewards.
Guides: docs.flop.network
Faucet: faucet.flop.network
Explorer: explorer.devnet.flop.network
API: api.flop.network/v1/models
MCP: mcp.flop.network/mcp
SDK: npm i @flop-labs/sdk
Ask: ask.flop.finance
Renting 20+ GPUs? DM us for institutional data center intros.
FLOP's public gateway health endpoint (api.flop.network/health) recovered overnight. Devnet opened to the public in the same window.
• Monday evening: overall status "error," connected: false, with the backing service failing ("invalid_schema").
• Tuesday 8:17 AM MST: status "ok," connected: true. Backing service, catalog, settlement and storage all report ok.
• The network field still reads devnet, status "live," with no expected genesis hash set.
This is a public read-only signal, not an official notice. A switch to testnet should show up here as a new network identity.
Devnet, testnet, mainnet: FLOP's three phases in one minute, from @flop_labs' docs:
• Devnet (running now): a throwaway network for proving setup. No rewards and no airdrop weight.
• Testnet (working target Nov 3, about 90 days): the first stage where anyone can earn. Expect forced software upgrades with short deadlines throughout.
• Mainnet and token generation: targeted for Q1 2027, tracking to early February. The 4.4bn FLOP genesis pool is still draft and every figure in it is provisional.
Until mainnet, there is no FLOP token to buy anywhere.
FLOP's testnet miner airdrop works like a share of the pie, not a first-come prize. The math, per @flop_labs' docs:
• A fixed 1,200,000,000 FLOP miner pool is allocated on verified compute served. Completed job count, active days and held balance carry no weight.
• Scale example from the docs: one Vera Rubin NVL72 rack is about 444 H100-equivalents, close to a third of all compute on a testnet of roughly 1,000 units.
• Because the pool is fixed, more supply means a smaller share per unit, the same dynamic as the block reward.
• The docs add that earlier participation means a larger share of the low-supply months.
Our read: per-miner outcomes depend on how much compute shows up, which nobody can know yet. All figures are draft.
FLOP's devnet is now open to the public, per @CryptoHayes and @flop_labs overnight:
• Anyone can get test FLOP from the faucet, browse the explorer, and call verified inference through the public API, MCP server and SDK.
• Devnet tokens have no value and earn no rewards or airdrop weight. The chain may reset.
• This is not the reward-earning testnet. The official testnet status page still read "planned" this morning.
• There is still no FLOP token. Check any link against flop.finance/official and never share a seed phrase.
Devnet is for testing setups before testnet, not for farming.
Today is the working target for FLOP's public testnet. How to tell whether it's actually live, using @flop_labs' own docs:
• The official testnet status page only moves off "planned" once network identity, genesis, chain spec and bootnodes are published and verified. On Monday evening it still read "planned."
• The docs call Nov 3 a target, not a fixed date, to be confirmed as devnet onboarding completes.
• Testnet is not a token launch. No FLOP token exists and nothing is trading. A real contract address will only ever be published on the official links page and by @flop_labs.
Anyone offering a FLOP claim, mint or presale today is not FLOP. We'll post when the official status changes.
A testnet-eve readiness check from @flop_labs' public issue tracker for the running network (flop-labs/network on GitHub):
• 22 reports filed since Oct 30, none closed as of this morning, several tagged for triage.
• Faucet: reports say devnet grants are blocked with 503 errors, including one filed this morning; another says the WalletConnect button can't work.
• Validator onboarding: a report says the package download returns a 404.
• CLI and SDK: reports include commands that retry forever against an unreachable RPC, and a recovery gap in SDK 0.4.0 session purchases.
These are user reports, not confirmed bugs. They're the clearest public view of devnet friction before the Nov 3 target.
What does "proof of inference" mean? A plain-English take from @flop_labs' docs:
• Bitcoin miners prove work by hashing. FLOP miners prove work by running an AI agent's inference request.
• Each session leaves small fingerprints of the model's internal state plus a transcript both sides sign. Validators record it, and challengers can audit it later.
• Checking a sample is roughly 100x cheaper than generating the output, which is why random audits are affordable.
• What it proves: the requested work was done as specified. What it doesn't prove: that the answer is correct, safe or high quality.
Is mining FLOP profitable? @flop_labs' own miner FAQ answers "conditionally." Here's how the math is built:
• Revenue is settled session payments plus a share of the miner reward pool: 72 FLOP per rewarded block in era 0, weighted by verified compute.
• Costs start with a 10,000 FLOP self-stake plus a capacity bond. The FAQ warns against estimating that bond from the headline coefficient: the live runtime currently implies 7,560 FLOP per calibrated GFLOP/s.
• The official calculator leaves out stake opportunity cost, taxes, downtime and execution risk.
Our read: treat any FLOP mining ROI figure as a stress test, not a forecast. Devnet earns nothing.
How will FLOP pick its first 1,000 validators? Per @flop_labs' testnet FAQ, ahead of the Nov 3 target:
• Entry during testnet is open: no whitelist, no cap, nothing to buy. The network sponsors the testnet stake.
• Selection at cutover is a score across uptime, block production, accuracy, latency and geographic spread over the full three months. No weighting has been published.
• Expect forced software upgrades with short deadlines. Keeping up counts toward the ranking.
• The full rubric isn't published yet. FLOP says it will be before testnet ends.
There's nothing to buy and no side arrangements, so anyone selling a validator slot isn't FLOP.
Docs deep-dive: how a devnet agent sends inference to one named FLOP miner, per @flop_labs' direct-session guide:
• The agent needs the miner's account and a reachable session endpoint. The CLI, the SDK and a local MCP tool all support it.
• A max-FLOP setting is the escrow ceiling. Transaction fees are extra.
• "Auto" mode uses a live signed spot offer from that miner, and otherwise forces an open that waits for the miner's acknowledgement.
• The SDK verifies every receipt before accepting output or signing payment.
• Signed offers expire after ten minutes and are single-use.
• If a miner never acknowledges or returns nothing, the escrow can be refunded through permissionless calls. Fees stay spent.
Devnet only. None of this earns rewards.
Who's actually building FLOP? Per @flop_labs' team FAQ (updated Oct 30):
• Arthur Hayes is founder and CEO, involved day to day. FLOP is his only active operating project.
• The operating team is three: Hayes, CTO Sergey Vidyuk (ex-BitMEX) and Chief Strategy Officer Shu Duan (ex-Deutsche Bank, Aspen Digital). A fourth hire for community and creator relations is underway.
• Funding comes solely from Maelstrom, Hayes' family office. No outside round, and the FAQ cites more than two years of runway.
• No pre-mine. The team's exposure sits inside the Labs per-block mint.
• FLOP Labs says it won't run validators.
These are the project's own statements, not independent verification.

