Answers are grounded in this paper and cite their sources.
Technical report demonstrates a restricted token framework for account-to-account clearing, highlighting the separation of oracle attestation from manager settlement.
ORUSD is a USD-denominated clearing token designed for direct account-to-account settlement within the Osnias Clearing architecture. It is implemented as a restricted ERC-20 token with 6 decimals and a deliberately narrow functional scope.Its primary purpose is clearing and settlement, not market trading or speculative use.Ordinary transfers are designed for direct EOA-to-EOA circulation.The reference implementation disables approve() and transferFrom() and rejects ordinary transfers to smart contracts. Minting and burning are explicit operations controlled by the manager.Authorized oracles may submit MINT or BURN requests but cannot directly alter the token supply.Oracle requests remain valid for 24 hours and must be executed or rejected by the manager.External clearing references are protected against replay, preventing the same proof from being used more than once. The token therefore separates attestation authority from final settlement authority.USDC is the contemplated collateral asset, but collateral is not held or managed by the ORUSD token contract itself.Collateral custody, lending operations and risk management remain within independent partner infrastructures.Ethereum Sepolia serves as the public reference and testing environment for the current implementation.The intended production deployment is on Sei EVM, with a distinct canonical production state. The architecture does not rely on bridges, OFT, wrapping or cross-chain balance migration for ORUSD.This Zenodo archive contains the Solidity source code, ABI, flattened contract and the ORUSD technical white paper and audit reference.
No takes yet. Share an insight, caveat, or question.
Denis Bouzon (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: