Skip to content

Architecture at a Glance

ARKONIX follows a hub-and-spoke pattern at two levels: at the smart-contract layer (a hub coordinating per-chain spoke deployments) and at the service layer (a gateway routing to focused services).

                        ┌────────────────────────────────────┐
                        │        ARKONIX Platform (web)      │
                        │  Earn app · Partner portal · Site  │
                        └──────────────┬─────────────────────┘
                                       │ HTTPS · JWT / SIWE
                                       ▼
                        ┌────────────────────────────────────┐
                        │            API Gateway             │
                        └───────┬────────────────┬───────────┘
                                │                │
                 ┌──────────────▼───┐   ┌────────▼──────────────┐
                 │  Arkonix Backend │   │  Rebalancing Engine   │
                 │  (execution)     │   │  (strategy execution) │
                 └───────┬──────────┘   └────────┬──────────────┘
                         │      signals/indices  │
                         │   ┌───────────────────▼──┐
                         │   │      SignalForge     │  ← operated by
                         │   │  (Arkonix Capital    │    Arkonix Capital
                         │   │   Management)        │    Management
                         │   └──────────────────────┘
                         │ signed txs (KMS)
                         ▼
        ┌───────────────────────────────────────────────────┐
        │            ARKONIX Protocol (on-chain)            │
        │   ERC-4626 / ERC-7540 vaults · hub-and-spoke      │
        │   Ethereum · Arbitrum · Base · BSC · HyperEVM     │
        └───────────────────▲───────────────────────────────┘
                            │ direct wallet interaction
              ┌─────────────┴─────────────┐
              │  Depositors & Partner UIs  │
              │  (Vault SDK / wallets)    │
              └───────────────────────────┘

The layers

Frontend — arkonix-platform. A monorepo of Next.js applications: the public Earn app (vault listings, deposits, portfolio), the partner portal (share-class operations, queues, governance), and the marketing site. Details in Platform (Frontend).

Backend — arkonix-backend. The execution platform: a FastAPI service behind the API gateway. It serves the public read-only API, the authenticated app API, indexes on-chain events into a database, orchestrates epoch settlement, and executes strategy transactions signed through cloud HSMs. Details in Backend (Execution).

Signals — SignalForge. The signal- and index-generation service that produces the quantitative inputs certain strategies consume. SignalForge is owned and operated by Arkonix Capital Management (ACM), a separate entity from the platform. Details in SignalForge.

SDKs. Two distinct SDKs with different audiences:

  • arkonix-vault-sdk — public, partner-facing React/React Native SDK for vault deposit/redeem flows and financial data.
  • arkonix-defi-sdk — internal Python SDK the execution engine uses to interact with DeFi protocols (Aave, Hyperliquid, and others) across chains. Not for external consumption.

Protocol — on-chain vaults. ERC-4626 vaults extended with ERC-7540 asynchronous flows, deployed hub-and-spoke across chains (built on Centrifuge Protocol v3). Deposits, redemptions, share prices, and holdings are on-chain facts. Details in Protocol Layer.

Key data flows

  1. A deposit — the depositor's wallet calls the vault contract directly (via the Earn app or a partner UI built on the Vault SDK). The backend's indexer observes the on-chain event and updates TVL, share price, and position data that the public API serves.
  2. An epoch settlement — the operator processes queued deposit/redeem requests at NAV; depositors then claim their shares or assets.
  3. A rebalance — strategy logic (informed by SignalForge signals where applicable) produces target allocations; the execution layer simulates, signs (HSM), and submits the transactions on-chain.

For the depositor-eye view of these flows, see Deposits & Withdrawals. For the integrator-eye view, see the Vault SDK concepts.