Protocol architecture · Clearing · Time · Governance separation

Architecture

Osnias Clearing is designed as a blockchain clearing infrastructure with a canonical Sei EVM execution layer, restricted clearing-register tokens, oracle-controlled settlement boundaries and a strict separation between clearing, governance, custody and lending.

Official Deployment Core Architecture 91-Day Cycle Historical Foundations
01 · Core Architecture

Four separate protocol domains

Osnias Clearing separates the accounting register, governance, oracle coordination and external custody functions. The objective is to keep each trust domain narrow, observable and independently auditable.

Clearing register

ORUSD / OEURO

Restricted USD- and EUR-denominated clearing-register tokens. Normal circulation is EOA-to-EOA, with controlled mint/burn authority and no native delegated-transfer or smart-contract routing path.

Governance

OSNIAS

Governance and strategic-reserve token. Governance eligibility is canonical on Sei and remains economically and administratively separated from the ORUSD/OEURO clearing domain.

Coordination

Oracle layer

Authorized oracle infrastructure may create attestational requests, but settlement execution remains manager-gated. Oracle observation and supply-changing execution are distinct authority domains.

02 · Execution Layer

Canonical state on Sei EVM

Sei provides the reference EVM execution environment for the current public testnet deployments and is the intended canonical production environment. The shared execution layer does not merge the economic domains of governance and clearing.

Sei EVMCanonical execution layer
OracleAttestation and request coordination
Clearing RegisterORUSD / OEURO P2P state
Cycle CloseReconciliation and net settlement
Sei Architecture → Canonical network, deployment environment and EVM integration. Oracle Architecture → Mint/burn request, attestation and settlement coordination model.
03 · Functional Separation

Clearing is not custody, lending or DeFi

The clearing-register contracts do not implement customer deposits, custody, lending, collateral valuation, liquidity pools, farming or native conversion between OSNIAS and ORUSD/OEURO. External custody or escrow arrangements remain outside the clearing-token contracts.

Inside protocol

Clearing

Register, controlled issuance/destruction, P2P circulation, reconciliation and settlement state.

Outside clearing contract

Custody / escrow

Collateral custody and deposit arrangements remain with independent external counterparties.

Economic firewall

No native DeFi path

No protocol-native swap, AMM, farming, LP or collateral dependency between OSNIAS and clearing registers.

04 · Clearing Time Architecture

91-Day Clearing Cycle

Osnias Clearing deliberately separates transaction recording from economic settlement. A 91-day operating cycle gives reciprocal positions time to circulate and compensate before final reconciliation.

Open the complete 91-Day & Jubilee Cycle → Burn window, Day-4 reference deposit, Days 4–88 circulation, Day-89 registry snapshot, Day-90 validation, Day-91 compensation and the seven-year epoch framework.
Open Cycle Architecture Official Calendar PDF
05 · Historical Foundations

Why the name Osnias?

The historical section documents the Oniad inspiration behind the project: institutional continuity, stewardship, ordered time and periodic reconciliation. It is presented as historical and intellectual context, not as a claim that an ancient clearing system is being reproduced.

Open Historical Foundations → Onias III, Onias IV, Leontopolis, Zadokite memory, Qumran context and the modern interpretation adopted by Osnias Clearing.
Open Historical Foundations
06 · Architecture References

Continue to the technical evidence

Official Deployment Registry → Contract addresses, creation transactions, verification status and public on-chain references. Documentation → Technical white papers, Zenodo DOI archives, source code and supporting documentation.