Connect, subscribe, measure.

NoName serves executed Solana transactions and account updates over the Yellowstone gRPC protocol. If your code already talks to a Yellowstone Geyser endpoint, switching is a URL and a token.

Overview

Most Geyser endpoints sit behind a validator: the validator receives shreds, replays the block, and a plugin forwards the results. NoName runs its own execution engine directly on the shred stream. Transactions are executed as their shreds arrive, and the resulting account writes and transaction results are sent to subscribers straight from execution.

What you get:

• Account updates: the full account (or the slices you ask for) after each transaction that writes it.
• Transaction updates: the executed transaction with its message, status, compute units and fee.
• Processed commitment, the earliest point at which executed state exists.
• Slot updates: slot status notifications, at processed commitment.
• The Yellowstone wire format, so the standard Rust, TypeScript, Go and Python clients work unchanged.

What it is not: an RPC node, a shred feed, or a source of block or entry notifications. See what is not served.

Quick start

1. Sign in to the dashboard with Discord.
2. Open Subscribe, choose a location and enter the public IPv4 address of the server that will connect.
3. Start the free 3-hour trial, or pick a paid period and pay in USDC. Within a few seconds the dashboard shows your endpoint and your x-token.
4. Point your Yellowstone client at the endpoint, send the token, and subscribe.

grpcurl -plaintext \
  -H "x-token: $NONAME_TOKEN" \
  -d '{"transactions":{"pump":{"accountInclude":["pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA"]}}}' \
  ams.no-name.io:10000 geyser.Geyser/Subscribe