Skip to content
This repository was archived by the owner on Dec 8, 2025. It is now read-only.

docs: order book architecture #109

Open
bguiz wants to merge 2 commits into
base: master
Choose a base branch
from
Open

docs: order book architecture #109

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
57a622a
docs: add root page for CLOB in /defi/order-book
bguiz Aug 27, 2025
1623c2e
docs: add architecture page for CLOB in /defi/order-book/architecture
bguiz Sep 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions .gitbook/SUMMARY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,11 @@
* [Wallet](defi/wallet/README.md)
* [Create a wallet](defi/wallet/create.md)
* [Accounts](defi/wallet/accounts.md)
* [Token Standards](defi/tokens/README.md)
* [INJ coin](defi/tokens/inj-coin.md)
* [Token Factory](defi/tokens/token-factory.md)
* [CW20 Standard](defi/tokens/cw20-standard.md)
* [Order Book](defi/order-book/README.md)
Comment on lines +8 to +12
Copy link

@coderabbitai coderabbitai bot Sep 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Indentation is wrong: “Token Standards” is not under Wallet.

Current two‑space indent makes it a sibling of Wallet. Use four‑space indent to nest under Wallet.

-  * [Token Standards](defi/tokens/README.md)
-    * [INJ coin](defi/tokens/inj-coin.md)
-    * [Token Factory](defi/tokens/token-factory.md)
-    * [CW20 Standard](defi/tokens/cw20-standard.md)
+    * [Token Standards](defi/tokens/README.md)
+      * [INJ coin](defi/tokens/inj-coin.md)
+      * [Token Factory](defi/tokens/token-factory.md)
+      * [CW20 Standard](defi/tokens/cw20-standard.md)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* [Token Standards](defi/tokens/README.md)
* [INJ coin](defi/tokens/inj-coin.md)
* [Token Factory](defi/tokens/token-factory.md)
* [CW20 Standard](defi/tokens/cw20-standard.md)
* [Order Book](defi/order-book/README.md)
* [Token Standards](defi/tokens/README.md)
* [INJ coin](defi/tokens/inj-coin.md)
* [Token Factory](defi/tokens/token-factory.md)
* [CW20 Standard](defi/tokens/cw20-standard.md)
* [Order Book](defi/order-book/README.md)
🤖 Prompt for AI Agents 
In .gitbook/SUMMARY.md around lines 8 to 12, the "Token Standards" section is
indented with two spaces, placing it as a sibling of "Wallet" instead of nested
under it; increase the indent to four spaces for the "Token Standards" line and
all its child list items (INJ coin, Token Factory, CW20 Standard) so they are
correctly nested under Wallet and maintain consistent indentation for the block.

Copy link

@coderabbitai coderabbitai bot Sep 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Indentation is wrong: “Order Book” should be under Wallet; add Architecture subpage.

Fix nesting and include architecture.md to surface the deep dive.

-  * [Order Book](defi/order-book/README.md)
+    * [Order Book](defi/order-book/README.md)
+      * [Architecture](defi/order-book/architecture.md)
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
* [Order Book](defi/order-book/README.md)
* [Order Book](defi/order-book/README.md)
* [Architecture](defi/order-book/architecture.md)
🤖 Prompt for AI Agents 
In .gitbook/SUMMARY.md around line 12, the "Order Book" entry is incorrectly
top-level instead of nested under "Wallet" and you need to add an "Architecture"
subpage; move the "* [Order Book](defi/order-book/README.md)" line to be
indented under the Wallet section (increase indentation by two spaces or one tab
to match other subitems) and add a new line for the architecture deep dive such
as "* [Architecture](defi/order-book/architecture.md)" as a sibling to Order
Book under the Wallet group, ensuring the path and indentation match the rest of
the SUMMARY.md structure.

* [Trading](defi/trading/README.md)
* [Order Types](defi/trading/order-types.md)
* [Trading Fees and Rebates](defi/trading/fees.md)
Expand All @@ -19,10 +24,6 @@
* [Pre-Launch Futures](defi/trading/derivatives-pre-launch-futures.md)
* [Index Perpetual Futures](defi/trading/derivatives-index-perpetual-futures.md)
* [iAssets](defi/trading/derivatives-iassets.md)
* [Token Standards](defi/tokens/README.md)
* [INJ coin](defi/tokens/inj-coin.md)
* [Token Factory](defi/tokens/token-factory.md)
* [CW20 Standard](defi/tokens/cw20-standard.md)
* [Bridge](defi/bridge/README.md)
* [From Ethereum](https://blog.injective.com/en/how-to-bridge-from-ethereum-to-injective-using-metamask/)
* [From Solana](https://blog.injective.com/en/how-to-bridge-from-solana-to-injective-using-phantom/)
Expand Down
14 changes: 14 additions & 0 deletions .gitbook/defi/order-book/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Central Limit Order Book (CLOB)

The cryptocurrency industry is experiencing a renewed fascination with Central Limit Order Books (CLOBs). Across crypto social media, research reports, and development communities, on-chain orderbook infrastructure has emerged as one of the most discussed topics of 2024 and 2025. New projects are launching with significant fanfare, promising to bring "institutional-grade" trading experiences to decentralized finance. Venture capital is flowing toward CLOB-focused startups, and the narrative has crystallized around the idea that on-chain orderbooks represent the next evolutionary leap for decentralized exchanges: a sophisticated alternative to the Automated Market Maker (AMM) model that has dominated DeFi since Uniswap's rise.

Yet this narrative treats on-chain CLOBs as a recent innovation, with most discourse focusing on newly-launched projects. The industry speaks of "pioneering" new approaches to orderbook infrastructure, connoting that the concept of on-chain CLOB infrastructure is being invented for the first time. This framing, while understandable given the current hype cycle, obscures a crucial historical reality.

Injective has been operating a decentralized, fully on-chain CLOB infrastructure since its inception. Founded in 2018 and incubated by Binance Labs that same year, Injective launched with comprehensive orderbook functionality supporting spot trading, perpetual futures, expiry futures, and binary options markets. For seven years, Injective has been quietly solving the technical challenges that the broader crypto community has only recently begun to grapple with.
Most CLOB-based projects emerging on the scene face fundamental constraints, as they are built within virtual machine (VM) environments. These solutions, whether on Ethereum, Solana, Aptos, Sui, or other execution environments, suffer from gas economics, computational overhead, and architectural boundaries. Additionally, many implementations rely on Layer-2 scaling, off-chain components, or hybrid architectures that compromise the decentralization that motivated moving away from centralized exchanges.

To be fair, Injective is not the only project to recognize these architectural limitations. Hyperliquid, which launched in 2022 and has captured massive attention in the current CLOB narrative, has also built a custom L1 to avoid VM constraints. However, it employs a dual architecture, splitting state execution between HyperCore and HyperEVM, introducing development complexity and performance implications for applications hoping to leverage the CLOB.

Injective's approach is fundamentally different: implementing orderbook functionality as a native blockchain module rather than an application layer. This enables permissionless plug-and-play access for any application built on Injective, eliminating cross-layer complexity while executing sophisticated financial operations without gas optimization constraints or architectural compromises.
Copy link

@coderabbitai coderabbitai bot Sep 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Accuracy: “without gas constraints” is misleading.

Even as a native module, transactions still incur base fees/gas. Rephrase to “reduced sensitivity to VM gas metering; fixed trading fee model.”

-...without gas optimization constraints...
+...with reduced sensitivity to VM gas metering and a fixed trading fee model...
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Injective's approach is fundamentally different: implementing orderbook functionality as a native blockchain module rather than an application layer. This enables permissionless plug-and-play access for any application built on Injective, eliminating cross-layer complexity while executing sophisticated financial operations without gas optimization constraints or architectural compromises.
Injective's approach is fundamentally different: implementing orderbook functionality as a native blockchain module rather than an application layer. This enables permissionless plug-and-play access for any application built on Injective, eliminating cross-layer complexity while executing sophisticated financial operations with reduced sensitivity to VM gas metering and a fixed trading fee model or architectural compromises.
🤖 Prompt for AI Agents 
In .gitbook/defi/order-book/README.md around line 12, the sentence claims
Injective executes sophisticated financial operations "without gas optimization
constraints or architectural compromises," which is misleading; update the
wording to indicate that native module design reduces sensitivity to VM gas
metering and uses a fixed trading fee model. Replace "without gas optimization
constraints" with phrasing like "reduced sensitivity to VM gas metering; fixed
trading fee model" and ensure the sentence still communicates native-module
benefits while acknowledging transactions still incur base fees.


This paper provides a comprehensive examination of Injective's on-chain CLOB infrastructure, explaining both how it works and why its architectural approach offers inherent advantages over alternative implementations. We will explore the Exchange module's (Injective’s CLOB infrastructure) design, detail its key innovations such as the Frequent Batch Auction mechanism for front-running prevention, and analyze how chain-level implementation enables capabilities that remain difficult or impossible to achieve within virtual machine environments. By understanding Injective's technical architecture, we can better appreciate both its significance as the original on-chain CLOB implementation and its strategic positioning as the crypto industry rediscovers the power of decentralized orderbook infrastructure.
Loading