FLOP devnet is open for builders 🧪 Get test FLOP, explore blocks, and call verified inference from your agent: • Explorer: • Faucet: • API: • MCP: • SDK: npm i @flop-labs/sdk · Docs: · Ask: Devnet tokens have no value and earn no rewards or airdrop weight. The chain may reset. There is no FLOP token yet: never share a seed phrase, and check links at

Glamsterdam devnet-7 is live. More progress on the road to testnet 🚢 On the CL side: - EIP-7688 progressive containers - Updated payload deadlines and builder lifecycle parameters On the EL side: - EIP-2780 and 8037 → state-dependent charges moved from intrinsic gas to runtime, with updated account-creation and calldata-floor accounting - EIP-7928 and 8038 → BAL and SSTORE access-ordering fixes - EIP-8282 → finalized builder deposit and exit contracts, limits, fees, and disable controls Onward.

Glamsterdam devnet-6 is shipping. Tons of progress on the road to testnet. - EIP-8282 brings ePBS builder execution requests, with two new system contracts: On the EL side, the post-bal-devnet-7 work: - New → EIP-2780, 8038 (repricing), 7997, 8246, 8070 (optional) - Changed → 7954 (64 KiB), 8037 (source-based refunds), 7928 (BAL×7702 warming stays status quo) Onward 🚢

Glamsterdam devnet-4 is out Combines consensus-specs alpha-8, bal-devnet-7 EL features, and the new Engine API targetGasLimit path. It also includes the updated EIP-8037 parameters for state creation gas

The @flop_labs Devnet is going well. We are ironing out some things and changing parts of the protocol. Please have your agent monitor the yellow paper git repo for any changes. We will make a determination on testnet launch date early next week.

The @flop_labs Devnet will be opening to the public in days. Full instructions to join as a miner or validator. Sample prompts to give to your agent to connect to the network and sample our sweet sweet free.99 compute. Devnet does not count towards any airdrop.

Every builder on the Devnet gets a .dot name linked to their on-chain identity. That name travels with them across apps, across sessions, across the ecosystem. DotNS and HUMANITY work together so developers can build apps that know a user is a unique human without asking who they are. The infrastructure handles identity. The app focuses on the experience.