For everyone / Pickle in plain terms
Why build on Pickle
Five reasons, each a mechanism described elsewhere on this site, then the comparison a builder actually makes and the honest statement of what Pickle is asking for in return.
The short version
Pickle is built for apps that feel instant: what a user does is worked out the moment they do it, and the app can show the result straight away. Users pay tiny fees in ETH, the money they already have, not in a new coin. Anything that runs on Ethereum runs here without changes. Apps get prices of shares, gold and crypto for free from the chain itself. And businesses that make money here keep most of it: nothing at all is owed on the first hundred thousand dollars a year, and never more than 18 percent of anything.
Transactions execute the moment they arrive and return a signed preconfirmation, so an application can show a result without waiting for a block. Fees are paid in ETH, permanently, so a user never has to acquire a chain token to press a button. Execution is the same EVM as Ethereum, pinned to a known version, so contracts, wallets and tooling work unchanged. The protocol publishes 33 price feeds in every block, so an application reads a price without integrating an oracle. And an application that wants ecosystem support routes a published share of its own protocol take through an on-chain router: nothing on the first $100,000 a year, and the builder keeps at least 82 percent at any scale.
Synchronous execution on admission with a write-ahead log, sealed into sequencer-signed mini-blocks at a 10 ms scheduling target and Cancun-shaped EVM blocks at a 250 ms scheduling target; gas in ETH with a one-wei consensus floor and no base-fee burn; revm pinned to Cancun with the documented gaps in bloom filters, archive depth and the fee market; derivation payloads to a content-addressed DA layer with one commitment to an Ethereum inbox per 60 s scheduling target and calldata fallback. Genesis predeploys a price registry and adapter written by one flagged system transaction per block. An application-side registry, router and vault settle a marginal 0/6/12/18 percent of protocol take above $100,000, $500,000 and $1,000,000, with compensated capital and labour excluded from every base and rates set per tier by governed, timelocked vote.
Your users see results immediately
On most chains an application submits a transaction and waits for the next block to know what happened, and the interface spins. On Pickle the sequencer executes on arrival, so the result exists before the call returns, and a signed mini-block follows at a 10 millisecond scheduling target. An application can act on that signature, and the ordinary block, the one wallets understand, catches up on its own rhythm behind it. Mini-blocks are exposed over their own RPC methods and a WebSocket subscription for exactly this use.
That changes what you can build: a game, a trading interface, a chat with payments, a point-of-sale flow, anything where a person is waiting for the screen to change. The confirmations page says exactly what that signature does and does not promise, and you should design against the honest version.
Your users pay in ETH
Every fee on Pickle is in ETH, permanently. Your users do not need to find, buy and hold a chain token before they can use your application; anyone who has ETH can bridge and act. The minimum gas price is one wei, so a flow with many small transactions is not priced out. The fees page explains the decision and what the chain does with what it collects.
Your code and tools work unchanged
The execution engine is the Ethereum Virtual Machine, pinned to the Cancun rules. Solidity contracts deploy unmodified; MetaMask, Foundry and Hardhat speak to the chain through the standard RPC surface: transactions, calls, logs, filters, fee history and gas estimation. Pickle does not claim EVM equivalence. The claim is narrower and measured: compatibility sufficient for the standard toolchain, with bloom filters, archive depth and the EIP-1559 fee market as documented gaps.
The main differences a builder meets: the node keeps a short window of history and the explorer is the archive; the fee market has no base fee; and a small set of methods is refused by design. Each is documented with the reason on the developer side of this site.
You keep most of what you earn
This is the reason that is specific to Pickle. An application that wants ecosystem support settles a published share of its own protocol take through an on-chain router, and that share feeds the ecosystem token. What makes it a builder's argument rather than a tax:
- The first tier is free. Nothing is owed on the first $100,000 of annual protocol take.
- Brackets are marginal and the top rate is 18 percent, so the builder keeps at least 82 percent at any scale, and there is no cliff to hold revenue under.
- Your users' money is never in the base. Liquidity-provider fees, supplier interest, royalties, principal and collateral are excluded permanently. Only the fee you keep for yourself counts.
- Your own token is allowed at every tier. The router settles first and the rest is yours to distribute.
- It is verifiable. Every settlement emits a public event, so the revenue an application reports is checkable on-chain rather than estimated.
The application fee-sharing page has the full schedule, the worked examples, and what the mechanism does not enforce.
Prices arrive with the block
Applications that need a price, of ETH, of gold, of a share, normally fetch it from an oracle and pay for the privilege. Pickle publishes 33 feeds as part of every block, at a canonical address, with market hours respected for the real-world assets. A builder writes against a price that every other application on the chain reads identically, in the same block, without integrating a third party. The oracle page says how a price is formed and what it does not guarantee: the publisher is the sequencer.
The comparison a builder actually makes
| Question | Answer |
|---|---|
| Protocol revenue retained | Pickle: 100%, falling to 82% marginala general-purpose L2: 100% |
| Revenue below $100,000 | Pickle: 100%a general-purpose L2: 100% |
| Grants | Pickle: an allocated share of supply for builder incentivesa general-purpose L2: competitive, discretionary |
| Liquidity support | Pickle: allocated incentives plus protocol-owned liquiditya general-purpose L2: competitive, discretionary |
| Distribution | Pickle: homepage, explorer verification, campaign supporta general-purpose L2: compete with thousands of applications |
| Own token | Pickle: yes, optional, revenue-backed and verifiable through the routera general-purpose L2: yes, as the only route to monetise |
The honest statement of the trade
What Pickle asks for, and what it cannot promise
Pickle offers revenue plus ecosystem support in exchange for a progressive share of protocol take. Whether that beats going it alone depends on how much distribution and capital Pickle actually supplies, an empirical question this documentation cannot settle in advance, and does not pretend to. An application can decline to register and keep everything; it then forfeits ecosystem support, and that is the whole of the consequence.
And everything above runs on one sequencer. The trust model is stated in full on its own page, and it is the page to read before this one is allowed to be persuasive.