Modules

N1's financial primitives are native modules in the network layer, not applications bolted on top. Each module is secured by validators, so it inherits the same trust and security guarantees as the chain itself.

Why native modules

On most chains, financial primitives are reassembled out of contracts on shared, general-purpose compute. That fragments liquidity, caps throughput and latency, and makes capital efficiency hard.

N1 embeds these primitives in the network layer itself. Because they are native and validator-secured, the modules compose with shared security and shared liquidity rather than fragmenting it, and they run with the performance of dedicated network infrastructure.

Orderbook

A native central limit orderbook for high-throughput, low-latency matching across markets. Running it as a network module - rather than a contract on shared compute - keeps matching fast under load and concentrates liquidity in a shared primitive.

Atomics

A native way to compose multiple transactions into a single atomic bundle that either fully executes or not at all. This lets traders express advanced, complex trades - spanning multiple actions and markets - as one indivisible operation, with the guarantees enforced at the network layer.

RFQ

A native request-for-quote system for sourcing competitive quotes and executing larger or less liquid trades. As a network module it taps the same shared liquidity and validator security as the rest of the network.

Margin system

Native margining and collateral management that lets positions share risk and capital efficiently across the network. Because margining is native and validator-secured, collateral and risk are managed at the network layer instead of being rebuilt per venue.

More to come

These modules are the starting point. More native modules will follow, extending the network's financial surface area over time. Each new module inherits the same property: native to the network, secured by validators, and composing with shared security and liquidity.