OSNIAS CLEARING
🇫🇷 Français🇬🇧 English
Book VII · O-POP Osnias · Mainnet · Private RPC · Resilience

O-POP Osnias

Book VII presents the target server and network architecture of an Osnias Point of Presence for Mainnet operations. It describes the separation between private RPC access to the Sei network, the dedicated end-user network, the local Administration LAN, Osnias-Core servers dedicated to netting computation, reconciliation with Ethereum escrow, and the principles of security, operational neutrality and redundancy.

Book VII · Release 1.0 · 30 September 2026

English PDF French PDF Zenodo DOI

Book VII describes the target architecture of an Osnias Point of Presence: private RPC access to the canonical Sei ledger, a dedicated end-user network, an isolated Administration LAN, Osnias-Core servers for netting computation, reconciliation with Ethereum escrow, A/B redundancy, and principles of resilience and operational neutrality.

Osnias Clearing — O-POP Mainnet server and network architecture
Architecture

A secure, neutral and redundant point of presence

The O-POP provides controlled access to the canonical Sei ledger without creating a private blockchain network. The end-user RPC network is dedicated and separated from the local 10.x.x.x Administration LAN. Critical functions are deployed with A/B redundancy to reduce single points of failure and preserve service continuity during clearing, freeze, netting and reconciliation phases.
Functional separation

RPC, computation, administration and escrow remain distinct

Sei RPC servers follow and expose the canonical network state; Osnias-Core performs netting computation and invariant checks; the Administration LAN remains isolated from user access; Ethereum provides the escrow and collateral layer. This separation allows each function to be sized, secured, audited and supervised independently.
Access security

Dedicated VPN, traceability and access control

Operational access to the O-POP can be protected through a dedicated VPN connecting authorized components and approved operational teams to the local infrastructure. This access layer adds a security boundary distinct from the public network by controlling entry points, segmenting traffic, logging connections and retaining trace data useful for audit and incident analysis. Combined with the separation between the end-user network, private RPC layer and Administration LAN, it strengthens operational traceability and reduces direct exposure of critical components.