Migrating from Triton One

OpenInfra.sh runs the same Yellowstone gRPC stack as Triton. The migration is mostly a URL swap.

Compatibility

Yellowstone gRPC protocol is identical — same proto definitions, same message shapes.
JSON-RPC 2.0 methods are fully compatible.
The @triton-one/yellowstone-grpc npm package works unchanged.

Before:

TRITON_RPC_URL=https://my-project.rpcpool.com/your_token

After:

RPC_URL=https://rpc.openinfra.shOPENINFRA_API_KEY=oi_live_xxxxxxxxxxxx

Before:

const client = new Client(  "my-project.rpcpool.com:443",  undefined,  { "x-token": "your_triton_token" });

After:

const client = new Client(  "grpc.openinfra.sh:10000",  undefined,  { "x-token": process.env.OPENINFRA_API_KEY });

The x-token header key is the same. Only the endpoint and token value change.

Private fabric (optional)
If your application runs on an OpenInfra server, connect to the local gRPC socket at /run/yellowstone-grpc/yellowstone.sock instead of the public endpoint. This eliminates the network hop and TLS overhead entirely.