Permissionless Perps Explained: What BIP-1 Means for Onchain Derivatives

Permissionless perpetuals are perp markets that anyone can list onchain without exchange approval, gatekeeper sign-off, or business development. BIP-1 is BULK Exchange’s proposal to bring this to a high-performance orderbook DEX. If it ships as specified, it is the most consequential change to derivatives market structure since Uniswap v2.

This page explains what “permissionless perps” actually means, why no orderbook DEX has shipped it credibly before, and what BIP-1 changes.

What “Permissionless” Actually Means

In every current perp DEX — Hyperliquid, dYdX, Drift, GMX, Aevo — listing a new market requires:

• Internal exchange approval
• An oracle integration the exchange controls
• A risk parameter set the exchange writes
• A market launch the exchange schedules

This is not permissionless. It is centrally curated, even when the matching is non-custodial.

A truly permissionless perp market means:

1. Any wallet can deploy a new perp market
2. The market goes live without exchange intervention
3. The exchange’s matching engine processes it the same as any other market
4. Risk parameters are set by the market deployer (within protocol-level bounds)
5. Oracle and funding mechanisms are pluggable

This is what permissionless spot trading became with Uniswap v2 in 2020: anyone could list any token pair, and the AMM didn’t care.

Why This Hasn’t Happened on Orderbook DEXs

Two reasons:

1. Matching engine architecture

AMMs are stateless per pool — adding a new pool is just deploying a contract. Orderbook DEXs have shared matching infrastructure, fee distribution, liquidation engines, and risk systems. Adding a market historically meant adding code paths.

2. Risk surface

A bad perp market with garbage oracles or wrong parameters can drain the entire insurance fund through cascading liquidations. Centralized listing exists because the risk model assumed the exchange was on the hook.

BULK’s architecture addresses both: the matching engine treats markets as data, not code, and risk is isolated per market with parametric guarantees.

What BIP-1 Specifies

BIP-1 is the first BULK Improvement Proposal. Its scope:

• Permissionless market creation: any wallet can submit a market spec onchain.
• Oracle flexibility: the market deployer chooses among approved oracle types (Pyth, Switchboard, internal TWAP, or custom signed feeds).
• Risk isolation: each market has its own insurance allocation. A bad market cannot contaminate good markets.
• Listing bond: market deployers post a bond that funds initial insurance and is slashable if the market misbehaves.
• Quality scoring: markets earn discoverability based on volume, spread, and uptime. Bad markets are deranked but not censored.
• Validator vote for protocol-tier markets: markets that want top-tier insurance backing and main-UI listing can opt into a validator approval flow, but this is opt-in, not gating.

The full BIP-1 spec is in the BULK governance forum. Read it directly — the parameter tables matter.

Why This is the Uniswap v2 Moment

Uniswap v2 didn’t invent AMMs. It made them permissionless. The result:

• Long-tail liquidity exploded
• Token launches moved onchain
• New market structure (memecoins, fair launches, LP farming) emerged
• Centralized exchanges lost the listing monopoly

Permissionless perps on a fast orderbook will produce equivalent structural changes:

• Long-tail derivatives: perps on illiquid tokens, prediction markets, real-world assets, indices
• Fair-launch perps: new token? Launch the perp the same day, no application
• Onchain-native funding markets: market deployers compete on funding rate design
• Cross-margin baskets: custom index perps that benefit from BULK’s portfolio margin

What’s Different About Doing This on BULK Specifically

Three architectural prerequisites that BULK already has:

1. 5–20ms matching latency. Permissionless markets only matter if they trade well. A slow orderbook with thousands of dead markets is worse than a curated one with ten good markets.

2. Portfolio margin. Long-tail perps are only safe if they can be netted against major positions. BULK’s correlation-adjusted margin makes a small altcoin perp position cheap to hedge.

3. Validator-replicated matching. Risk is enforced at the consensus layer, not by an exchange operator. A misbehaving market cannot be unilaterally manipulated.

No other orderbook DEX has all three.

Risks and Open Questions

Honest list:

• Listing spam. The bond size has to be calibrated. Too low and you get thousands of dead markets. Too high and “permissionless” is theatre.
• Oracle attacks. Pluggable oracles mean pluggable attack surface. The approved oracle types and quality scoring are doing heavy lifting here.
• Discovery problem. With 1,000 markets, how do users find the right one? UI deranking helps, but information architecture matters.
• Insurance fund dynamics. Per-market isolation is correct in theory; the per-market bond sizes and slashing conditions are the practical question.

These are calibration problems, not architectural ones. They’re solvable.

What to Watch

If BIP-1 passes governance and ships on schedule:

• Expect the first permissionless markets within weeks of activation
• Expect a wave of long-tail perp markets on Solana ecosystem tokens
• Expect copycat specs from other perp DEXs within 3–6 months
• Expect BULK validator count to grow as market-deployment fees become a meaningful revenue stream

Related Reading

• BIP-1: Permissionless Perps Proposal — the official spec and governance status
• BULK Exchange Architecture Deep-Dive — the technical prerequisites BIP-1 relies on
• Portfolio Margin Explained — why cross-margin makes long-tail perps cheap to hedge
• BULK Exchange Overview
• BULK Token TGE — how BIP-1 governance drives token demand

→ Browse the full BULK Exchange glossary