How It Works
ARKONIX uses a signed-intent architecture with a hub-and-spoke model for on-chain fund accounting.
Architecture
┌────────────────────────────────┐
│ Depositors │
│ (deposit USDC, earn yield) │
└──────────────┬─────────────────┘
▼
┌────────────────────────────────┐
│ ERC-7540 Vaults │
│ (async deposit/redeem) │
└──────────────┬─────────────────┘
▼
┌────────────────────────────────┐
│ Hub (Fund Accounting) │
│ ┌──────────┐ ┌─────────────┐ │
│ │PoolManager│ │ShareClasses │ │
│ └──────────┘ └─────────────┘ │
└──────────────┬─────────────────┘
▼
┌────────────────────────────────┐
│ Strategy Modules │
│ ArkForge │ ArkBase │ ArkLend │
│ ArkMarket │
└──────────────┬─────────────────┘
▼
┌────────────────────────────────┐
│ Multi-Chain Settlement │
│ Ethereum │ Arbitrum │ Base │
│ BNB Chain │ + more │
│ (via LayerZero) │
└────────────────────────────────┘
Execution flow
- Deposit — Users deposit assets (e.g. USDC) into an ERC-7540 vault
- Accounting — The hub tracks shares, NAV, and allocations per pool
- Strategy execution — The engine allocates capital to strategy modules based on market conditions
- Rebalancing — Portfolios rebalance every 5 minutes using signed intents
- Settlement — Cross-chain settlement via LayerZero messaging
- Redemption — Users request redemption; assets are returned after the next epoch
Vault types
Sync deposit, async redeem
Deposits mint shares immediately. Redemptions go through a request-claim flow — you request, wait for the next epoch, then claim your assets.
Fully async
Both deposits and redemptions use the request-claim pattern. This allows the vault operator to manage liquidity more precisely.
Key characteristics
| Property | Value |
|---|---|
| Rebalance cycle | 5 minutes |
| Fund accounting | On-chain, hub-and-spoke |
| Vault standard | ERC-7540 (async ERC-4626) |
| Cross-chain | LayerZero |
| Custody | Non-custodial |
| Settlement | Signed-intent |