Contract Standards
This section lists the Ethereum Improvement Proposals (EIPs) which are relevant for Orion Finance, outlining compatibility and synergies with the broader Ethereum ecosystem.
EIPs
| Standard | Description |
|---|---|
| ERC-20 | This standard allows for the implementation of a standard API for tokens within smart contracts. This standard provides basic functionality to transfer tokens, as well as allow tokens to be approved so they can be spent by another onchain third party. |
| ERC-1967 | A consistent location where proxies store the address of the logic contract they delegate to, as well as other proxy-specific information. |
| ERC-3643 | An institutional grade security token contract that provides interfaces for the management and compliant transfer of security tokens. |
| ERC-4626 | The following standard allows for the implementation of a standard API for tokenized Vaults representing shares of a single underlying EIP-20 token. This standard is an extension on the EIP-20 token that provides basic functionality for depositing and withdrawing tokens and reading balances. |
| ERC-5115 | Interface for wrapped yield-bearing tokens. |
| ERC-7528 | An address placeholder for ETH when used in the same context as an ERC-20 token. |
| ERC-7540 | Extension of ERC-4626 with asynchronous deposit and redemption support. |
| ERC-7575 | Extended ERC-4626 Interface enabling Multi-Asset Vaults. |
| ERC-7621 | Collateralized, tokenized funds with adjustable weights and reserves and minting/burning of LP tokens. |
| ERC-7726 | Interface for data feeds providing the relative value of assets. |
| ERC-7845 | A universal data model that an Orchestrator can understand to help fulfill a request for a solution from a wallet or any other system. |
| ERC-7887 | Extension of ERC-7540 with cancelation support. |
| ERC-7984 | Confidential fungible tokens use an account-based accounting model while maintaining the confidentiality of transfer amounts and balances. |