One Chain. One Token. Many Applications.
Pickle is a real-time Ethereum Layer 2 built on one conviction: the value an ecosystem creates should concentrate, not evaporate. Applications keep the majority of what they earn, the rest flows on-chain into a single asset. Every app. One token. Forever.
Lane cadence illustrates the scheduling targets. The head block and the figures below are live from this node's RPC.
00 / Verifiable by design
Every claim on this page is checkable on-chain or in the whitepaperAudited claim contract
The ABX migration claim is replay-protected and audited before it opens. No claim without a published report.
A public event per settlement
The fee router emits a settlement event every time it splits revenue. The waterfall is auditable, not asserted.
Snapshot anyone can rerun
Merkle root, script and block height are published so any holder can reproduce the eligibility set themselves.
Two security council seats
Elected collectively by Verified applications. Treasury and unvested balances cannot vote.
01 / The problem
Ecosystems don't die
from slow blocks.
They die from scattered value.
Blockspace is abundant and getting cheaper. What's scarce is useful applications, real users, and a community still willing to participate after being asked to buy its fifteenth token.
Application value never reaches the chain
A DEX doing real volume earns far more than the gas it pays. That revenue leaves the ecosystem entirely. The chain supplies security, settlement, users and tooling, and captures a rounding error.
Every app launches a token, and they eat each other
Issuing a token is the default way a team gets paid. A community of a few thousand people is asked to fund fifteen assets, each diluting the others' liquidity and attention. Most go to zero.
Chain tokens are disconnected from the chain
For most L2 tokens there is no mechanism connecting network activity to the asset beyond a governance vote nobody uses. Price reflects narrative, and when the narrative fades, there is nothing underneath.
02 / The Pickle thesis
One chain. One token.
Many applications.
The slogan is not decoration. It is the architecture.
One shared state
A single execution environment. Applications compose in one state, against one liquidity pool, in front of one user base. No fragmentation, no bridging between your own products, no cold start for every new app.
One asset carries the weight
BX is the only asset Pickle issues and the only asset its incentive programmes reward. Apps use the stablecoins, LP positions and receipts they need, but speculation, governance and value accrual live in exactly one place.
Compete on being useful
When you don't have to launch a token to get paid, you build a product instead of a launch. Pickle funds builders from revenue and treasury, so applications compete on utility, not on emissions.
Pickle is a permissionless EVM chain: anyone can deploy anything, including a token. What Pickle controls is what it verifies, features, funds and rewards — the policy is economic, not technical, and we would rather say so than make a claim a five-minute investigation would disprove.
03 / Technology
Real-time execution.
Ethereum settlement.
A custom Rust sequencer executes your transaction the moment it arrives, in deterministic admission order, with a receipt before the block containing it is even sealed. Then Ethereum makes it final.
Immediate execution
No mempool purgatory. Transactions execute on arrival through a bounded admission queue and a native fast path built on revm.
Signed preconfirmations
Mini-blocks stream at a ~10 ms scheduling target carrying receipts, logs, a state-diff hash and a sequencer signature. A commitment, not a guess.
Your tools, unmodified
Standard eth_* JSON-RPC. MetaMask, Foundry and Hardhat work as-is. Solidity contracts deploy without a single change.
DA with a fallback
Sealed blocks compact into batches and commit to Ethereum through a batch inbox. If the DA path fails, batches still land as L1 calldata.
Two timescales, one chain
Execute immediately. Preconfirm at mini-block cadence. Confirm at EVM block cadence. Finalise on Ethereum. We use the word finality for exactly one thing.
04 / Applications
Six surfaces,
one sequencer.
Everything below runs against the same chain, the same state and the same account. Live on this testnet right now.
Faucet
1 ETH + 50,000 BX every 24h. Paste an address — no connect required.
L1 ↔ L2Bridge
Deposit ETH from the local L1 onto Pickle, or withdraw back.
ToolsToolkit
Deploy a token, NFT, collection or multisig. Look up transactions. Stake BX.
IdentityNames
Register a .pkl name. Fees are paid in ETH.
RealtimeMini-blocks
The raw ~10 ms sequencer stream, over WebSocket.
IndexExplorer
Blocks, transactions, traces, transfers, accounts and tokens.
05 / The value engine · PREL
Revenue goes in.
Supply comes out.
The Pickle Revenue Enforcement Layer is a public, on-chain path from application revenue to permanent BX supply reduction. Builders keep the majority. Liquidity providers are never touched.
Registry, router, vault, buyback and burn are Proposed: specified, not yet shipped. Percentages shown are the working base case.
What is never revenue
Capital and work get paid in full, first, permanently. A chain that taxes its own liquidity has no liquidity.
Worked example
A DEX charges a 0.30% swap fee. 0.25% goes to liquidity providers. 0.05% is the protocol's own take.
Swap fee0.30%
To LPs0.25%
Revenue base0.05%
| Registry tier | Ecosystem share | What the application receives |
|---|---|---|
| First-party | 100% | Pickle's own applications: the name service, the DEX. Pickle keeps no builder share from itself. |
| Verified | 40% | Grants, liquidity support, incentive eligibility, verified mark, placement across every Pickle surface. |
| Listed | 15% | Verified mark and directory listing, with reduced support. |
| Permissionless | 0% | Deploys and runs normally, forever. No ecosystem support, and no permission required. This tier is the guarantee, not the punishment. |
06 / BX
Ten billion. No mint function.
One ecosystem asset.
BX is not the gas token. ETH is, and that will not change. BX is where the ecosystem's fee share, coordination and governance weight live.
Costs are paid before value is distributed
Ethereum settlement, data availability, sequencer operations and the standing security budget come out first. Only what's left gets split.
The builder keeps the majority
Every settlement through the router splits on a published schedule, not a negotiated, per-application rate.
Fee share, paid in ETH
Staked BX receives a share of net gas revenue in ETH. Not emissions. A yield paid in the staked token is a transfer from non-stakers, not revenue.
Buyback & burn
A defined share of net revenue acquires BX on the open market and reduces totalSupply(). Permanently.
Utility that isn't speculation
.pkl registration at a published discount, application bonds, and priority-lane access keyed to staked BX.
Governance
Staked BX votes on fee rates, registry tiers, incentive schedules and treasury spend. Treasury and unvested balances cannot vote.
Three things we will not say
We will not promise a price effect. A buyback is a demand flow of fixed currency size, not fixed token size. That is a mechanical property, not a floor.
We will not project a yield. The staking interface shows realised historical distributions and nothing else. When the chain earns little, stakers earn little.
We will not describe BX as equity. BX confers no ownership of, claim on, or entitlement to the assets, revenues or profits of any entity.
07 / ABX community migration
The community comes
with us.
1,500,000,000 BX RESERVED
Pickle reserves 15% of total BX supply for verified historical AlphBanX holders: a discretionary allocation recognising an existing community.
50% liquid at claim, 50% vesting linearly over 12 months.
Eligibility excludes team, investor, treasury and protocol-contract balances, classified by address at the snapshot block.
Ratio is an output, not an input: 1,500,000,000 ÷ eligible ABX at snapshot.
How the claim works
- 01Snapshot at a published historical block, taken before the ratio is announced.
- 02Balances decomposed; insider and contract addresses classified and published.
- 03Merkle root, snapshot script and block height published so anyone can reproduce it.
- 04Audited, replay-protected claim contract goes live.
- 0512-month claim window. Unclaimed BX returns to the ecosystem treasury.
This is not compensation, restitution or recovery, and it does not restore any prior market value. Pickle Chain is a separate project on separate infrastructure. The ratio will not be published until the snapshot is complete and independently reproduced.
08 / For builders
Get paid in revenue.
Not in your own token.
Most application teams monetise by issuing a token to their users. Pickle offers the alternative: cash from day one, plus capital and distribution from an ecosystem that wants you to win.
| Pickle receives | You receive |
|---|---|
| 40% of net protocol take (Verified tier) | 60% retained, in cash, from day one |
| Registry compliance and public revenue reporting | Grants and milestone funding from a 12%-of-supply builder allocation |
| A commitment not to launch a competing speculative token | Liquidity support from an 8%-of-supply allocation |
| Nothing further | Verified mark, homepage and explorer placement, campaign support |
| Nothing further | Two security council seats, elected collectively by Verified applications |
| Nothing further | A user base that isn't being drained by fifteen competing token launches |
09 / Roadmap
Shipped, next,
and honest about both.
No date is attached to any phase, because a date we could not defend would be the first false statement on this page.
Local testnet: the Rust sequencer, mini-blocks, EVM blocks, ETH bridge, block explorer, .pkl name service, token & NFT toolkit, faucet and BX fee-share staking.
Public testnet on an Ethereum test network. Canonical BX token with burn. Aggregated L1 batch posting. Cost-first fee accounting. EigenDA integration. Public RPC and explorer.
Mainnet deployment. Canonical BX distribution. ABX snapshot, audited claim contract and migration opens. Registry and fee router live. First-party DEX. Public revenue dashboard.
Buyback and burn execution, with sealed-bid clearing and an insider denylist. Third-party applications onboarded to the registry.
Token governance. Forced inclusion. Permissionless derivation. A proof or challenge path replacing the trusted bridge messenger. Sequencer redundancy.
10 / Join the network
One chain. One token.
Build the many applications.
Run a node, deploy a contract, claim a name, or bring your application to a chain that pays you in revenue instead of asking you to sell a token.