
DeepBook
Tier B1. Protocol Core Thesis & Architecture
DeepBook is an engineered Arbitrum Orbit deployment within the DeFi sector operating on ARBITRUM. Built as part of the Arbitrum Nitro Optimistic Rollup, DeepBook addresses liquidity efficiency and trust-minimized user execution. DeepBook is the first native central limit order book (CLOB) on the Sui blockchain. It works as a shared liquidity layer that other Sui protocols, including spot DEXes and margin-trading apps, route through for order matching and deep liquidity. Trades settle in roughly 390 milliseconds. DeepBook was built by Mysten Labs, the team behind Sui, and sits underneath much of the chain’s trading activity, so order flow reaches it from many of Sui’s DeFi front-ends. By participating in the early distribution phase, users establish on-chain provenance before protocol decentralization.
2. Airdrop Allocation Mechanics
The protocol operates a structured reward architecture designed to distribute native governance weighting to authentic liquidity providers, testnet validators, and transaction originators. Unlike standard promotional campaigns, DeepBook's tokenomics prioritize multi-epoch engagement. Points accrued through protocol interactions correlate directly to snapshot weightings, penalizing sybil clusters and inactive addresses while compounding rewards for sustained weekly volume.
Strategic Sybil Defense & Risk Assessment
**Estimated Capital Required:** Minimal to Free Testnet interactions. Network gas profile: Very Low ($0.08-$0.20). **Sybil Defense Standard:** Cluster analysis and multi-month continuous engagement. We recommend maintaining a clean wallet history with diverse protocol interaction timestamps. **Farming Velocity:** 14.9k Farming actively tracking this protocol. Current ecosystem heat metric: 16.8k. **Smart Contract & Operational Risk:** Moderate - active testnet or early dApp stages. Always verify domain TLS certificates and never permit unverified token spend approvals.
Actionable Qualification Checklist
Complete each step sequentially to maximize snapshot weight.


