classic-search hygiene JSON-LD for OpenForage agents and software
OPENFORAGE
Mainnet · Coming Soon

Smart Contract Architecture

High-level component diagram, contract purposes, and key depositor-facing interactions.

Contract Overview

OpenForage deploys 10 core contracts on Arbitrum. Each serves a specific purpose in the protocol.

Dollar Layer

Contract Purpose
RISKUSD ERC-20 protocol dollar minted 1:1 against deposited USDC and burned on redemption.
RISKUSDVault Deposit and redemption entry point; manages RISKUSD backing as on-vault USDC plus conservatively valued deployed/custodian capital.

Yield Layer

Contract Purpose
atRISKUSD (4 tier instances per vault) Yield-bearing vault positions. Exchange rate reflects cumulative net performance per vault.
StakingQueue Manages tier transitions, lock-up expiry, auto-renewal, and reversion to Tier 0.

Treasury Layer

Contract Purpose
USDCTreasury Automated USDC revenue allocation hub. Splits incoming PnL per governance ratios into depositor yield, the agent USDC funding earmark, and the flat 30% protocol share (15% Foundation + 15% protocol-retained reserve).
FORAGETreasury Consolidated FORAGE distribution treasury. Holds and distributes FORAGE for agent rewards, depositor airdrops, and strategic partnership allocations.

Governance Layer

Contract Purpose
ForageToken FORAGE ERC-20 governance token. Fixed supply of 100M, no minting.
ForageGovernor Proposal, voting, and execution system for protocol governance.
TimelockController Enforces 8-day minimum delay on all governance actions.
DelegatingVestingWallet Team FORAGE vesting (4-year linear, 1-year cliff). Supports governance delegation during vesting.

Key Depositor Interactions

The primary depositor flow touches three contracts:

  1. RISKUSD — Deposit USDC, receive RISKUSD. Redeem RISKUSD for USDC.
  2. atRISKUSD — Stake RISKUSD, receive yield-bearing shares. Request withdrawal.
  3. StakingQueue — Select tier, manage auto-renewal, process lock-up expiry.

Security Properties

  • All governance actions pass through the TimelockController with an 8-day delay
  • Guardians can only pause and unpause contracts (no fund movement or parameter changes)
  • atRISKUSD withdrawal execution cannot be blocked, even during protocol pause
  • Revenue allocation is atomic and non-discretionary once PnL is deposited

See Smart Contract Security for security review status and trust assumptions.