OSNIAS CLEARING
USD Clearing Register · Version 2.0 · Sei Testnet Public Technical Reference

ORUSD

A token designed for direct account-to-account clearing

ORUSD is a USD-denominated clearing register token designed for direct P2P circulation between EOA accounts on Sei. Version 2.0 combines controlled minting and burning, traceable oracle requests, non-replayable external proofs and final settlement under manager authority. The public reference deployment is verified on Sei Testnet.

Local Technical Documentation · PDF ↗ Zenodo DOI · Permanent Archive ↗
02 · ORUSD on Sei Testnet
ORUSD Version 2.0 has a public reference deployment on Sei Testnet for development, integration testing, wallet validation and pre-audit review. The deployed source is publicly inspectable and has been verified on SeiScan as an Exact Match.

Cosmos chain ID: atlantic-2
EVM Chain ID: 1328 (0x530)
Native gas asset: SEI
RPC: https://evm-rpc-testnet.sei-apis.com
Contract: OsniasClearing_Orusd
Contract address: 0x0c3a19455b898913A1DaD93d724c24062293dB5F
Creation transaction: 0xce15b298a4f1b0474e9c704996fd6d08c8d939d09def0eba8205998112c1ff15

View verified ORUSD contract on SeiScan → View creation transaction →
03 · Technical Role

A clearing register, not a market token

ORUSD is designed for one specific function: representing and transferring a USD-denominated clearing unit between user accounts. The token contract intentionally avoids the ordinary integration surfaces used by market, lending and DeFi tokens.

Clearing

Direct transfer

The normal operational path is a direct transfer from one user-controlled EOA to another user-controlled EOA.

Controlled supply

Explicit mint / burn

Supply changes only through explicit mint or burn paths under manager control, either manually or following a valid oracle request.

Network locality

Sei-native reference

The public reference implementation is Sei-native and exposes no bridge, OFT, wrapping, cross-chain transfer or balance-migration mechanism.

Canonical-state principle. Sei Testnet is the current public technical reference. Any future Sei Mainnet production instance will be deployed independently with its own production address, privileged-role configuration and operational-security controls. Testnet balances and administrative actions create no Mainnet entitlement.
04 · P2P Circulation

Gross debited / net received model

For an ordinary user transfer, the sender is debited the stated gross amount. The protocol deducts 0.15% within that amount and credits it to the feeRecipient; the beneficiary receives the net balance.

1,000.000000 ORUSD

Gross amount requested by the sender.

1.500000 ORUSD

0.15% protocol fee credited to the feeRecipient.

998.500000 ORUSD

Net amount received by the beneficiary.

Transfer invariant. Sender debit = beneficiary credit + feeRecipient credit. The fee mechanism creates no additional ORUSD.

Permitted circulation

  • EOA → EOA.
  • Gross amount ≥ 0.501 ORUSD.
  • 0.15% protocol fee.
  • Restricted-recipient rules apply.

Disabled paths

  • Ordinary transfer to a smart contract rejected.
  • approve() disabled.
  • transferFrom() disabled.
  • Minting to a smart-contract recipient rejected by the reference implementation.
05 · Oracle & Settlement

The oracle attests. The manager settles.

An authorized oracle cannot directly create or destroy ORUSD. It submits a MINT or BURN request based on identifiable external evidence. The request becomes visible on-chain before any supply change.

1 · Attestation

An authorized oracle observes or validates an external event and creates an on-chain request.

2 · Pending

The request includes type, account, amount, external reference and timestamp. It remains executable for 24 hours.

3 · Settlement

Only the manager can execute or reject the request. An expired request can no longer be executed.

Oracle authority

Request only

The oracle can attest and request; it cannot settle or directly modify supply.

Anti-replay

Single-use proof

The same sourceChain / externalRef pair can be consumed only once. Rejection does not release the proof for reuse.

Finality

Terminal status

An executed or rejected request retains an identifiable final state in the on-chain audit history.

06 · Clearing / Custody Segregation

USDC by Circle recommended for external escrow

The ORUSD smart contract is a clearing register and does not receive or hold customer deposits. Where an external USD-denominated escrow or custody layer is used, USDC issued by Circle is the recommended collateral asset. Deposit, custody, lending and collateral-management functions remain within independent partner infrastructures.

Clearing layer

ORUSD

ORUSD records and settles USD-denominated clearing units. It does not hold customer USDC collateral.

External collateral layer

USDC by Circle

USDC issued by Circle is recommended for external USD-denominated escrow or custody arrangements.

Structural separation

Distinct authorities

Custody of USDC confers no ORUSD mint, burn, oracle or manager authority.

Strict clearing / custody segregation. ORUSD performs clearing; external escrow or custody partners perform deposit and collateral functions. A collateral event may produce a clearing instruction through the oracle, but it does not transfer custody of USDC to the ORUSD contract.
07 · Technical Specification

ORUSD token specification

Open ORUSD Technical Documentation · PDF ↗
Role Restricted USD-denominated clearing register token.
Contract name OsniasClearing_Orusd.
Symbol ORUSD.
Solidity ^0.8.22; verified with v0.8.22+commit.4fc1097e.
Base standard OpenZeppelin ERC-20 with Ownable2Step administration.
Decimals 6.
Minimum P2P transfer 0.501000 ORUSD gross.
Protocol fee 15 basis points = 0.15%, deducted from the transferred amount.
Circulation Direct EOA → EOA transfer, subject to recipient and amount rules.
approve / transferFrom Disabled in the reference implementation.
Mint / burn Explicit manager-controlled paths; the oracle cannot mint or burn directly.
Oracle request MINT or BURN request, 24-hour validity, NONE / PENDING / EXECUTED / REJECTED lifecycle.
Anti-replay A sourceChain + externalRef proof pair can be consumed only once.
Recommended external escrow collateral USDC issued by Circle, managed outside ORUSD by independent partners.
Public reference network Sei Testnet · atlantic-2 · EVM Chain ID 1328 (0x530) · native gas asset SEI.
Verified contract 0x0c3a19455b898913A1DaD93d724c24062293dB5F
Creation transaction 0xce15b298a4f1b0474e9c704996fd6d08c8d939d09def0eba8205998112c1ff15
Compiler / optimizer v0.8.22+commit.4fc1097e · optimizer enabled · 200 runs · EVM target Paris.
Explorer verification SeiScan · Source Code Verified — Exact Match.
Intended production Separate Sei Mainnet deployment, with no bridge, OFT, wrapping or balance migration.
08 · Security

Explicit trust boundaries

Supply

No hidden path

Supply creation and destruction remain limited to explicitly defined manager-authorized functions.

Oracle

Separation of powers

Compromise of an oracle alone is insufficient to create or destroy ORUSD.

Proofs

Anti-replay

The same external proof cannot produce a second ORUSD request.

P2P accounting

Conservation

An ordinary transfer redistributes existing ORUSD between the beneficiary and feeRecipient without fee-induced inflation.

Collateral

Asset segregation

Compromise of the ORUSD register does not itself provide access to USDC collateral held by an external partner.

Production

Privileged-key security

Future Mainnet privileged roles must use the separately published production security architecture.

09 · Transparency

The code and documentation are public

The Solidity contract, ABI, flattened source and Version 2.0 technical white paper are directly accessible in the public /orusd/ repository directory.

Permanent technical archive — Zenodo. ORUSD Version 2.0 is archived under DOI 10.5281/zenodo.22200260 . The archive contains the Solidity source code, ABI, flattened contract and ORUSD Technical White Paper & Audit Reference.
Zenodo — ORUSD Technical Archive Record 22200260 · DOI 10.5281/zenodo.22200260
DOI ↗
/orusd/orusd-sei-testnet.sol Sei Testnet Solidity source
SOURCE ↗
/orusd/orusd-sei-testnet.abi Public ORUSD contract ABI
ABI ↗
/orusd/orusd-sei-testnet-flat.sol Flattened Sei Testnet source for verification and technical review
FLAT ↗
/orusd/ORUSD_Technical_White_Paper.pdf ORUSD Technical White Paper & Audit Reference — Version 2.0
PDF ↗
Sei Testnet — verified ORUSD contract 0x0c3a19455b898913A1DaD93d724c24062293dB5F
SEISCAN ↗
Reference deployment — Sei Testnet. ORUSD Version 2.0 reference address: 0x0c3a19455b898913A1DaD93d724c24062293dB5F . SeiScan reports the deployed source as Exact Match.
Document scope. The ORUSD Technical White Paper describes the token architecture, deployment model, smart-contract behavior, operational roles, security boundaries and audit invariants. Legal, regulatory, contractual and compliance matters are addressed separately in dedicated Osnias Clearing regulatory documentation.
Publication metadata.
Version 2.0 · 31 August 2026
Author / Rédacteur: Denis Bouzon · ORCID 0009-0007-8894-8902
Zenodo record: 22200260
DOI: 10.5281/zenodo.22200260
Copyright © 2026 Denis Bouzon — Osnias Clearing. All rights reserved.