Shreder Docs
Data Streaming

Geyser gRPC / Fastlane

100% compatible with standard Yellowstone Geyser gRPC — Regular Geyser and Fastlane

Shreder Geyser gRPC / Fastlane is 100% compatible with standard Yellowstone Geyser gRPC (same protocol, protos, filters, and clients).

Point any Yellowstone gRPC client at a Shreder endpoint and keep your existing subscription logic. You get structured Solana updates for transactions, accounts, slots, blocks, and metadata.

Regular Geyser vs Fastlane

ModeWhat it is
Regular GeyserStandard Yellowstone Geyser gRPC for reliable production streaming
FastlaneShreder’s accelerated implementation of the same Yellowstone Geyser gRPC interface — typically 2× faster delivery, no client changes

Fastlane is not a separate data format. Change endpoint (and token) only — filters, protos, and stream types stay the same.

In GeyserBench Fastlane uses kind = "yellowstone".

What you can subscribe to

Standard Yellowstone stream types, including:

  • Transactions
  • Accounts (exact account, owner, memcmp, data-size, optional data slices)
  • Slots
  • Blocks and metadata

Keep subscriptions focused on the data your backend needs.

Usage

  1. Get a Shreder Geyser gRPC / Fastlane endpoint from the console or contact.
  2. Use any standard Yellowstone gRPC client.
  3. Keep your existing SubscribeRequest filters.

When to use it

  • You already run Yellowstone gRPC clients
  • You need post-execution context (state, logs, balances, outcomes)
  • You want structured multi-stream subscriptions (accounts + slots + transactions)

For earlier pre-execution Shred Streams, see Decoded Shreds or Binary.

Endpoints

Fastlane is available in all five regions. All endpoints share the same limits.

RegionEndpoint
Frankfurthttp://fra.fastlane.shreder.xyz:10000
Amsterdamhttp://ams.fastlane.shreder.xyz:10000
New Yorkhttp://ny.fastlane.shreder.xyz:10000
Londonhttp://lon.fastlane.shreder.xyz:10000
Tokyohttp://tyo.fastlane.shreder.xyz:10000

Limits

These limits apply to every Fastlane endpoint.

LimitValue
Max concurrent connections per token per region8
Max subscriptions / filters per connection1000
Total filters per connection150
Max accounts per connection150,000
RegionsFrankfurt, Amsterdam, New York, London, Tokyo

On this page