Osnias-ID

Why Osnias-ID?

Osnias-ID was designed to provide Osnias Clearing with a compact internal reference usable across different escrow-capable blockchain chains, independently of each chain's native addressing system, account model or execution environment.

Deterministic 19-digit format · Release 2.0

Release 2.0 binds a clearing account to its network, authorized server, monetary unit and clearing cycle directly inside the identifier. Currency and cycle are therefore protocol-level identity attributes rather than mutable off-chain metadata.

The complete identifier contains 19 decimal digits. Its maximum decimal space remains below 10¹⁹, which fits inside an unsigned 64-bit integer. The human-readable decimal representation can therefore be encoded on-chain as a single uint64 / 8-byte value and rendered back into its structured decimal form by the interface.

One Osnias-ID across different escrow networks

Osnias-ID provides the common clearing reference between the native escrow account on its local network or rail and the corresponding clearing account on Sei. Each escrow network keeps its own native account identifier — for example an EVM 0x address, a Solana address, a TRON address or a banking account identifier — while the Osnias-ID is the shared clearing identifier used by the two registries.

The escrow-network registry immutably matches the local escrow account, using the native identifier of that network, with its Osnias-ID. The Sei clearing registry matches the same Osnias-ID with the corresponding local 0x clearing address on Sei.

Legal Entity → Clearing Account → Technical Address

An Osnias-ID is not a company identifier. A company or institution may hold several Osnias-ID clearing accounts, all linked by the Osnias Registry to the same legal entity.

No valid Osnias-ID, no clearing admission

The Osnias Registry is the authoritative resolution layer between a clearing account, its identified participant and its currently authorized operational addresses. Release 2.0 adds two admission invariants before a clearing request can be accepted: the OID monetary code must match the escrow and clearing rail, and the OID cycle must match the target clearing room. Checksum validity alone is never sufficient: the identifier must also resolve to an active and eligible registry record.

Pre-allocated and reserved network namespace

KK is the two-digit Osnias network or rail namespace. KK=00 is permanently reserved as a null/unassigned value. Allocated public-network codes identify escrow-capable blockchain environments, while dedicated ranges are reserved for future public networks, institutional rails and Osnias internal infrastructure. A reserved code is a namespace allocation and does not imply integration, validation, participation or endorsement.

Osnias-ID correspondence between KK network namespaces and native escrow-account identifiers across public blockchain networks and institutional banking rails.

Published, citable and versioned

Osnias-ID Release 2.0, dated 11 September 2026, is publicly archived and citable through both HAL and Zenodo. The repository-hosted HAL PDF below is the public Release 2.0 paper corresponding to the current specification.

What Osnias-ID is — and is not

Osnias-ID is an internal Osnias Clearing identifier and registry reference for interchain clearing. It is not a bank account number, legal-entity identifier, wallet address, regulatory authorization number, security, token or credential of legal status. KK and NNN are allocated by Osnias Clearing; MMM carries the ISO 4217 numeric monetary code; WW records the clearing-cycle duration in weeks; SSSSSSS is allocated by the authorized server inside that server/currency/cycle namespace; and XX is calculated under the Osnias-defined checksum rule. References to ISO 4217, ISO 20022, LEI, UID/CHE, FINMA or other external frameworks are interoperability references only and do not imply certification, regulatory status or endorsement.