Stream Pump AMM Data with Helius - gRPC
Learn how to stream live Pump AMM data from Solana using gRPC streaming with Helius.
gRPC Streaming
Why choose gRPC – lowest latency per‑message, Protobuf types, HTTP/2 transport.
Requires a Dedicated Node or Laserstream – both provide a gRPC endpoint and auth token.
How it works – open a bidirectional stream, send a
SubscribeRequest
, then receive a continuous feed of Pump AMM
transactions. The sample handles reconnection up to ten times with exponential
back‑off.
Requirements
Set Up Node.js Environment
Ensure you have Node.js ≥ 18 (tested with v20) installed on your system. You can check your version with:
If needed, install or update Node.js from nodejs.org.
Install TypeScript
If you plan to run the .ts
samples with ts-node
, install TypeScript ≥ 5:
Verify the installation:
Get Helius Access
You’ll need a Helius Dedicated Node or Laserstream subscription. Sign up through the Helius Dashboard if you don’t already have access.
Obtain gRPC Credentials
After subscribing to a Dedicated Node or Laserstream, you’ll receive:
- A gRPC endpoint URL
- An authentication token
Keep these secure as you’ll need them for your environment variables.
Implementation
Install Dependencies
Create the Stream Manager
Create a file named grpc-pump-stream.ts
with the following code:
Implement Transaction Monitoring
Add the transaction monitoring code to your file:
Set Environment Variables
Create a .env
file or set environment variables with your gRPC endpoint and auth token:
Replace the placeholder values with your actual Helius Dedicated Node or Laserstream endpoint and authentication token.
Run the Application
Execute the script to start streaming Pump AMM data:
You should see JSON-formatted Pump AMM transactions streaming in your terminal.
Key benefits
- Lowest latency - gRPC’s binary protocol is optimized for high-throughput, low-latency data streaming
- Structured data - Get fully parsed transaction objects with all accounts and instructions
- Resilient connection - Built-in reconnection logic with exponential backoff
- Production ready - Designed for high-volume applications that need reliable data streams
Common issues and solutions
Next steps
Implement Message Queue
Add a message queue like RabbitMQ or Kafka to process transactions asynchronously:
Add Persistent Storage
Implement a database solution to store transaction data for later analysis:
Create Alerts
Set up a notification system for important events or threshold crossings: