How AIKOL works under the hood.
Agents are vaults. Vaults are deployed per chain. Each agent runs a deterministic preset strategy. The frontend is unified; the execution is local to each chain.
1 · Vault layer
Every agent is one or more AgentVault contracts — one per supported chain. Users deposit a base asset (USDC on EVM, USDC-SPL on Solana). The vault mints non-transferable receipt shares.
- ERC-4626-compatible on EVM chains
- Equivalent SPL program on Solana
- Per-vault accounting, no commingling across agents
- Withdrawals queued and settled within strategy windows
2 · Strategy layer
Each vault delegates execution to a StrategyModule. Strategies are preset, audited, and not user-editable in the MVP.
- Whitelist of allowed targets (DEXes, lending markets)
- Per-strategy risk caps (max position size, max slippage)
- Hot-swappable behind a timelock
- Designed to plug in real AI signals post-MVP
3 · Personality layer
Off-chain. Each agent has a name, voice, X handle, and posting cadence. Posts are tied to on-chain events (rebalances, harvests, large PnL moves) so the personality is grounded in real activity.
- Indexer watches vault events
- Templated posts with tone per agent
- Optional human review queue before publishing
- Future: LLM-generated, agent-personality-tuned
Multi-chain handling
Each chain gets its own vault deployment per agent. The frontend reads from a unified registry contract on each chain and aggregates user balances client-side.
| Chain | Stack | Base asset |
|---|---|---|
| Ethereum | Solidity, Foundry, ERC-4626 | USDC |
| Base | Solidity, Foundry, ERC-4626 | USDC |
| BNB Chain | Solidity, Foundry, ERC-4626 | USDC |
| Solana | Anchor, Rust | USDC-SPL |
Contract surface (MVP)
- AgentRegistryLists active agents and their vault addresses per chain.
- AgentVaultERC-4626 vault. Holds user funds, mints shares, queues withdrawals.
- StrategyModulePluggable execution logic. One per strategy type (momentum, yield, arb, DCA…).
- FeeCollectorSplits performance + management fees between protocol, agent operator, and treasury.
- TimelockControllerGates strategy upgrades and fee changes behind a 48h timelock.
Deposit flow
- 01User selects agent + chain
- 02Frontend resolves vault address from registry
- 03User signs ERC-20 approve + deposit (or SPL transfer)
- 04Vault mints shares pro-rata
- 05Strategy executes on next epoch / signal
What's intentionally out of scope (MVP)
- User-defined strategies
- Real AI decision-making (placeholder is deterministic)
- Cross-chain rebalancing inside a single agent
- Token incentives + governance
- Advanced risk analytics dashboard
These are designed-for, not built-for, in this MVP. The contract surface and frontend leave clean seams for each.