This page has longer, end-to-end examples. They combine the feed subscription and HTTP/3 submit surfaces into programs that you can run. Feeds use @clutchcall/sdk/moqt. Transactions use the HTTP/3 submit API.

Recipe 1 — A feed-driven transaction submitter

Watch the live blockhash and priority-fee feeds. Build a transaction against the freshest blockhash. Price it from the live p50. Land it through the BDN with fan-out. The BDN dedups on the signature. Thus a retry is idempotent.
1

Connect to the feed relay

One client serves both feeds. It reconnects automatically and replays subscriptions.
2

Track the freshest blockhash and fee

Keep the latest object from each track in memory. The feed pushes a new object every slot (or every N slots for the fee track).
3

Build and sign against live state

Use your wallet/keypair and Solana tooling to build a tx. Use the live blockhash and a compute-unit price set from the live p50. Replace the placeholder builder with your own.
4

Land it through the BDN with a safe retry

Fan-out submits to every edge. The 64-byte-signature dedup makes retries idempotent. Thus you can loop until the tx lands or the blockhash expires.
For latency-sensitive landing, set fanout_leaders (server-side) above 1. The BDN then lands on the next leader before that leader becomes current. It moves ahead of the slot boundary instead of racing it.

Recipe 2 — A private gossip/Geyser feed consumer

Consume a private feed and drive a slot-aligned cache. A private feed is your own ingest endpoint, republished as an org-scoped MoQT track. The private namespace is sol/feed/<orgId>. Subscribe with an org-scoped token. The relay holds your subscribe even before the ingest publishes. Thus it is safe to start this at boot.
1

Subscribe to the private slots track

2

Layer the blockhash track on the same client

One connection multiplexes every track. You do not dial a second time.
3

Expose a freshness check

The frame timestamp shows how stale your view is. You can gate trading logic on it.
4

Shut down cleanly

You configure the private ingest endpoint in the portal/control plane, not through an SDK call. The endpoint is your gossip/Geyser gRPC URL and its auth token, sealed at rest under your org. The SDK only subscribes to the resulting sol/feed/<orgId> tracks.

Recipe 3 — Combining a feed and a direct TPU land

Sometimes you already know the leader that you want (e.g. you co-locate next to one). Then skip the mesh. Watch the slot feed to fire at the right moment. Then land straight on that validator’s TPU with the direct /tpu route.
The direct /tpu route does no fan-out and no dedup across edges. If you call it in a loop, you can double-land. Use /bdn/submit (with its signature-keyed dedup) whenever you retry.