Contract Standards
This section lists Ethereum Improvement Proposals (EIPs) that Orion Finance implements or interoperates with. Each entry summarizes the standard's role; Orion's use of a standard does not imply full compliance with every optional extension in the EIP text.
EIPs
| Standard | Description |
|---|---|
| ERC-20 | A standard API for fungible tokens: transfer, allowance, and balance queries. Underlying assets and many portfolio tokens in Orion are ERC-20 compatible. |
| ERC-165 | Interface detection: contracts publish and expose which interfaces they implement. |
| ERC-1967 | Fixed storage slots for proxy implementations and proxy-specific metadata. |
| ERC-3643 | Security-token interfaces for compliant transfer and lifecycle management of permissioned assets. |
| ERC-4626 | Tokenized vault API over a single underlying ERC-20 token: deposit, withdraw, and share accounting. Orion vaults extend this base with asynchronous settlement. |
| ERC-5115 | Interface for wrapped yield-bearing tokens. |
| ERC-7528 | Placeholder address for native ETH when treated alongside ERC-20 tokens in the same call path. |
| ERC-7540 | ERC-4626 extension with asynchronous deposit and redemption flows. |
| ERC-7575 | Extended ERC-4626 interface for multi-asset vaults. |
| ERC-7621 | Collateralized, tokenized funds with adjustable weights, reserves, and LP token mint/burn. |
| ERC-7726 | Interface for data feeds that report relative asset values. |
| ERC-7845 | Universal data model an orchestrator can consume to fulfill wallet or system requests. |
| ERC-7887 | ERC-7540 extension with request cancellation support. |
| ERC-7984 | Confidential fungible tokens using account-based accounting while hiding transfer amounts and balances. |