For Traders · Solana validator-side runtime
See first.
Trade first.
Run your strategy inside a Solana validator. Read decoded state in ~35ms, submit to the next leader before the public network can react. No co-location. No middleware. No validator ownership.
What you build
Bot meets optimizer.
To trade on Catscope you write two pieces of code that work together. Neither works without the other.
Part 1
The bot
Your trading strategy, compiled to WASM and deployed inside the validator. Subscribes to account state, runs your logic, submits transactions. You write it; you own it.
noncepad/catscope-rust-bot →
Part 2
The optimizer
The control plane for your bot. Deploys bots to validators, pushes configuration down (thresholds, rate limits, target accounts), and receives signals back (PnL, fill rates, price data). You define what the messages carry and when the optimizer acts on them.
noncepad/optimizer →
Three streams · one runtime
The fastest path to state, priority, and execution.
Catscope is a marketplace inside Solana validators. Three independent products — buy any one, or all three. No subscriptions, no co-location, no relationships required.
Read
Decoded state. Streamed.
Subscribe to a live graph of decoded Solana accounts — nodes, edges, every dependency — straight from a validator's shared memory. Real-time pools, order books, account graphs. Pay per byte.
Write
Priority to the next leader.
Route your transactions directly to the validator about to produce the next block. Auction-priced priority, transparent fee curve. Skip the mempool, skip the public RPC roulette.
Bot
Strategy inside the box.
Deploy a WASM strategy in a guest slot inside the validator. React the millisecond state changes; submit on the machine that builds the block. Validator-side, no relay, no proxy.
Modular by design
Pick one. Pick all three.
Slow on state? Read replaces polling with a live push stream straight from validator memory. Losing the race to land? Write routes your transaction directly to the next leader. Both? Bot puts your whole strategy inside the validator — state and execution on the same machine, zero round-trips.
The edge
The fastest path to state on Solana.
Three structural advantages no external relay or RPC provider can match — because they're all consequences of being inside the validator.
01
~35ms validator-internal reads.
Measured on Solana mainnet (Orca round-trip, 2026-06-10). Order-of-magnitude ahead of Yellowstone gRPC (~300ms typical) and public RPC. The fastest decoded-state path published. Independent third-party benchmark forthcoming.
02
One network hop removed — permanently.
Every alternative — RPC polling, gRPC streams, shred feeds — delivers data across a wire and races back through another to land. Catscope reads and submits on the same machine that proposes the block. The closer to the validator, the faster you see state. Nothing outside the validator can close that gap.
03
First-visibility execution.
Your evaluate() runs on the same machine that's about to propose the next block. Decision and submission happen before public mempool traffic can react. You're not racing other searchers to a shared mempool — you're already there.
Developer experience
Trading at validator speed — in ~12 lines.
The surface area is small on purpose. Subscribe to accounts. React to state changes. Submit a transaction. Catscope handles the validator, the optimizer connection, and the marketplace. You write the strategy.
What you write
- Rust, Go, or any language compiling to
wasm32-wasip2. - Open reference bot: noncepad/catscope-rust-bot.
- Subscribe in
on_load(). React inevaluate(). Done. - Quickstart and full design docs at catscope.io/docs.
- Ship a working strategy in an afternoon.
pub(crate) fn on_load(&mut self) {
let g = self.o_graph.take().unwrap();
// Subscribe to a pool account
let pool = account_id_from_pubkey(&POOL_PUBKEY);
let _sub = g.subscribe(pool, 0, 0).unwrap();
self.o_graph.replace(g);
}
pub(crate) fn evaluate(&mut self) {
if self.state.spread > self.cfg.min_spread {
let ix = build_arb_ix(&self.state);
self.wallet.append_ix(ix, 0);
if let Some((sig, tx)) = self.wallet.assemble() {
transactionprocessor::send(sig.as_ref(), tx).ok();
}
}
}What to build
Strategies that need to be early.
If your edge comes from latency, indexer freshness, or first-visibility — Catscope is built for it.
Cross-DEX arbitrage
Spot a mispricing the moment a pool updates. Atomic-bundle the rebalance before the next block.
Market making
Quote tighter spreads when you see depth change ahead of competitors. Re-quote on every state delta.
Liquidation hunting
Watch borrow positions in real-time. First into the liquidation the moment collateral slips.
Sandwich defense
Detect hostile activity targeting your own flow, route around it, and protect your fills before they land.
On-chain order books
Build a CLOB without paying for a third-party indexer. Catscope is the indexer — and the execution lane.
Real-time risk & analytics
Power dashboards, trading terminals, and risk engines from a single decoded stream — no parsing, no polling.
Pricing
One pricing model. Three markets.
Validators set capacity. You bid for your share. Price and allocation adjust automatically with demand — no fixed tiers, no per-request fees.
Read · data streaming
Auction-priced · bid for your share of bandwidth
Write · priority to leader
Auction-priced · bid what landing first is worth
Bot · guest-slot hosting
Auction-priced · clears continuously, no fixed tiers
Commitment
None — bid lengths are configurable, no minimum spend
Open auction · transparent · cancel anytime · no exclusive deals.
Bid table · example
Bidder
Bid
Share
You
10
50%
Trader B
5
25%
Trader C
3
15%
Trader D
2
10%
Total
20
100%
Your share of capacity scales with your bid relative to the field.
What's next
The roadmap that pays you back.
Every milestone on the Catscope roadmap is designed to deepen the edge for traders already on the platform.
Catscope Explorer
Live dashboard of listed validators, auction prices, bot performance, and your own earnings — on-chain, exportable, free to read.
Multi-validator routing
Bid for guest slots across multiple listed validators in a single integration. Redundant pipelines, broader reach, no dropped messages.
Hackathons
Sponsored hackathons focused on building trading strategies on Catscope. Build in public, win prizes, get early access to new features.
CATP token
Governance over fee parameters, marketplace rules, and roadmap priorities. Traders running on Catscope are first-class participants in the program.
Founding builder program
Be early. Earn more.
Traders who deploy strategies during Catscope's beta and early launch phases earn points in our incentives program. Points convert directly to token allocation at TGE — and the earliest builders earn the most. First in, biggest share. The slots that compound the most are the ones still open today.
Why this matters
Speed used to be a question of who you knew.
Private validator relationships, exclusive relays, hand-shake deals — the kind of access that excluded everyone outside the room. Catscope makes that access tradable, on-chain, and open. Bid what landing first is worth to your strategy; your share of priority scales with your bid. Competition by speed and strategy — not by who you've gotten on the phone.
FAQ
Common questions.
How fast is the read path?
~35ms validator-internal read latency measured on Solana mainnet — order of magnitude ahead of standard alternatives (Yellowstone gRPC ~300ms typical, public RPC sub-100ms on dedicated infra). Independent third-party benchmark forthcoming.
What languages can I write strategies in?
Anything that compiles to wasm32-wasip2. Rust and Go SDKs are first-class; the reference bot is open source. Quickstart at catscope.io/docs/tutorials.
Do I need to own a validator?
No. The whole point of Catscope is that you bid for validator-side access on an open marketplace. No co-location, no validator ownership, no middleware.
Can I run multi-validator strategies?
Yes. You can bid for guest slots across multiple listed validators for redundancy and reach. Bots are deployed to a specific validator and cannot move between them — if you want to exploit leader scheduling, build an optimizer that orchestrates multiple bot instances running on different validators simultaneously.
What does it cost to run?
All three markets are auction-priced. Validators set capacity, you bid for your share — allocation scales with your bid relative to the field. No fixed subscriptions, no minimum spend, no co-location contracts.
How does this compare to running my own Geyser pipeline?
Faster, lower overhead, no infrastructure to maintain. Catscope's shared-memory path eliminates the wire hop you'd pay running Geyser yourself — and you don't have to operate the validator either.
Can I trust the validator hosting my bot?
On-chain validator reputation is public; bid lengths are configurable; the architecture prevents the most common form of misbehavior (front-running unsubmitted transactions) at the runtime level. Misbehaving validators get systematically routed around.
Can I cancel or change my strategy?
Yes. Bid lengths are configurable; you can re-deploy, re-target, or exit at any time. No lock-in.
What about regulated trading firms?
An open auction with transparent, on-chain pricing is typically more compatible with regulated trading than private validator relationships. Every fee, every bid, every clear is public and auditable.
How does this compare to shredstream services?
Under shredstream, your bot receives raw shreds and must decode them and maintain local state itself. Under Catscope, your bot reads decoded account and transaction data directly from the graph interface — no decoding, no local state management. For traders already running shredstream-style setups, we're also building zerohop shredstreams — expected to be faster than traditional shredstream services.
How do I deploy a bot onto a validator?
Via a gRPC endpoint that handles the auction and bot upload. Once deployed, your optimizer maintains a persistent streaming connection to the active bot through a separate gRPC interface — similar to stdin/stdout. If that connection drops, the bot is evicted for inactivity.
Can a validator front-run or sandwich my bot's transactions?
The validator cannot read transactions submitted by your bot, which removes the most direct vector for front-running. Beyond that, the economics work against misbehaviour — validators run auctions continuously and their recurring revenue depends on traders returning. A validator that manipulates transactions loses those traders and their fees immediately. Consistent, fair behaviour earns more over time.
Can the validator see or interfere with my bot's logic?
No. All bot logic runs in a sandboxed WASM environment. There is no privileged access granted to the validator over your bot, and no configuration path allows the validator to read or modify your strategy.
Get early access.
Catscope is in early beta. Traders who join now are eligible for the founding builder program. Talk to the team to get set up.