Protocol
Architecture
How the app, the data layer, the engines and the onchain programs fit together.
Overview#
Pool data + RPC
Solana mainnet
Adapters
normalise every pool
Engines
score, risk, strategy, mandate
App + API
web, PWA, /api/v1
Programs
6 onchain programs
Reading is offchain and fast: the app pulls live data, normalises it and scores it on the server every 60 seconds. Anything that moves money is onchain: your wallet or your agent signs transactions to VYLO programs or to Solana pools, and the programs enforce every rule.
Components#
| Component | Responsibility |
|---|---|
| Protocol adapters | One adapter per pool family. Each reads pools and reports its capabilities. A failing source is reported, never replaced with invented data. |
| Opportunity engine | Pure functions: score components, total, risk class. |
| Strategy engine | Rule evaluation, mandate checks, score-weighted allocation, plain language compiler. |
| Solana package | Token analysis, wallet balances, live market prices, client instructions for every VYLO program. |
| Web app | Next.js app with server rendering, the public API and the installable PWA. |
| Programs | Fee Router, Pool Factory, Staking, Buyback Vault, Agent Vault, VYLO Lock on Solana mainnet. |
How the programs connect#
- The Pool Factory reads the Fee Router config to know where the protocol share goes, and refuses to collect while the router is paused.
- The Fee Router pays the buyback share to the Buyback Vault authority (CYLr...RBzt) and the staker share to the Staking pool (EhEB...hsnt).
- The Agent Vault can only move funds between the vault and pools (VYLO classic pools and bin pools, plus swaps whose output stays in the vault), never to a wallet.
- The Buyback Vault can only call the whitelisted swap router.
These program ids are compiled into the binaries, so no one can point a program at a different program after deployment.