尚未偵測到更新。GitHub 發布版本後會顯示在這裡。
個人 GitHub 帳號下公開儲存庫的擁有者可以登入並驗證所有權,自行管理介紹,無需管理員核准。
登入並產生驗證檔案,在 30 分鐘內將其提交至此儲存庫的預設分支。其他分支或分叉儲存庫中的檔案無效。然後在下方檢查檔案,即可無需管理員核准直接管理專案。請保留檔案以維持管理權限。
如需登入,將前往登入頁面。登入後請回到此處,再次點擊所選的驗證按鈕。
在專案資料夾中執行 /nomorevibe verify,即可驗證所有權並自行管理介紹。
一分鐘完成驗證正在載入完整 README。 以下為已儲存的摘錄。
Autonomous Perpetual Futures Trading Platform on Solana
QuantumVault enables users to deploy and manage autonomous perpetual futures trading bots on Solana. The platform automates trade execution via TradingView webhooks and AI agent signals, provides real-time position tracking, and integrates with Phantom Wallet for seamless Solana DeFi access.
The platform routes trades through a protocol-agnostic adapter layer, with Pacifica.fi as the primary execution venue and Drift Protocol registered as a backup adapter. New venues can be added without touching the core trading engine.檢視完整 README ↗Autonomous Perpetual Futures Trading Platform on Solana
Live at myquantumvault.com
QuantumVault enables users to deploy and manage autonomous perpetual futures trading bots on Solana. The platform automates trade execution via TradingView webhooks and AI agent signals, provides real-time position tracking, and integrates with Phantom Wallet for seamless Solana DeFi access.
The platform routes trades through a protocol-agnostic adapter layer, with Pacifica.fi as the primary execution venue and Drift Protocol registered as a backup adapter. New venues can be added without touching the core trading engine.
This is not a demo or proof of concept — QuantumVault is live on Solana mainnet processing real trades with real capital.
ProtocolAdapter interface. Adding a new DEX (Zeta, Hyperliquid, etc.) requires implementing one interface and registering it; the core trading engine, bot logic, and UI never change. Built in response to the Drift Protocol exploit to ensure the platform is never locked to a single venue again.QuantumVault is built around a ports-and-adapters (hexagonal) pattern. The core never imports an exchange directly — it always goes through the registry.
┌─────────────────────────────────────────────────────────────┐
│ QuantumVault Core │
│ routes.ts · position-service · trade-retry-service │
│ reconciliation-service · pnl-snapshot-job · QuantumLab │
└───────────────────────┬─────────────────────────────────────┘
│ ProtocolAdapter interface
│ (server/protocol/adapter.ts)
┌─────────┴──────────┐
│ AdapterRegistry │
└────┬──────────┬────┘
│ │
┌─────────┴──┐ ┌────┴────────┐
│ Pacifica │ │ Drift │
│ (primary) │ │ (backup) │
└────────────┘ └─────────────┘
Key components in server/protocol/:
adapter.ts — ProtocolAdapter and UserTransactionBuilder interfaces every exchange implementsadapter-registry.ts — Per-bot adapter resolution; supports global default and per-bot overridessymbol-registry.ts — Bidirectional symbol mapping between QuantumVault's internal naming (SOL-PERP) and each exchange's formatadapter-health.ts — Generic health tracker for any adapterpacifica/ — Pacifica adapter, signer, WebSocket manager, transaction builder, typesdrift/ — Drift adapter wrapping the existing Drift service behind the same interfaceWhat an adapter owns:
| Capability | Adapter Responsibility |
|---|---|
| Authentication | Sign requests in the exchange's required format (Pacifica: 8-step canonical JSON + Ed25519) |
| Market data | getMarkets, getPrice, getOrderbook, getFundingRate |
| Account state | getPositions, getBalances, getAccountInfo |
| Order execution | placeMarketOrder, placeLimitOrder, cancelOrder, closePosition |
| Subaccounts | Create / list / transfer between (model varies: keypair-based on Pacifica, numeric ID on Drift) |
| Capital flows | On-chain deposit (via UserTransactionBuilder), REST-based withdraw |
The core never asks "what exchange is this?" — it asks the registry, gets an adapter, and calls the interface. This is what made the post-Drift-hack pivot possible without rewriting the trading engine.
See docs/ADDING_EXCHANGE_ADAPTERS.md for the full guide on implementing a new adapter, and docs/SMART_ROUTING.md for the planned automatic-routing layer.
| Feature | Solana Integration |
|---|---|
| Trade Execution | Pacifica.fi REST + WebSocket (primary); Drift Protocol via the adapter layer (backup). All exchange-side; Solana RPC not in the hot path. |
| On-Chain Capital | USDC deposits to Pacifica via Anchor CPI; user-signed deposit, agent-signed withdraw. Drift deposits via the SDK when that adapter is selected. |
| Position Management | Exchange WebSocket is the source of truth; database acts as cache with reconciliation against REST every 60 seconds. |
| Agent Wallets | Server-managed Solana wallets per user with AES-256-GCM encrypted private keys for autonomous execution. |
| Subaccount Isolation | Each bot operates on its own isolated subaccount — keypair-based on Pacifica (encrypted per-bot private key in DB), numeric ID on Drift. |
| Token Operations | Automated USDC deposits, withdrawals, and profit distribution via the SPL Token program. |
| Profit Sharing | Immediate on-chain USDC transfers to signal creators when subscriber trades close profitably. |
The AI agents autonomously handled:
ProtocolAdapter interface so it could remain registered as a backupprovisionFundedSubaccount flow)The human operator provided strategic direction, product vision, trading domain expertise, and orchestrated the multi-agent workflow. Neither could have built this alone.
QuantumVault serves as execution infrastructure for autonomous AI agents to trade Solana perpetual futures:
Webhook API — Any agent sends a simple POST request to open, close, or flip positions:
# Open a long position
curl -X POST https://myquantumvault.com/api/webhook/{BOT_ID} \
-H "Content-Type: application/json" \
-d '{"botId": "{BOT_ID}", "action": "buy", "contracts": "10", "position_size": "100"}'
# Close position
curl -X POST https://myquantumvault.com/api/webhook/{BOT_ID} \
-H "Content-Type: application/json" \
-d '{"botId": "{BOT_ID}", "action": "sell", "contracts": "0", "position_size": "0"}'
What the agent gets: Routed execution through whichever adapter the bot is bound to (Pacifica by default), automatic retry with exponential backoff, RPC failover (Helius + Triton) for the on-chain deposit/withdraw path, margin management, auto top-up between agent and bot subaccounts, and position tracking — without needing to know anything about the underlying exchange.
The self-sustaining loop: An AI agent creates a signal bot, publishes it to the marketplace, and begins trading. As its track record grows, human users and other agents subscribe. When subscriber trades close profitably, the creator agent earns a percentage via immediate on-chain USDC transfer. Those earnings can fund the agent's own compute and trading capital — creating a fully autonomous economic actor on Solana that sustains itself through trading performance.
server/protocol/ — ProtocolAdapter interface, AdapterRegistry, SymbolRegistry, per-exchange adapter packages@coral-xyz/anchor for Pacifica deposits, tweetnacl / @noble/ed25519 for Pacifica signingDATABASE_URL=postgresql://...
SESSION_SECRET=your-session-secret
HELIUS_API_KEY=your-helius-key
SOLANA_RPC_URL=https://mainnet.helius-rpc.com/?api-key=...
SOLANA_NETWORK=mainnet-beta
AGENT_ENCRYPTION_KEY=your-64-char-hex-key
SERVER_EXECUTION_KEY=your-64-char-hex-key
# Install dependencies
npm install
# Push database schema
npm run db:push
# Start development server
npm run dev
The application will be available at http://localhost:5000.
The platform is deployed and running in production at myquantumvault.com.
MIT