The entire architecture is designed to keep you in full control. At no stage does ViperX gain custody of your funds, the ability to withdraw your capital, or the power to override your wallet’s authority over the vault.
The Five-Stage Pipeline
1
On-Chain Registry
You deploy a trading vault and sign a single transaction that calls
register_agent on the ViperX registry contract (Base Sepolia or Solana Devnet). This writes your agent identity, display name, and strategy metadata URI permanently to the blockchain.Your vault address is recorded at this point — along with the cryptographic proof that your wallet owns it. You keep full custody throughout; the registry only stores your identity and strategy pointer, not your funds.What gets written on-chain:- Agent ID and display name
- Strategy metadata URI (pointing to your off-chain config)
- Vault address and ownership key
2
Narrow Delegation
After registration, you sign a second transaction calling
delegate_authority. This grants the ViperX off-chain runner the right to submit trade transactions and invoke circuit breakers on your behalf — nothing else.Withdrawal permissions are never part of the delegation. The runtime cannot transfer tokens, drain your vault, or act outside the bounds of your configured strategy profile. If it tries, authority_pause() fires automatically.What the delegation grants:- Trade submission authority (open and close positions via DEXes)
- Circuit-breaker invocation (
authority_pause())
- Withdrawal rights
- Token transfer approvals
- Principal movement of any kind
3
Autonomous Trading
With delegation active, the ViperX execution runtime polls your strategy on a 15-second tick cycle. At each tick, it fetches your strategy config from the off-chain URI, evaluates the current market state, and — if the strategy signals a trade — submits a signed transaction to the appropriate decentralised exchange.Each executed fill is recorded on-chain via
record_trade, creating an auditable trace of every position your agent opens and closes. The runtime operates continuously without manual input, stopping only if authority_pause() fires or your vault balance drops below the minimum trade threshold.Runtime behaviour per tick:- Fetches strategy config from your strategy URI
- Evaluates market conditions against strategy parameters
- Submits trade transactions to DEXes if signal conditions are met
- Records fill signatures on-chain via
record_trade
4
Indexer Verification
After each fill is recorded on-chain, the ViperX indexer independently verifies it. The indexer syncs blocks from Base Sepolia and Solana Devnet, then cross-references each self-reported fill against the actual settled position changes visible in on-chain account state.A fill only counts toward your verified total if it passes all three anti-gaming heuristics:
Fills that fail any check are excluded from your verified count and flagged in your agent’s tuning log. An agent cannot game the system by looping
record_trade calls without placing real orders — the indexer confirms everything against independent on-chain position state.5
Leaderboard Ranking
Once the indexer has confirmed 50 independently verified fills for your agent, it becomes eligible to appear on the public leaderboard. Your rank is calculated from a risk-adjusted Sharpe-like ratio derived entirely from your verified on-chain trade history and vault balance changes — not from self-reported PnL figures.The ranking metric penalises maximum drawdown, so a lucky high-leverage bet cannot outrank consistent risk-managed performance. All inputs to the ranking calculation come from verified on-chain data that anyone can independently audit.Ranking inputs (all on-chain verified):
- Realised PnL from verified fills
- Vault balance changes at each block
- Maximum drawdown over the agent’s full history
- Volatility-adjusted Sharpe ratio calculation
Strategy URI and Off-Chain Metadata
Your strategy configuration — parameters like tick window, RSI bounds, trade size, and grid spacing — lives off-chain at the URI you register. This can be an IPFS content hash or any publicly accessible URL. The execution runtime fetches this config at each tick to know how to trade.Keeping strategy config off-chain gives you flexibility: you can update parameters without re-deploying your agent on-chain. The on-chain registry stores only the pointer (the URI), not the full config. The runtime always fetches the latest version of your config at each polling tick.
Full Architecture Diagram
The diagram below shows how every component connects: from your wallet through the registry, runtime, DEXes, indexer, and out to the leaderboard.Why This Design
Traditional copy-trading and performance-tracking platforms rely on centralised databases that managers can modify, selectively delete, or spoof with opposing accounts. ViperX eliminates those trust assumptions by anchoring every meaningful event — agent registration, trade fill, authority delegation, circuit-breaker invocation — to a public blockchain.Custody stays with you
Separating execution authority from withdrawal rights means the runtime can trade autonomously on your behalf without ever touching your principal. You remain the only party who can move funds.
Rankings are manipulation-resistant
Because the indexer independently verifies fills against settled on-chain state, no agent can inflate its record through fake trades, database edits, or looped contract calls.
Strategy logic is portable
Storing strategy config off-chain at a URI you control means you can iterate on your parameters without on-chain transactions. The contract stores ownership and history; you own the intelligence.
Failure is safe by default
If ViperX infrastructure goes offline,
authority_pause() fires and execution halts. Your vault balance is unaffected. You can withdraw at any time regardless of system state.