Sign inGet started

Do gRPC and Shreds Help Land Solana Transactions?

Clarifying the difference between 'Reading' and 'Writing' on Solana. Why gRPC and Shreds help you see the chain early but cannot send transactions themselves.

  • November 20, 2025
  • AllenHark Team
A quiet stack of pagesAn abstract drawing of light on the page's dark ground. A neat stack of thin, solid pages, the top one lit, with faint streams of light drifting toward it from the left.A quiet stack of pagesAn abstract drawing of light on the page's dark ground. A neat stack of thin, solid pages, the top one lit, with faint streams of light drifting toward it from the left.

There is a common misconception among new Solana developers:

"I'll upgrade to gRPC or Shreds so my transactions will land sooner."

This is false.

While gRPC and Shreds are critical components of a trading stack, they are strictly Read-Only technologies. They help you see earlier, but they do not help you act.

The Difference Between Read and Write

1. The Read Path (Input)

This is how your bot gets information about the blockchain state (prices, account updates, new blocks).

  • Standard RPC (polling): You ask for data every few seconds and see changes late.
  • gRPC (streaming): Streams account updates, transactions and slots as the validator processes them.
  • Shreds (earliest): Streams block data from the Turbine protocol before the block is even fully constructed.

Verdict: Upgrading to AllenHark gRPC or Shreds lets your bot decide sooner than competitors who poll an RPC.

2. The Write Path (Output)

This is how your bot sends your signed transaction back to the network to be executed.

  • gRPC/Shreds: Cannot send transactions. They are one-way streams from the network to you.
  • sendTransaction (RPC): The standard way. Gossip-based and unpredictable.
  • Jito Bundles: Atomic, but can be congested.
  • Direct Leader Relay: Straight to the leader, so your Write Path keeps up with your Read Path.

The "Speed Gap" Problem

Imagine you have a race car (Shreds) that gets you to the starting line early. But once the race starts, you have to get out and run on foot (Standard RPC).

You lose the advantage you gained.

If you use Shreds to detect an opportunity while the block is being built, but use a Public RPC that passes the trade through gossip, you will still miss the slot.

The Solution: Match Your Read and Write Paths

To truly win, your Write Path must be as direct as your Read Path.

  • Read: Use AllenHark Shreds to detect the signal while the block is still being produced, before RPC confirmation.
  • Write: Use AllenHark Relay to deliver the action over private connections straight to the current leader, over a connection that is already open.

Summary

TechnologyFunctionDirectionWhen you see or send
gRPCAccount UpdatesRead (In)As the validator processes it
ShredsBlock DataRead (In)While the block is being built
RelayTransaction DeliveryWrite (Out)Straight to the current leader

Don't build a half-direct bot. Pair your data feed with a transaction relay that goes straight to the leader.

Explore AllenHark Infrastructure