Kaldera gRPC

Kaldera is constant-k's Yellowstone (Geyser) gRPC service. Any Yellowstone client works against it without code changes, given a Kaldera endpoint and your API key as x-token.

Endpoints

Connections use TLS. See Authentication.

Server version and protocol files

Kaldera runs yellowstone-grpc v16.1.1+solana.4.3.0, the upstream release with no local changes. A client generated from the protocol files of that release matches the server field for field. GetVersion reports the running release, its protocol version and the Agave version behind it.

Client packages from that release: yellowstone-grpc-client 15.0.0 and yellowstone-grpc-proto 14.0.1 on tonic 0.14, or @triton-one/yellowstone-grpc 9.0.0 for TypeScript.

Methods

The geyser.Geyser service defines ten RPCs. The table records what each returns on Kaldera, measured against a live endpoint.

What Kaldera adds to Yellowstone

Streams and limits

Kaldera accepts every Yellowstone filter type: accounts, transactions, transaction status, slots, blocks, block meta and entries. Each subscription picks one commitment level: PROCESSED, CONFIRMED or FINALIZED. An account set can also be sent as a compressed filter rather than a list, which is how a set larger than the list limits is tracked. See Filters for every option, the per-stream filter limits and the gRPC status returned when a subscription is refused.

Kaldera is included on Blade Runner and Nexus. Limits apply per region.

A stream that goes over its plan's bandwidth limit is throttled. Kaldera buffers up to 64 MB of your data while you catch up. If the buffer fills, Kaldera drops the oldest queued updates and keeps you on the newest data. The full tables are on Plans & Limits.

Compression

Compression lowers bandwidth, which matters most on streams carrying many accounts and on streams close to the Blade Runner limit.

import Client from "@triton-one/yellowstone-grpc";

const client = new Client(
  "https://kaldera-newyork.constant-k.com",
  process.env.CK_API_KEY,
  {
    grpcDefaultCompressionAlgorithm: 1, // 0 = gzip, 1 = zstd
    grpcMaxDecodingMessageSize: 64 * 1024 * 1024, // room for large account updates
  },
);
await client.connect();

Clients

Minimum versions for transaction v1

Mainnet carries version 1 transactions as well as legacy and version 0. Nothing about Kaldera changes for them: the same endpoints, the same x-token key, the same SubscribeRequest and the same filters. The client changes: a proto that does not know the new fields cannot read a version 1 transaction that arrives on a stream you already hold.

In other languages, the newest client release carries the fields. A self-generated client needs protocol files at yellowstone-grpc-proto 12.6.0 or later; the files above are 14.0.1. See Transaction v1.

Kaldera, Turbo Kaldera, ShredPrism or WebSockets

Data Stages sets out the pipeline these four sit on, and the stage each one delivers at. The Benchmarks page compares Kaldera with another Yellowstone provider in each region and publishes the results live.

Related