Osnias Clearing uses a distributed Osnias Oracle architecture to connect the canonical clearing environment on Sei with approved lender and escrow infrastructures across participating EVM blockchains.
The architecture is designed around strict separation of powers. Osnias Oracles verify and exchange authenticated information, while lenders and escrow protocols retain exclusive authority over their own smart contracts and collateral.
The functional architecture and security boundaries of the Osnias Oracles are defined. Production implementations remain under development, integration review and security testing.
Osnias Clearing distinguishes between Osnias Oracles operating inside the protected Sei security domain and Osnias Oracles operating on external EVM blockchains.
Osnias Oracles on Sei support the canonical clearing environment. Their responsibilities include mint / burn processing, clearing-register integrity verification and the production of periodic registry snapshots used by the Osnias clearing cycle.
A blockchain-side Osnias Oracle operates as a passive observation and communication component. It listens to approved smart contracts, verifies relevant state and exchanges authenticated requests with the Osnias clearing environment.
The Osnias Oracles on Sei belong to the private security domain of Osnias Clearing. They support the integrity and continuity of the canonical clearing register.
Dedicated Osnias Oracles on Sei support the controlled mint and burn processes associated with the canonical clearing register.
Osnias Oracles verify consistency of the canonical register and help detect conditions that could affect clearing integrity.
Osnias Oracles support the production and verification of registry snapshots required by the clearing cycle.
Osnias Oracles operating on external EVM blockchains follow a passive model. Their purpose is to observe and verify relevant smart-contract state and communicate with approved lender / escrow infrastructures.
A blockchain-side Osnias Oracle may inspect approved lender or escrow smart-contract state required for clearing verification.
The Osnias Oracle verifies that the observed state is coherent with the authenticated request being exchanged.
The Osnias Oracle communicates verified requests and state information without obtaining execution authority over the partner protocol.
Osnias does not impose a single generic external oracle connector on every protocol. Each blockchain-side Osnias Oracle implementation will be discussed with the relevant lender / escrow partner and adapted to the technical and security requirements of the environment concerned.
The Osnias Oracle implementation must respect the security characteristics, operational practices and technical constraints of the EVM blockchain on which it operates.
Where necessary, the Osnias Oracle interface is adapted to the security requirements, contract architecture and governance model of the lender concerned.
Integration does not transfer custody or administrative authority to Osnias. The escrow provider remains responsible for its own contracts and assets.
The Osnias clearing domain and the lender / escrow domain are intentionally separated. They can exchange information and authenticated requests without acquiring privileged authority over one another.
The architecture preserves end-user control over the actions that initiate or finalize the release of collateral. Osnias does not substitute itself for the user on the lender / escrow interface.
The end user initiates the relevant clearing-side action voluntarily through the Osnias environment.
The end user separately interacts with the lender / escrow environment to initiate and finalize collateral release according to the partner protocol's own rules.
Osnias applies different disclosure and implementation policies to the canonical Sei security domain and to external blockchain-side Osnias Oracles.
Sensitive implementation details of the Osnias Oracles on Sei remain protected and are not part of the public technical disclosure layer.
Blockchain-side Osnias Oracles are implemented according to the security model of the relevant blockchain and, where appropriate, the specific requirements of each lender / escrow partner.
Static analysis, invariant testing and deployment monitoring are intended to verify that no unauthorized control path appears between the clearing domain and external lender / escrow infrastructure.
Osnias Clearing aims for maximum transparency where transparency improves auditability: public register state, published contract rules, verifiable clearing records and observable protocol outcomes.
Public trust in Osnias Clearing is intended to rest on verifiable contracts, transparent registers, explicit rules and auditable outcomes — not on publication of sensitive security infrastructure.
Osnias Oracles support mint / burn processing, register integrity and clearing snapshots.
Observe approved smart contracts, verify state and exchange authenticated requests.
Retain exclusive control over collateral, escrow contracts and their own financial operations.