Drag to spin · pinch or + − to zoom
- IN publishers Up, where the feed enters
- OUT receivers Up, where it is delivered
- Registered, none Up
- Reach, not the route
Reading the figure
Each point on the globe is a DoubleZero metro, placed at the coordinates the ledger stores for it. A diamond with broadcast arcs, labelled IN, marks ingress, where a feed’s publishers attach and its data enters the network. A ring, labelled OUT, marks egress, where its receivers attach and the data is delivered. A metro that does both shows the diamond inside the ring. The numbers count accounts reporting BGP Up. A dashed outline means accounts are registered there but none report Up.
The lines are reach. Each one joins a metro with a publisher reporting Up to a metro with a receiver reporting Up, because multicast delivers from any publisher to every subscriber. Every pair gets a line, so Solana’s 23 ingress metros and 15 receiver metros make 331 of them. The lines are great circles lifted off the surface, not fiber routes. The ledger holds no per-feed path and doesn’t record which publisher wins at a receiver.
When a feed loads, rings spread from every ingress metro at the speed of light in fiber, about 204 km per millisecond, and each line grows with its ring. A receiver glows when the nearest ring reaches it. The clock at the lower right counts fiber milliseconds. Real paths are longer, so read the times as lower bounds. After the first wave, a pulse keeps running along the lines at the same speed. Select a metro to pick out its lines.
Method
- GroupRead every multicast group from the public mainnet-beta ledger, without a wallet or subscription.
- AccountMatch each group’s address to the
publishersandsubscriberslists on user accounts. - DeviceFollow each user to the DoubleZero device it attaches through.
- MetroFollow the device to its location and exchange records, which supply the metro name and coordinates.
- StatusRead the stored BGP status, and count only accounts reporting Up as live points.
What this cannot tell you
- Where the source really is. A metro is where a publisher enters DoubleZero. It isn’t necessarily the publisher’s host, a matching engine, or the upstream collection point.
- Whether packets are flowing. BGP status is stored and reported, not independently measured. A publisher reporting Up may not be transmitting.
- Who is receiving. Receivers are network attachments, not people, firms, or paying customers. Some are monitoring or test systems.
- How many customers exist. One account can subscribe to several feeds. Family totals are deduplicated within a family and must not be added across families.
- Subscriptions without attachments. A paid subscription with no registered receiver account is invisible here. So is any feed on another network.
- Which source wins. The ledger doesn’t show which publisher’s packets reach a given receiver first.
- Whether every label is official.
jito-shredstreamhas no catalog entry, so its name rests on the group code alone.
All feeds
Up counts, with registered totals after the slash. Select a row to load that feed on the globe.