Contract and On-chain data

Key Smart Contract Module Descriptions

• Bonding Contract: Implements the logic for users to purchase $OPEN at a discounted price, ensuring that token issuance adjusts dynamically based on treasury value and market premiums. Uses TWAP and IV pricing mechanisms, along with the debt ratio, to calculate the discount rate users can receive.

• Staking Contract: Manages users' $OPEN staking status and executes periodic Rebase distributions. Implements reward release, unlocking restrictions, and the $NEC acceleration mechanism.

• Treasury Contract: Accepts assets from users' bond purchases and securely holds the Protocol-Controlled Value (PCV). Works in conjunction with the minting contract to mint and burn $OPEN tokens.

• Rebase Engine Contract: Triggers dynamic Rebase every 12 hours, minting new tokens based on yield and system parameters. Introduces exponential growth logic and prevents excessive inflation.

• Governance Contract (DAO): Receives votes from $NEC holders and manages parameter changes, asset allocation, and roadmap decisions. Supports full governance processes, including proposal submission, voting, and execution.

On-chain Data and Cross-chain Design

To achieve multi-chain collaboration and transparent operations, OpenFi employs the following technical mechanisms:

• On-chain Data Accessibility: All core protocol data (staking, treasury balance, bond metrics) is stored on-chain and publicly accessible.

• Oracle System: Uses multi-node oracles to provide asset pricing and TWAP support.

• Cross-chain Bridge Design: OpenFi will deploy on multiple EVM chains in the future, utilizing cross-chain infrastructure such as LayerZero or Axelar to enable token and staking certificate interoperability.

This technical architecture ensures that OpenFi can maintain security, stability, and high performance while supporting full-chain operations and asset integration, providing a solid technical foundation for future ecosystem expansion.