Protocol architecture
The web app, private operator, data services, and durable transaction jobs.
Execution layers
The web app provides Privy login, launch and trade forms, market views, and server API routes. Sensitive credentials stay on the server. The private Node operator prepares and checks transactions using Helius RPC.
The launch instruction engine is pinned to Rust pump-rust-client 0.1.9 with compatibility extensions. Current Pump account decoding and checks also use the official TypeScript SDK.
| Component | Responsibility |
|---|---|
| Privy | Account authentication and wallet connection |
| Helius | Solana state, simulation, and configured broadcasting |
| Rust Pump engine | Launch instruction construction |
| D1 database | Registry, receipts, jobs, budgets, and round records |
| OpenSea / Collector Crypt | Card inventory and supported purchase actions |
| Relay | Constrained fee-currency conversion |
| drand | Verifiable round randomness |
Automatic processing
The worker schedules fee collection, buybacks, conversion, purchases, and distributions as separate stages. Each stage requires its own configuration and execution gate. Enabling launch submission does not silently enable treasury spending.
Work is leased and recorded in durable jobs. Prepared bytes, signed transactions, signatures, reservations, and reconciliation states survive process restarts. This is how retries can avoid issuing a second payment after an ambiguous network response.
Wallet and signing boundaries
Users sign their launch and trade transactions with their selected wallet. Automatic treasury actions use configured operator wallets and constrained preparation policies. Keys do not belong in browser bundles or public environment variables.
The current architecture includes an operator-controlled treasury and application-level accounting. It should not be described as a fully trustless autonomous on-chain vault.