For everyone / Before you rely on any of it
Glossary
Every term this documentation leans on, defined by what it means to someone deciding whether to trust it. The developer glossary defines the same words by their shape on the wire.
| Term | Meaning |
|---|
| Layer 2 | A chain that runs on its own but publishes a checkable record of itself to Ethereum, so its state can be reproduced from public data. |
|---|
| Sequencer | The single process that receives, orders, executes and seals every transaction. |
|---|
| Mini-block | A signed bundle of the transactions executed in one interval, sealed at a 10 ms scheduling target. A preconfirmation. |
|---|
| EVM block | An Ethereum-shaped block wrapping the interval's mini-blocks, sealed at a 250 ms scheduling target. The confirmation wallets and explorers see. |
|---|
| Preconfirmation | The sequencer's signed commitment to an ordering and an outcome. Evidence against it if a later block contradicted it. |
|---|
| Confirmation | Inclusion in a sealed EVM block. |
|---|
| Finality | Ethereum settlement: the data needed to re-derive the block is committed to Ethereum, and that commitment is itself final. |
|---|
| Scheduling target | The interval the sequencer aims to seal at. Not a latency guarantee and not a throughput claim. |
|---|
| Term | Meaning |
|---|
| Operator | The party running the sequencer. A user relies on its honesty, plus the public data needed to check it. |
|---|
| Replica | A second copy of the chain that re-executes everything from the public record and halts permanently on any mismatch. It can detect; nothing on-chain arbitrates. |
|---|
| Derivation payload | A block's full transaction list with its range, parent hash, block hash and committed timestamp. What a replica replays. |
|---|
| Data availability | The content-addressed layer payloads are stored in, keyed by their hash. If it fails, the payload goes to Ethereum as calldata. |
|---|
| Inbox | The Ethereum contract that receives one commitment per aggregation window from the batcher key and emits the indexed event every verifier follows. |
|---|
| Aggregation window | The 60 s scheduling target at which one commitment for many blocks is posted to Ethereum. |
|---|
| Messenger | The trusted key that finalises bridge transfers in both directions. It can delay; it cannot forge or replay. |
|---|
| Forced inclusion | A path by which Ethereum could force a transaction into the chain. Pickle has none. |
|---|
| Term | Meaning |
|---|
| Gas | The unit a transaction's work is measured in. Paid in ETH, permanently. |
|---|
| Net basis | What remains of gas fees after settlement, data availability, operations and security are paid. The only base anything is distributed from. |
|---|
| The split | 40% PKL buyback, 30% PKL stakers in ETH, 20% treasury, 10% security, of net gas revenue. |
|---|
| Fee-share vault | The staking contract: stake PKL, receive ETH, unbond over seven days. Not a validator bond; no slashing; never PKL emissions. |
|---|
| Protocol take | An application's own revenue. Never liquidity-provider fees, interest, royalties, service payments or user money. |
|---|
| Ecosystem share | The marginal 0/6/12/18% of protocol take an application routes through the FeeRouter above $100,000, $500,000 and $1,000,000 a year. |
|---|
| FeeRouter | The contract that receives protocol take, splits builder retention from ecosystem share, and emits a public revenue event. |
|---|
| Buyback | PKL acquired with ecosystem revenue, primarily through a sealed-bid batch auction, and burned. |
|---|
| Float | The PKL actually in circulation, as opposed to the total that exists. Rises during the vesting years; the burn reduces total, not float. |
|---|
| Term | Meaning |
|---|
| PKL | The ecosystem token: ten billion, minted once, no mint function, no owner, holder-only burn. A fee-share and coordination asset, never equity. |
|---|
| Burned | Total supply reduced, verifiable from the token's supply. Never used to mean locked or held aside. |
|---|
| Unlocked | Everything that could circulate at a given month, including balances still held in contracts. Always published beside the lower actual float. |
|---|
| Cliff | The period before an allocation begins to vest. Twelve months for contributors and private investors. |
|---|
| Continuity allocation | The 6% of PKL for the ABX community: 4% direct, 2% earned by locking. Not compensation. |
|---|
| Staked PKL | The only asset that votes. Treasury, incentive, reserve and unvested balances cannot. |
|---|
| Term | Meaning |
|---|
| Native oracle | 33 price feeds, 19 real-world, written into every block by one system transaction. The publisher is the sequencer. |
|---|
| Market status | Whether a real-world feed's market is open. Accompanies every answer; positions freeze when it is closed. |
|---|
| Exposure | A long or short position against a feed, collateralised and settled in crypto. Not the asset, not a share, nothing to redeem. |
|---|
| Collateral registry | Where third-party tokenised assets are admitted as collateral with haircuts and circuit-breakers. Pickle issues nothing. |
|---|
| Bridge | Moves ETH between Ethereum and Pickle. Both directions finalise on the messenger's say-so. |
|---|
| Name service | Rents .pkl names that point at addresses, priced by length in ETH or in PKL at a discount. Expiry is instant, with no grace period. |
|---|
| Pepper | The first-party exchange. Constant-product pools; the providers' share of the fee is never touched; the buyback's secondary venue. |
|---|
| Toolkit | NFTs, collections, multisig, multisend, locks, vesting, streams and approvals, each from a form: what it deploys is owned by whoever asked, and what it locks, vests or streams follows only the contract's rules. |
|---|
| Explorer | The chain's complete history, internal call traces included, and where the verified mark on an application lives. |
|---|
| Verified | Revenue verified through the router. Not token endorsed. |
|---|
For the precise developer-facing definitions, including method names and field shapes, see the developer glossary.