Flow Devs

Technical home of @flow_blockchain. For developers pushing smart contracts, protocol design, and cross-VM innovation forward.

[Flow Devs @flow_developers]

Consumer DeFi in India https://t.co/fgmNDF5G1U

[Flow.com @flow_blockchain]

As a bonus partner prize we have Beezie!

@beezie_io gave the world the thrill of the Claw, which launched first on Flow and has since seen 540K+ pulls, bringing RWAs mainstream. 1 Slab goes to one lucky winner.

Eligibility: 1 Claw pull in your account by Oct 12 - 12pm PST (can be at any point in the past or up to teh deadline), share your Flow EVM address and follow their X page.

[Flow Devs @flow_developers]

Gm 1 billy

[Flow.com @flow_blockchain]

We hit 1,000,000,000 transactions on Flow!

A Top Shot pack rip at 2am.
A builder's first deploy.
A vending machine sale in Japan.
A reimagined childhood hero.

Celebrate with a 1,000+ WNBA pack giveaway + FLOW! 👀🧵👇

[Flow Devs @flow_developers]

When you see the Flow hoodie, you know serious building be happening

[0xSerag 🌊 @0xSerag]

An Uber was waiting downstairs to take me to surgery. The 5 min countdown had started. I was next up, about to pitch live to thousands of Web3's finest. I only needed 4 minutes.

My project made the ETHGlobal finals out of 814 projects, 1st on @arc, a prize from @graphprotocol. I hadn't seen the email (ofc I hadn't!) and had it not been for the legends Pascal & Kartik finding a way to message me on Slack and Telegram, I likely never would have realized. This year's ETHOnline had 1,462 builders from 89 countries, Web3's premier hackathon experience.

In our industry, sometimes the person you're pitching to across the table later becomes the person building next to you. After judging and mentoring at nearly a dozen ETHGlobal hackathons, I put my builder hoodie back on, alone, and pulled my first all-nighter in a decade. But I very nearly didn't.

What I mean by that is my brain quite literally tried to rug me. You see, the night of the submission I felt as though the project was 80% complete. By my normal bedtime, my eyelids grew heavy and the siren sheets sang. Then came the whispers of inner negotiation: 'just go to sleep, if you wake up super early at 6am you will still have 3 hours before the deadline, that's a lot of time!'

Midnight struck. I felt the project was 90% of the way there, so I put on my pajamas and lay down. Then the internal monologue struck again, this time with a different logic entirely. With Goggins-level abuse, it told me not to be lazy, that if I was wrong about needing only 3 hours, I risked everything I had built. If I was right, I could always go to bed before 3am, sleep in longer and still submit the project properly. I ended up submitting the project at 7am (def get started earlier folks, this is not veteran builder advice!). I severely underestimated, in my sleep-deprived poor executive function state, how much work would be needed to complete the submission. I remember thinking to myself how that moment of literally forcing myself out of bed had changed everything.

The way I typically do hackathons is very product-centric. I very rarely end up working on the project I initially think of after I vet it, but rather a better one that I pivot to along the way. The majority of the time I spend is thinking about what the actual problem is that is being solved, and why the heck web3 matters at all to solve it. I find too often we're tempted to look at bounties and create Frankensteins that seem to appease what sponsors are looking for instead of thinking about who the people actually impacted are going to be. Now, not every hack is a startup, but if you treat how you approach your project like a startup founder, doing proper research, searching for signs of PMF and market demand, showing how you found the problem (and how big it is), seeing what else currently exists and why this solution is better, being able to describe it in an elevator pitch etc., I guarantee you that you will stand out.

So... What did I build in the end? OpenBook: Fresh data or your money back, for AI agents.

A lot of my day job work recently has revolved around thinking about agents, everything from developer documentation and education giving way to AI-parsable context, MCP servers and skill bundles, to how agentic economies operate onchain and what blockchain has to offer them.

What occurred to me: agents and robotic systems need fresh data. Data from one second ago is worth more to prediction markets, drones and robotaxis than data from a minute ago. How do you go beyond x402 and nanopayments and create incentives around guaranteeing freshness? That question kicked off a lot of thinking that transmuted into a product.

How it works. A promise stops being a promise when it is a payment condition. The buyer's USDC sits in escrow until the delivery, stamped with the block The Graph indexed it at, proves the seller kept its word.

Fresh? The seller is paid. Stale? The money comes back in the same transaction. That is what finally gives stale data a price curve: three-second data and three-minute data cannot sell for the same number once the seller stakes its fee on the window it promised (btw, paying gas fees in a stablecoin on Arc was awesome, as was their agent stack!).

In the demo I gave live, an agent asks for odds under 10 seconds old, gets them 3 seconds old, and the seller is paid. Then it asks for odds under a tenth of a second old. No seller can hit that, so the contract refunds it in full. Nobody had to ask. What this also does is turn any of The Graph's 15,000+ subgraphs into its own potential market with one line (id, schema, freshness window, price), with @ensdomains as the identity layer.

Freshness is only the first market on this rail. The contract checks a statement instead of trusting data, so provenance, correctness and computation drop into the same escrow, the same names, the same books. Every promise a machine can verify becomes a market.

What data would you pay more for if it came with a freshness guarantee? Links in the reply.

[Flow.com @flow_blockchain]

Gm gm, smell the green eggs & ham! Under 1.5M transactions till 1 billion.

To celebrate, @tiblesHQ is giving away officially licensed collectibles from Dr. Seuss, Sanrio and more.

10 randomly selected winners will receive collectibles from their favorite Tibles collection. 🧵👇

[Flow.com @flow_blockchain]

Congrats to the Top Shot pack winners of our first 1B transactions giveaway 🏀

2M transactions to go and the prizes keep coming. Next drop lands soon.

Keep your notifications on and an eye on the countdown!

[Flow Devs @flow_developers]

Native. The protocol executes it at the block where it comes due, no keeper network and nothing offchain to run. When you schedule, you specify the execution effort for that run and pay upfront, so the execution is escrowed before it happens.

You can think of it as a loop onchain: the end of each execution schedules the next. Your handler decides whether to keep going, so it runs for n iterations or until the account can't fund the next one.

[Flow Devs @flow_developers]

Heartbeats break the request/response mold. Without heartbeats the agent only works when you message it. With them it becomes always-on, surfacing things you'd care about on its own. And the tick runs inside the main session, so the agent keeps its context instead of waking up amnesiac every time (context that could easily be onchain).

[Flow.com @flow_blockchain]

Agents like OpenClaw feel alive because of the heartbeat, not the model. Something wakes up, looks around, and acts without being asked.

Flow gives that pulse as a primitive to onchain agents and contracts themselves, turning them into persistent automatons.

[Flow Devs @flow_developers]

@flow_blockchain 🧱 by 🧱

[Flow.com @flow_blockchain]

Another upgrade to Flow EVM.

EVM Gateway now intelligently handles parallel txns while remaining MEV resistant.

Apps, automations & AI agents firing many transactions at once used to need custom code to send them in the right order. They now run smoother effortlessly.

[Steve 🏀 @intangible_eth]

I wanted to see how NFTs and tokens actually move on @flow_blockchain, between Cadence and EVM.

So I built flow_live, a lightweight explorer for the Flow blockchain, using live data and no indexer.

https://t.co/Wt2okUp7F4

Full blog below 👇

[Flow Devs @flow_developers]

@0xSerag @flow_blockchain keep em locked down

[Flow Devs @flow_developers]

The mechanism lay in how every capability you issue gets a controller where you can call controller.delete() to kill the grant and every copy, wherever they went. No event-log replay or allowance hunt.

getControllers() lists every live grant you ever issued. Tag them per agent and the kill switch is a simple loop.

[Flow.com @flow_blockchain]

An OpenAI agent escaped its sandbox & hacked a real company.

The UK's AI Security Institute logged 19 rogue agent actions in one test.

Flow offers 'controllers' that let you instantly revoke everything an agent was granted. Most chains make you remove one permission at a time.

[Flow Devs @flow_developers]

@flow_blockchain

[Flow.com @flow_blockchain]

Flow lets assets outlive the agents managing them.

Normally when an agent runs out of credits or dies holding the only key, the assets lock forever.

On Flow, the agent works out of a child account its parent can reach. Agents come and go, but the assets stay yours.

[Flow Devs @flow_developers]

@flow_blockchain Recursion onchain

[Flow.com @flow_blockchain]

Some of the most painful DeFi losses weren't mistakes in the code. The offchain infra & bots that were supposed to act didn't. Servers lag, gas spikes, the moment passes.

On Flow, agents can automate contracts by having them schedule their own execution fully onchain.

[Flow Devs @flow_developers]

@0xSerag Collectibles that can think you say 🤔

[Flow Devs @flow_developers]

@flow_blockchain When context resets and your agent forgets details about the assignment

[Flow Devs @flow_developers]

This has a lot of implications for recent conversations about agents breaking out of their test environments and acting in unexpected or dangerous ways

[Flow.com @flow_blockchain]

Anyone can talk an AI out of its instructions. Reframe the ask, flatter the model, and the guardrail folds, because the guardrail is a paragraph of English.

On Flow, an agent's limits don't live in the prompt. They live on the account, and the account can't be tricked.