Policy

Earn more by
playing fair.

Catscope focuses on economic incentives over technical restrictions — making the default Agave client competitive and aligning validator revenue with searcher trust.

Technical design

No custom ordering. No bundles.

Catscope does not implement any custom block construction, transaction ordering, or bundling logic.

01

Wraps the Agave validator client with no modifications to how transactions are sequenced.

02

Transactions are sent directly via Agave's sendTransaction mechanism.

03

We do not stall, batch, or reorder transactions.

04

There is no support for transaction bundles or block assembly — these concepts are not part of our design.

Validators using Catscope expose a gRPC endpoint and run a Geyser plugin to collect fees through bandwidth auctions. Catscope acts purely as a coordination layer — not in the critical path of transaction submission or inclusion.

Economic alignment

Long-term revenue over short-term extraction.

Each validator runs multiple auctions per day. Their income depends on searchers voluntarily returning and paying high fees for guaranteed bandwidth.

If a validator engages in sandwiching or manipulates transactions, searchers leave immediately and take their fees with them. This ongoing relationship creates a strong business incentive for validators to maintain fairness, reliability, and transparency. Validators who consistently deliver unmanipulated results earn more over time.

We do not act as a validator or counterparty.

We do not route or front-run transactions.

Our role is to help validators earn recurring revenue by selling reliable, manipulation-free bandwidth.

Searchers connect directly to validators, and can quickly switch if trust is broken.

Frontrunning and sandwiching

No mempool. No privileged access.

Catscope does not filter or censor any transactions. Stricter anti-MEV behavior is an option validators can implement themselves.

01

Searchers do not see any pending transactions that haven't already been submitted to the leader.

02

All data is accessed via Geyser — which reflects already-submitted transactions.

03

We do not provide any private mempool access or privileged information to any party.

Execution environment

Sandboxed. No arbitrary code.

Catscope does not allow searchers to run arbitrary code on the validator.

01

All logic runs in sandboxed WASM environments.

02

There is no privileged access granted to bidders or bots.

03

The plugin ships with safe defaults — no configuration path grants bots access to privileged validator state.

Want to build on fair infrastructure?

Mainnet onboarding is open to a closed cohort of trading teams and validators.