Skip to content

Protocol Layer

The on-chain foundation of ARKONIX: tokenized vaults with asynchronous settlement, deployed hub-and-spoke across networks.

Contract-level reference

This page is the conceptual overview. For the full contract-by-contract documentation — security model, messaging, hub/spoke/vault contracts, and the Arkonix extensions — see the Smart Contracts section.

Standards

ERC-4626 — tokenized vaults. Every vault is an ERC-4626 vault: deposits mint share tokens, the contract exposes standard conversion functions (convertToAssets, convertToShares), and positions are plain ERC-20 balances any wallet or protocol can read.

ERC-7540 — asynchronous flows. ERC-7540 extends 4626 with requests: requestDeposit and requestRedeem queue intent, an epoch settles the queue at NAV, and users claim the result. Two vault configurations are deployed:

Type Deposit Redeem
ASYNC asynchronous (request → epoch → claim) asynchronous
SYNC_DEPOSIT_ASYNC_REDEEM synchronous ERC-4626 deposit() asynchronous

Mechanical details that integrators rely on (single request slot per user, requestId = 0, cancel flows, claim semantics) are documented in SDK Concepts.

Hub-and-spoke deployment

The contract system is built on Centrifuge Protocol v3:

  • A hub coordinates pool- and share-class-level state.
  • Spokes are per-chain deployments; a share class can expose vaults on several networks simultaneously, linked to the hub through cross-chain messaging adapters (Axelar, Chainlink CCIP, LayerZero, Wormhole are the supported adapter families).
  • Deployments use deterministic addressing (CREATE3), so contract addresses are stable and predictable across chains.
  • Share-price (NAV) updates are published on-chain per spoke and emitted as events — this is the series the public API's share-price history exposes, block numbers and transaction hashes included.

Domain model

Pool ──── owns ───▶ Share Class ──── deployed as ───▶ Vault (per chain)
                      │
                      ├─ NAV / share price (published on-chain)
                      ├─ fee configuration (management / performance)
                      └─ strategy & governance parameters
  • Pool — the partner-level container.
  • Share class — the unit of strategy, fees, and NAV; identified by a hex share-class id.
  • Vault — a chain-specific ERC-7540 entry point to a share class, identified by its contract address.

Networks

Ethereum Mainnet, Arbitrum One (primary execution network), Base, BNB Smart Chain, and HyperEVM, with additional networks (e.g. Optimism, Polygon, Plume) in various stages of rollout. GET /discovery/chains on the Discovery API is the live source of truth.

Governance & controls

  • Vault parameters (fees, caps) can be governed by multi-signature contracts (Gnosis Safe) with per-vault thresholds.
  • Emergency controls — pause and circuit-breaker mechanisms exist at both the API and contract level, exercisable by the operator or multisig.
  • Transferability — share-token transferability is configurable per spoke (e.g. whitelist-restricted share classes for permissioned distribution).

Verifiability

Everything a depositor's position depends on is on-chain: deposits and redemptions (request and settlement events), share-price updates, and vault holdings. The public API exists for convenience — every series it serves can be recomputed from chain data.