Migrating from Triton One
The Yellowstone protocol remains familiar; update the RPC endpoint, gRPC endpoint, and credential.
Compatibility
- Standard Solana JSON-RPC methods remain compatible.
- Yellowstone protobuf message shapes depend on the client/proto version you install.
- The current @triton-one/yellowstone-grpc package works with OpenInfra using its HTTPS constructor endpoint.
Update RPC configuration
Before:
TRITON_RPC_URL=https://my-project.rpcpool.com/your_tokenAfter:
OPENINFRA_RPC_URL=https://rpc.sol.openinfra.shOPENINFRA_API_KEY=sk_live_xxxxxxxxxxxxUpdate Yellowstone
Before:
const client = new Client( "https://my-project.rpcpool.com", process.env.TRITON_TOKEN!,);After:
const client = new Client( "https://geyser.sol.openinfra.sh:443", process.env.OPENINFRA_API_KEY!,); await client.connect();const stream = await client.subscribe(request);OpenInfra's Yellowstone client credential is passed as the constructor token and sent as
x-tokenmetadata.Verify the first update
Subscribe to confirmed slots first. Receiving a decoded slot update verifies DNS, TLS, authentication, and protobuf compatibility before you migrate more complex filters.