One feed, every receiver.
Solana shreds, the packets of each block, go out once over multicast and every receiver takes the same feed: validators, RPC nodes, a local RPC on your machine, Chrome and phones.
- Current slot
- —
- FEC sets / s
- —
- KB / s
- —
- Shreds received
- —
- Decode p50
- —
| Slot | FEC set | Bytes |
|---|---|---|
| No FEC sets yet. A FEC set is one erasure-coded batch of shreds. | ||
Connecting to the feed… Open the full visualizer →
Node operators
A signed release turns a host you own into a non-voting Solana mainnet RPC node fed by the shreds: JSON-RPC on 8899 and gRPC on 10000. A validator takes the same feed on its TVU port. A fresh node downloads a snapshot and can take hours to catch up.
| Host | 16 or more dedicated physical cores at a high sustained clock, 384 GB RAM or more, two blank local NVMe disks over 1.9 TB each. A shared-core virtual machine falls behind the chain. |
|---|---|
| Network | A reserved public IPv4 address, 1 Gbit/s or more, TCP and UDP 8000–8030 open inbound |
| System | Ubuntu 24.04 LTS on x86-64 |
Chrome users
Multicast Gateway (BEACON) connects Blockcast web apps in Chrome to native and tunneled multicast; the live panel above then reads "Multicast".
dApp & bot builders
A local RPC on your machine answers what the feed carries and passes every other request, writes included, unchanged to your own RPC. The receiver and go-amt's amt_bridge come with pilot access; the receiver needs Node 22.18 or later.
$ amt_bridge -relay <relay>:2268 \
-iface <ifname> -source <source> \
-group <group> -port <port> \
-out 127.0.0.1:20001 &$ node src/node.ts \
--upstream https://<your RPC> \
--tx-feed udp://127.0.0.1:20001 \
--allow-origin https://<your dApp>Custom RPC http://127.0.0.1:8899 (WebSocket on 8900) bots and CLIs use the same URL
Phone users
The Blockcast Beacon app receives the feed in the background and hands it to pages in your phone's browser through window.multicast.
What you get
| Item | What it is | Where it runs | What your app reads |
|---|---|---|---|
| RPC node kit | A signed release: Agave with a Geyser gRPC plugin, the Blockcast Shreds gateway, a host firewall, metrics | A host you own, on any cloud provider | JSON-RPC on 8899 · gRPC on 10000 |
| Local RPC | The receiver on your own machine, fed through an AMT tunnel to the relay | Your laptop or server | http://127.0.0.1:8899 |
| Multicast Gateway (BEACON) | Chrome extension + gateway: connects Blockcast web apps to native and tunneled multicast | Chrome on desktop · Chrome Web Store | window.multicast |
| Blockcast Beacon | Phone app: receives over native multicast or an AMT tunnel and hands the feed to pages in your browser | Android on Google Play · iOS in TestFlight | window.multicast |
Pricing · pilot
Metering is not active, so no usage charge applies yet. The per-GB price is set on chain and shows here, read from the registry. Once you subscribe in the registry below, the program never bills above your price ceiling, never faster than your spend cap per slot, and never more than your balance.
- Price per GB
- Loading…
- Hold fee for a channel
- —
- Channels active
- —
Manage your subscription
Channels, balances and wallet actions live in the registry below.
Channel Registry
The on-chain registry for Blockcast's multicast feeds. Read it without a wallet; connect one to reserve a channel, subscribe to a feed, or manage your channels and subscriptions. A channel sends every transaction that calls one program as a top-level instruction, or lists one account among its static keys, to anyone; once metering starts, its sponsor pays for it. A subscription will pay for your own delivery of a feed outside the channel set, such as a Blockcast Shreds layer once layers open, to the gateways you allow.
Registry summary
Registry details
- Who approves channels
- —
- Withdrawal wait after a stop
- —
- Hold fee per active slot for a place in the cap
- —
- Price per GB, by region
- Billing signer meter
- —
- Registry config
- —
- Publisher
- —
- Program
- —
- Program status
A channel sends every transaction that calls one program as a top-level instruction, or lists one account among its static keys, to anyone. Once metering starts, the sponsor pays for it.
| Details | Filter | Status | Sponsor | Balance | Limits | Billed so far | Created slot | Actions |
|---|
A subscription will pay for your own delivery of a feed outside the channel set, to the gateways you allowlist, once delivery by subscription and metering start. Until then it only records your deposit, limits and allowlist on chain.
| Details | Multicast group | Status | Subscriber | Balance | Limits | Billed so far | Created slot | Gateway allowlist | Actions |
|---|
Reserve a channel for a program or account. It goes live when the publisher approves it.
Pilot: Reserve creates an on-chain channel and holds your refundable deposit in it. Billing starts only when metering is switched on; until then nothing is charged, and Close returns the deposit in full, less network fees. Your deposit and limits are recorded on chain now and apply from the day metering starts.
A subscription will pay for your own delivery of one feed outside the channel set, such as a Blockcast Shreds layer once layers open. Enter the group address you were given for it.
Pilot: Subscribe creates an on-chain subscription and holds your refundable deposit in it. Delivery on subscription groups is not enforced yet: there is no relay filter, no meter and no per-layer IPv6 groups yet. Billing starts only when metering is switched on. Until then nothing is charged, and Close returns the deposit in full, less network fees. Your limits and gateway allowlist are public on chain.
Approve reservations and set the registry's prices and limits.
Approvals
No pending reservations.