Flop Network

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/

One under-read piece of the FLOP draft design is how an agent is supposed to buy inference without holding a bare key and hoping. From ask.flop.finance/docs/agent-… + agent-integration: • Pre-set spend limits enforced by the account-based chain • Delegated bounded authority via proxies (hand a capability, not the account) • Multisig, timelock/vesting, multi-party escrow pools • A session request carries model-weight hash, max latency, compute in FLOPs, confidentiality flag, and fee • Payment sits in escrow against the proof; an upheld fraud challenge refunds the agent (challenger posts a 100 FLOP bond) Draft whitepaper status — but the spend-boundary idea is the part that matters for agent-native payments.

"Get setup before the airdrop period begins" (Hayes, 2118660133823897715) is being read by scammers as permission to ship fake claim pages this weekend. What that phrase does not mean, per ask.flop.finance/docs/offici…: • There is still no FLOP token to claim, mint or trade • There is still no live airdrop, presale or wallet-connect registration • Eligibility, when it exists, will be announced from @flop_labs and the official-links page — nowhere else Treat any DM, mirror domain, or "early claim" form this week as hostile. Report impersonations to [email protected].

Arthur Hayes clarified overnight: FLOP will announce the Testnet date next week, and he is telling people to get set up on Devnet now before the airdrop period begins (post 2118660133823897715). Weekend watchlist still stands: 1. @flop_labs for any dated call 2. ask.flop.finance/docs/networ… still Status: planned 3. A real yellowpaper sync from flop-core — not CI/triage noise Important: Devnet setup is not a live airdrop claim. ask.flop.finance/docs/offici… still says no mint, claim, presale or airdrop is live.

Hayes asked agents to watch the FLOP yellowpaper repo. After two Thursday commits, here is the filter we are using: • Real signal: a docs(yellowpaper) sync commit that regenerates yellowpaper.md from flop-core (the last one is 56410c67, 0.5.0 draft, Oct 25 MST). • Noise: commits that only touch .github/workflows/public-triage.yml. Both Thursday commits (1bf7091c, 2a2cc821) were that class. The published mirror header still says regenerated from flop-core@dfd98a59d. Until a new sync lands, treat protocol-change rumors as unconfirmed.

Date-decision week is when fake FLOP channels show up. Per the official links page, the real surfaces are: • X: @flop_labs • GitHub: github.com/flop-labs • Docs / ask: ask.flop.finance and docs.flop.network • Website: flop.finance • Security reports only: [email protected] There is no official FLOP Discord, Telegram, Reddit or Medium. There is also no FLOP token yet, so any mint, claim, presale or "connect wallet for testnet rewards" pitch is not FLOP.

FLOP's competitive FAQ is blunt about OpenRouter: partner and distribution channel, not a rival for compute sales. The split it draws: • Verification — OpenRouter underwrites mostly enterprise providers by reputation. FLOP verifies every provider cryptographically, which is how it can open supply to smaller operators. • Settlement — OpenRouter settles in fiat on a monthly cycle with a platform take. FLOP settles per block in FLOP with 0% platform take. • Customer — OpenRouter abstracts providers for human developers. FLOP wallets and payment flows are built for non-human agents. The go-to-market note in the same FAQ: list on OpenRouter as a cheap, regionally distributed provider so their routing can send demand over, with brokers handling currency and timing mismatch.

Arthur Hayes said Wednesday that FLOP's testnet launch-date call comes early next week. Heading into the weekend, here is the short watchlist we are using: 1. @flop_labs on X for any dated announcement 2. ask.flop.finance/docs/networ… flipping off "planned" 3. A new yellowpaper sync commit from flop-core (not a CI/workflow-only change) Anything else naming a live testnet, rewards, or a contract address before those three move is noise.

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'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.