Trencher Labs: Jito rate limit request

Trencher Labs · October 16, 2026

What we're building

Trencher Labs is a Solana trading terminal for launchpad and memecoin traders. Website: trencherlabs.com. It's invite-only right now, and we can give your team access.

Our data comes from Helius: one LaserStream gRPC feed of every launchpad trade (about half a terabyte a day), plus their RPC and Sender.

How we send to Jito

Every trade goes to Jito as one tipped bundle, sent to the block engine region of the upcoming leader plus one nearby region.

  1. The user's trade runs on the execution node closest to them: Virginia, Salt Lake City, Miami, US West or Germany.
  2. We build and sign the transaction once. The Jito tip is inside it, as a transfer to one of your tip accounts.
  3. We size tips from your tip stream: p50 normally, p75 when it's busy, capped at 0.01 SOL.
  4. We check the leader schedule and send the bundle to the region of the upcoming leader, plus one nearby region. It's one signature, so it can only land once.
  5. We also race Helius Sender (which forwards to Jito too), Jupiter and Triton. Whichever lands first wins, and we confirm the signature on our side.

No spam, no duplicates, no arbitrage or backrun traffic. Every request is a real user trade.

Why 2 rps runs out fast

The limit is per region, and with leader targeting, one region carries every trade we send during that leader's slots. So 2 rps means 2 trades per second for the whole platform.

A 429 doesn't kill the trade, because the other lanes still carry it. But the trade loses the Jito path exactly when it matters, and our Jito land rate looks worse than it really is.

What we're asking for

We're asking for 25 rps per region now and 100 rps per region at public launch.

StageConcurrent tradersPeak trades per secondRate limit per region
Next 30 daysabout 1,000about 1725 rps
Public launchabout 4,000about 67100 rps

The math: one trade per active trader per minute during a busy stretch, plus 50% headroom for bursts. With leader targeting, each region we send to sees our full platform peak.

Starting now, every request from every node carries our UUID in x-jito-auth. That gives you our real volume and land rate under it for the 7-day review, and we're happy to share our own landing stats too.

Three questions so we size this right:

  1. Is the per-region limit shared by every IP that sends with our UUID, or counted per IP?
  2. Do sendBundle and sendTransaction count the same against it?
  3. Is there an endpoint you'd recommend for the upcoming leader's region, so we match your mapping?

Contact

Yowie on Discord (this ticket), or support@trencherlabs.com.