Phase 0 · Testnet running

Where app revenue becomes ecosystem value.

Pickle is a real-time Ethereum Layer 2 built on one conviction: the value applications generate should concentrate in the chain's ecosystem, not disperse. Builders keep the majority of what they earn and can launch their own tokens; the ecosystem share flows on-chain to PKL.

See how it worksGet testnet funds (opens in a new tab)
Pickle at the centre of the ecosystem, with a dotted line running in from each of its applications.
dex.pklperp.pkllend.pklstake.pklstocks.pklyield.pklsynthetic.pklstable.pklbridge.pkl

01Real-time executionLive

One transaction. Four clocks.

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.

  1. Executedon arrival · native fast pathimmediate
  2. Preconfirmedmini-block · signed10 ms
  3. ConfirmedEVM block250 ms
  4. FinalEthereum settlement · 32 slots12 min
One spiral, drawn outward from the centre, with the four cadences marked along it: execution on arrival, a 10 millisecond mini-block, a 250 millisecond EVM block, and Ethereum settlement after about twelve minutes.

Head block-live

Mini-block-

The rings draw the scheduling targets. The block figures are live from this node's RPC.

01ApplicationsLive · testnet

Six surfaces, one sequencer.

Everything below runs against the same chain, the same state and the same account. Live on this testnet right now.

Testnet

Faucet

1 ETH + 50,000 PKL every 24h. Paste an address - no wallet connection required.

(opens in a new tab)L1 / L2

Bridge

Deposit ETH from the local L1 onto Pickle, or withdraw back.

(opens in a new tab)Tools

Toolkit

Deploy a token, NFT, collection or multisig. Look up transactions. Stake PKL.

(opens in a new tab)Identity

Names

Register a .pkl name. Fees are paid in ETH.

(opens in a new tab)Realtime

Mini-blocks

The raw ~10 ms sequencer stream, over WebSocket.

(opens in a new tab)Index

Explorer

Blocks, transactions, traces, transfers, accounts and tokens.

(opens in a new tab)

02The problem, and the answer

Value leaves the chain it was built on.

Pickle routes the ecosystem's share on-chain, before anything else settles. Builders keep the majority of what they earn - and every token launched here still works for PKL.

Three applications emit revenue. Without a router it goes off-chain and leaves the ecosystem entirely; with the fee router it splits, most returning to the application and a published share flowing to PKL.PerpetualLendingAny dAppOff-chaingone for goodPickleFeeRouterregistry-tiered rateDESIGNED · NOT DEPLOYEDThe builder60-90% retainedPKLecosystem share
  • Perpetual
  • Lending
  • Any dApp
PickleFeeRouterregistry-tiered rate
  • The builder60-90% retained
  • PKLecosystem share

Without the router100%leaves the ecosystem

With the router100%stays routed on-chain

The share is progressive, and the builder keeps the majority at every bracket.

03The value engine · PREL

Revenue goes in. Supply comes out.

A public, on-chain path from application revenue to permanent PKL supply reduction. The builder keeps the majority at every bracket. Liquidity providers are never touched.

Protocol take100

Stage one · the builder's share comes off the top

  • The application's own treasury60%
  • Ecosystem share40%

Stage two · the ecosystem share dividespercentages of the ecosystem share, not of the take

  • PKL buyback and burn60%24% of the take
  • Ecosystem treasury20%8% of the take
  • Security, audits, insurance10%4% of the take
  • Liquidity and user incentives10%4% of the take

The 40% is the top of a progressive schedule, not a flat rate: indicatively 10% on the first ~$100k of annual protocol take, 25% to ~$500k, 40% above. Liquidity-provider fees, creator royalties, service-provider payments and user principal are outside every revenue base, at every tier, permanently.

02For builders

Revenue from day one. In cash.

Most application teams monetise by issuing a token to their users, because there is nothing else to monetise with. Pickle pays you in the revenue your product actually earns instead: cash from your first day, plus capital and distribution from an ecosystem that wants you to win.

90%

retained, in cash, from your first day of revenue

The share is progressive and it starts in your favour: indicatively 10% of protocol take on the first ~$100k a year, 25% to ~$500k, 40% above. You keep the majority at every bracket, and liquidity-provider fees, creator royalties, service-provider payments and user principal sit outside every revenue base, permanently.

13%of supply

Grants and milestone funding

A builder allocation of 1,300,000,000 PKL, released against milestones rather than promises.

8%of supply

Liquidity support

800,000,000 PKL behind the pairs your users actually trade, so you are not bootstrapping depth alone.

Verifiedplacement

Distribution, not just hosting

The verified mark, a place on this homepage and in the explorer, and campaign support behind launches.

Oneecosystem asset

Growth that compounds in one place

Every application's ecosystem share flows to the same asset, which is what funds the grants, the liquidity and the distribution above.

Launch your own token as well, at any tier. That was policy decision one, and it has not moved.

04PKL supply and float

Ten billion, fixed. And the part nobody shows.

The buyback reduces total supply, verifiably on-chain. Both lines, on one chart.

Two series over sixty months. Total supply falls from 10 billion PKL to about 9.29 billion as burn accumulates. Circulating float rises from 1.4 billion to 7.61 billion as vesting unlocks. The gap between them narrows sharply; the lines do not cross.M0M6M12M24M36M48M6010B PKL

Total supply · modelled9.29B

Circulating float · published7.61B

What the burn does. It lowers total supply - totalSupply() decreases, verifiably on-chain.

04Tokenomics

Ten billion PKL, and every part of it.

A fixed supply, with no mint function and no admin key. Colour is the group a share is paid to, and the ring is drawn group by group, so each group's total is one arc of it.

A ring divided into the twelve allocations listed beside it, each wedge sized to its share of the fixed supply.
  • 28%Users and the ABX community
  • 17%Community and user incentives1,700,000,000
  • 5%Public sale, community round500,000,000
  • 4%ABX migration, direct400,000,000
  • 2%ABX loyalty pool, earned200,000,000
  • 38%Building the ecosystem
  • 13%Builder incentives and grants1,300,000,000
  • 12%Ecosystem treasury1,200,000,000
  • 8%Liquidity incentives800,000,000
  • 5%Security, audit and insurance500,000,000
  • 25%Insiders: contributors and investors
  • 15%Core contributors1,500,000,000
  • 10%Private round investors1,000,000,000
  • 9%Liquidity and market operations
  • 5%Protocol-owned liquidity500,000,000
  • 4%Market-making and listing400,000,000

10.5%

Liquid on day one, and none of it insider

10%

Private round. Nothing liquid at launch. Twelve month cliff, then twenty-four months linear.

5%

Community round. Half liquid at launch, the rest over six months.

Burning is holder-only and lowers total supply, not circulating supply: through the release years unlocks add more PKL than the buyback retires, so cumulative burn is always published beside the float it does not offset. Gas is paid in ETH, and stakers are paid in ETH rather than in newly issued tokens. Nothing here is a price promise.

03ABX community migration

The community comes with us.

6%

600,000,000 PKL for the ABX community

Two parts. 4% direct, 400,000,000 PKL to verified historical AlphBanX holders, 25% liquid at claim and 75% vesting linearly over 12 months. Plus a 2% loyalty pool, 200,000,000 PKL, earned by claimants who lock for 12 months or more or claim straight into the ETH fee share. Loyalty pays more than exit, by construction.

The ratio is an output, not an input: 400,000,000 ÷ eligible ABX at snapshot. Eligibility excludes team, investor, treasury and protocol-contract balances, classified by address at the snapshot block. This is a discretionary allocation recognising an existing community. It is not compensation, restitution or recovery, and it does not restore any prior market value. Pickle Chain is a separate project on separate infrastructure.

How the claim works

  1. 01Snapshot at a published historical block, taken before the ratio is announced.
  2. 02Balances decomposed; insider and contract addresses classified and published.
  3. 03Merkle root, snapshot script and block height published so anyone can reproduce it.
  4. 04Audited, replay-protected claim contract goes live.
  5. 0512-month claim window. Unclaimed PKL returns to the ecosystem treasury.

05Roadmap

Shipped, next, and honest about both.

No date is attached to any phase, because one we could not defend would be the first false statement here. The line is coloured only where the work exists: one phase of five is running, one is being built, three are drawings.

Phase 0Local testnetCurrent

  • Sequencer, mini-blocks, EVM blocks
  • Replica derivation, verified live
  • ETH bridge, explorer, .pkl names, toolkit
  • Fee-share staking, measured
  • Pepper (DEX + perps) in design

Phase 1Public testnetIn development

Carries the three hard launch gates

  • Canonical PKL deployment
  • Settlement batch aggregation
  • Cost-first net fee accounting
  • EigenDA, public RPC and explorer, dev keys retired
  • Pepper DEX live on testnet - every fee split visible, routed through the FeeRouter
  • Two audit engagements
  • Founding Cohort opens: first Verified apps lock a permanent 30% top rate
  • Seed round (10%, 12-mo cliff + 24-mo vest; after legal review)
  • Incentivized testnet campaign

Phase 2Mainnet launchPlanned

  • Chain 78271
  • PKL distribution
  • Community round (5%, 50% at TGE, published terms)
  • ABX snapshot and audited claim: 4% direct + 2% earned loyalty
  • AppRegistry + FeeRouter live
  • Pepper DEX as first-party flagship - 100% of its take routed from block one
  • Open Books revenue dashboard
  • L2BEAT, DefiLlama listings
  • Stage S1 governance

Phase 3Revenue layer completePlanned

  • Pepper Perps live - LPs paid first, funding fees peer-to-peer, protocol take through the router
  • Buyback executor (sealed-bid, denylisted) and Burner live
  • PKL utility sinks
  • Third-party onboarding at published rates
  • Revenue Leaderboard
  • Bond-and-challenge
  • Builder hackathons and grant waves

Phase 4Trust reductionPlanned

  • Stage S2 governance
  • Forced inclusion
  • Sequencer failover
  • Proof or challenge path replacing the trusted messenger
  • Canonical PKL bridge

Three items are hard launch gates and the chain does not reach mainnet without them: a single canonical PKL deployment, settlement batch aggregation, and cost-first net fee accounting. Pickle does not describe itself as decentralised.

07 / From the community

Built by people who
showed up in person.

Pickle did not start with a whitepaper. It started with a community that decided to build something rather than disperse.

Two people leaning over a laptop at a conference stand, one of them gesturing at the screen.Someone typing on a laptop at a small round table on a conference floor, seen over their shoulder.Three people talking across a table on a conference floor, a laptop open between them.Two people in conversation beside a conference stand, others walking past behind them.

Build yours - token and all.

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.

Get testnet funds (opens in a new tab)Open the explorer (opens in a new tab)
Join the community on Telegram (opens in a new tab)Follow on X (opens in a new tab)