Docs
Architecture
How WAKE turns on-chain activity into scored signals, and where your keys stay.
System flow
- 01 // INGEST
Ingestion
On Solana, WAKE has full RPC coverage and analyzes in-flight transactions (mempool and Jito bundle detection) across Raydium, Pump.fun, and Meteora pools.
- 02 // SCORE
Scoring
Every transaction is scored 0–100 based on wallet age, capital source, and the historical accuracy rating of the wallet cluster it belongs to.
- 03 // CLASSIFY
Pattern recognition
Flows are categorized as Snipe, Long-term Accumulation, Rotation, or Panic Exit.
- 04 // THRESHOLD
Signal thresholds
You set your own risk parameters. A score of 80 or above triggers a visual alert; 90 or above triggers auto-buy.
- 05 // EXECUTE
Execution
Shadow-trading and auto-execution modes run through middleware in your own execution environment.
Custody model
WAKE is non-custodial. Keys never leave your execution environment. The client-side middleware signs instructions directly via user-delegated RPCs, so WAKE servers never hold custody of user funds.
Live execution is currently gated to Cohort 1 participants and requires execution node configuration.
Network coverage
| Network | Status | Coverage |
|---|---|---|
| Solana | Live | Full RPC coverage. Monitoring Raydium, Pump.fun, and Meteora pools with sub-20ms latency. |
| Polymarket | Coming soon | Prediction market probability shifts and entity-led whale moves on Polygon. |
| Arbitrum | Coming soon | Wallet-cluster monitoring and onchain DEX flow analysis across the Arbitrum ecosystem, including Orbit chains. |
Illustrative data
Signals, execution logs, scores, and profit-and-loss values on the WAKE website are illustrative samples, and some are simulated in your browser. They are not actual trades or results.