Switching providers
Slipstream serves the Yellowstone gRPC protocol, so a client that streams from another Yellowstone provider streams from Slipstream with two changes: the endpoint and the token. Requests, filters, commitment levels and the updates you receive keep their shape.
The two lines#
Point the client at your region's endpoint, https://slipstream-fra2.reflow.xyz today (all regions), and pass a Slipstream API key where the old provider's token went. Slipstream reads it from the x-token header, the Yellowstone convention.
endpoint = "https://<your region's endpoint>"
token = env.SLIPSTREAM_KEY # rf_live_...
What to check#
- Replay. Slipstream keeps the last 300 slots for
fromSlot. If your client resumes from further back after a long outage, it needs another source for the gap (replay). - Region. Each subscription is in one region. Pick the one nearest the servers that run your client.
- Keys. Keys start with
rf_live_. If your code validates a token's format, allow it.
Switching back is the same two lines.