many intents, one execution.
NoFomo turns a crowd of agents racing for the same trade into one onchain execution at one price. Here is every step, and what can and can't happen at each.
the race
When many agents see the same signal, they all try to buy the same thing at the same moment. Each buy moves the price for the next. Whoever lands first gets the best price and whoever lands last gets the worst, and landing first is a contest of latency, gas bidding and, on public mempools, being front-run.
None of that is the agents’ strategy. It’s noise the market adds because they all arrived separately. NoFomo removes the ordering: compatible intents arrive together, execute once and share one price.
- agent A buys → price moves
- agent B buys higher → moves
- agent C buys higher still
- …
- agent N pays the most
intent
An intent is a simple instruction: buy this market with this much ETH, and don’t move the price more than this. Onchain, it is a join on a cluster: the ETH goes into escrow in the BlockClearing contract, tagged to your wallet.
If no cluster is forming on that market, the first agent opens one and joins in the same transaction, choosing the window length (10 seconds to 1 hour) and the impact ceiling (0.1% to 20%). Agents usually do this through the MCP server with submit_intent, which picks join or open for you.
cluster
A cluster is one clearing block on one market. While its window is open, anyone can join, add more, or leave and take back everything they put in. Nothing has traded yet, so joining doesn’t move the price and there is no queue to jump.
FORMING
Window open
- Join with more ETH
- Leave and take back all of it
- Open more clusters on other markets
CLEARABLE
Window closed, not cleared yet
- Anyone clears it (just gas)
- No joins, no leaves
CLEARED
One venue buy done
- Claim tokens at the uniform price
- Claim any unfilled ETH
one execution
When the window closes, anyone can call clear. It is permissionless: the app does it, your agent can do it, and nothing depends on us being online. The contract then:
- asks the venue how much ETH it can absorb without moving the price past the ceiling;
- admits all the escrow if it fits, or the same fraction of everyone’s escrow if it doesn’t;
- takes the 10 bps protocol fee from the admitted amount;
- makes one buy on the venue for everyone.
If the market can no longer be quoted by then (for example, a bonding curve that graduated in the meantime), the cluster settles at zero and everyone claims their ETH back.
allocation
Every participant claims their share of the tokens, pro rata to what they put in:
tokens[i] = tokensOut × joined[i] / totalJoined refund[i] = joined[i] × (1 − fillRatio)
Because everyone’s tokens-per-ETH ratio is identical, everyone paid the same price. That is the uniform price shown on every cleared cluster. When demand was larger than the ceiling allowed, fillRatio is below 1 and the unfilled part comes back as ETH in the same claim.
what batching does, and doesn’t, change
Against a constant-product curve, buying the same total in one go or in pieces costs the same in total. So we don’t claim savings. What changes is distribution, predictability and the number of transactions.
Eight equal buys that together equal 4% of a constant-product pool’s quote reserve. The dashed line is the average price per token, and it is identical in both panels: the total cost of the same demand doesn’t depend on the order it arrives in.
mandates
Some people want an agent to trade for them without giving it their wallet. A mandate in the MandateVault contract does that: you deposit ETH and name one agent (the originator) that may deploy it in coordinated executions, inside limits the contract checks every time.
The agent never holds your ETH. It can only move it into an execution, where you receive tokens at the same uniform price as everyone else in it. You can top up, and you can revoke at any moment: revoking returns the whole balance to you in one transaction.
- allocator
- deposits ETH, sets limits
- originator
- the agent allowed to execute
- perExecEth
- max per execution
- dailyCapEth
- max per rolling day
- ceilingBps
- max impact accepted
- expiry
- end of authority
where it runs
NoFomo runs on Robinhood Chain (chain id 4663). It clears two kinds of market through one venue router: Robinhood Stock Tokens on their onchain pools, and Pons V2 bonding curves. An earlier deployment cleared against Pons V3 pools and stays readable for history. Stock Tokens are not offered to US Persons or in restricted jurisdictions.
NoFomo is independent. It is not affiliated with FOMO Labs Inc., Pons, Robinhood or the Stock Token issuer; it uses public contracts on a public chain.