HyperShreds: premium Solana shreds for $250 a month
HyperShreds is NoLimitNodes’ premium Solana shred feed. We buy shreds from the most expensive providers and fan them out over ultra-low-latency infrastructure to a UDP port you control. It costs $250 a month per destination, or $2,500 a year, and Max and Enterprise include it.
- Shreds bought from the most expensive providers
- Delivered by ultra-low-latency fanout to your UDP port
- $250 a month per destination, or included in Max and Enterprise
HyperShredsper destination
$250 a month
or $2,500 a year, two months free
Max, $300/mo, includes it, with HyperStreams and higher limits than Ultra. Enterprise includes two.
- 1Buy. We pay the most expensive shred providers for their feeds.
- 2Fan out. Our ultra-low-latency fanout delivers each shred to every customer.
- 3Receive. Your server gets raw shreds on its own UDP port for $250 a month.
The best Solana shreds cost thousands of dollars a month
A shred is one of the small packets a Solana block is split into as the leader sends it out, and it reaches you before the block is executed, confirmed or visible through RPC. The sooner your server has it, the sooner your bot can act. The feeds that deliver shreds earliest cost thousands of dollars a month, so the teams that can afford them see every block ahead of everyone else.
New to shreds? Read what a Solana shred is.
- 1
Premium feed
The best shred providers deliver each block first. Their feeds cost thousands of dollars a month.
- 2
Everyone else
Without a premium feed your bot sees the same block later. That delay is the gap.
- 3
Closing it
Closing the gap used to take a subscription priced for trading firms. HyperShreds closes it for $250.
How HyperShreds works: we buy the premium feeds, you pay $250
Think of a broker that opens to everyone what only institutions could reach. We pay the premium providers and run the delivery, so you get the shreds without carrying the bill.
- 1
We buy from the most expensive providers
We hold the subscriptions that cost thousands of dollars a month, so you do not have to.
- 2
We fan out with ultra-low-latency infrastructure
Our own delivery layer pushes each shred to every customer destination, built to add as little delay as possible.
- 3
You pay $250, not thousands
One destination is $250 a month, or $2,500 a year. Max and Enterprise include it.
What would your feed cost you?
Put your own price in and see it against HyperShreds.
Type your own figure. The starting value is only an example.
How many premium feeds do you run?
Many setups need more than one for complete FEC sets. Why.
$2,750 a month less
$33,500 a year if you pay yearly ($2,500).
A direct feed and HyperShreds are different products. This compares what you pay, not how fast either is: measure that with the scripts further down.
FEC completeness: why one premium feed is often not enough
Solana splits each block into FEC sets: data shreds plus the coding shreds that protect them. A set rebuilds only when you hold at least as many of its shreds as it has data shreds. A feed is FEC-complete when it delivers enough of every set. Few premium feeds do on their own, because many assume you subscribe to several.
Premium feed A on its own leaves this set 2 shreds short, so it cannot be rebuilt. Switch on a second feed.
- 1
What it means
Every FEC set has data shreds and coding shreds. Any N of its shreds, where N is how many data shreds it has, rebuild the whole set. If fewer arrive, that part of the block stays incomplete on your side.
- 2
Why one feed often falls short
Many premium feeds are built and priced on the assumption that you also subscribe to others, so one feed on its own may not hand you enough of every set. In some cases you need more than one premium feed to have a complete premium service.
- 3
What HyperShreds does
HyperShreds draws on several premium feeds, so completeness does not depend on any one provider. You pay for one destination, $250 a month, not for each feed.
What a complete premium service costs
Completeness is what you are really buying. Here is what it takes to get it.
One premium feed
Can leave gaps in some sets.
can leave gapsThousands of dollars a monthTwo or more premium feeds, combined by you
Complete sets, but you pay for each feed and combine them yourself.
completeSeveral times thatHyperShreds
Several premium feeds behind one destination.
complete, combined for you$250 a month
Do not take that on trust either: fec_check.py counts complete, recoverable and incomplete sets on your own server, for each feed and for both together.
Built for bots that need to see blocks first
Earlier data helps wherever a decision depends on seeing a block before the next bot does.
Launch and snipe bots
Act on new pools and tokens as their shreds arrive, ahead of the RPC that reports them later.
Arbitrage and market making
Start every quote and cross-venue trade from fresher state, so a price move reaches you earlier.
Liquidators and MEV searchers
Spot an account crossing its threshold and prepare the transaction while the block is still arriving.
Indexers and analytics
Take the earliest raw view of the chain, then confirm what happened with gRPC or RPC.
HyperShreds sees the block early. Pair it with Yellowstone gRPC to confirm what happened and UltraSend to send the transaction.
What you receive: raw Solana shreds over UDP
The same raw, Jito-compatible shreds as Shredstream, on our lower-latency delivery.
- Delivery
- UDP packets to a public IPv4 address and a port from 1024 to 65535 that you control.
- Format
- Raw Solana mainnet data and coding shreds in a Jito-compatible wire format.
- Proof of ownership
- One SHREDCAST-VERIFY packet. Paste its token back and delivery starts.
- Destinations
- Max includes 1 and Enterprise includes 2. Each extra one is $250 a month.
- Not included
- Logs, balances, errors and commitment level. Raw shreds carry none of them.
- You operate
- The receiver: deshredding, duplicates, gaps and forks.
- Signature64 bytesbyte 0
- Variant1 bytebyte 64
- Slot8 bytesbyte 65
- Index4 bytesbyte 73
- Version2 bytesbyte 77
- FEC set4 bytesbyte 79
- Payloaddepends on the shred typefrom byte 83
Slot and index sit at fixed offsets, so a receiver can read them without deshredding. The script below uses exactly those two fields to match the same shred across two feeds.
The tradeoff is real. Raw shreds carry no transaction logs, balance changes, errors, compute usage or commitment level. They can arrive twice, out of order or not at all, and a block seen early can belong to a fork that loses. Treat HyperShreds as the earliest signal, and confirm what matters with Yellowstone gRPC or RPC. Raw shred data behavior and Shredstream vs Yellowstone gRPC explain what to use when.
HyperShreds, Shredstream or a direct feed
Three ways to get shreds, and what each one asks of you.
| Topic | Buy a feed directly | Shredstream | HyperShreds |
|---|---|---|---|
| What it is | A premium provider’s own shred feed | Raw Jito-compatible shreds on our standard delivery | The same shreds on our lower-latency delivery |
| Typical monthly cost | Thousands of dollars | 1 destination with Ultra, extra destinations $100 each | $250 per destination, or $2,500 a year |
| Included in a plan | No | Ultra | Max (1 destination) and Enterprise (2) |
| Who runs delivery | The provider, to you | NoLimitNodes | NoLimitNodes, on ultra-low-latency fanout |
| Built for | Firms that can carry the bill | Bots that need raw shreds on a budget | Bots that need the premium feed without the premium bill |
Provider pricing varies. The first column describes the usual range, not any one provider.
Do not take our word for it: measure it
Two receivers, one machine. Point one destination at your current feed and one at HyperShreds. The first script prints which feed delivered each shred first. The second prints how many FEC sets each feed delivered in full, and how many you would hold by running both. One clock times both, so the comparison is fair.
Which of two feeds delivers each shred first? Python 3, standard library only.
#!/usr/bin/env python3# first_shred.py: which of two feeds delivers each shred first?# Point one destination at each port below, then run this on that one machine: python3 first_shred.py [seconds]import selectors, socket, struct, sys, time
FEEDS = {"current": 20001, "hypershreds": 20002} # feed name -> UDP port on this machineSECONDS = int(sys.argv[1]) if len(sys.argv) > 1 else 60HEADER = 83 # common shred header: signature 64, variant 1, slot 8, index 4, version 2, fec set 4
sel = selectors.DefaultSelector()for name, port in FEEDS.items(): sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.setsockopt(socket.SOL_SOCKET, socket.SO_RCVBUF, 8 << 20) sock.bind(("0.0.0.0", port)) sock.setblocking(False) sel.register(sock, selectors.EVENT_READ, name)
arrived = {} # (slot, index, variant) -> {feed: first arrival in ns}packets = dict.fromkeys(FEEDS, 0)end = time.monotonic() + SECONDSwhile time.monotonic() < end: for key, _ in sel.select(timeout=1): while True: try: pkt = key.fileobj.recv(2048) except BlockingIOError: break now = time.perf_counter_ns() if len(pkt) < HEADER or pkt.startswith(b"SHREDCAST-VERIFY"): continue slot, index = struct.unpack_from("<QI", pkt, 65) arrived.setdefault((slot, index, pkt[64]), {}).setdefault(key.data, now) packets[key.data] += 1
a, b = FEEDSboth = [t for t in arrived.values() if a in t and b in t]print("packets received:", packets)print("shreds seen on both feeds:", len(both))for first, second in ((a, b), (b, a)): lead = sorted((t[second] - t[first]) / 1e6 for t in both if t[first] < t[second]) if lead: p95 = lead[min(len(lead) - 1, int(len(lead) * 0.95))] print(f"{first} first on {len(lead) / len(both):.0%} of them: median {lead[len(lead) // 2]:.2f} ms ahead, 95th percentile {p95:.2f} ms")How many FEC sets does each feed deliver in full? Python 3, standard library only.
#!/usr/bin/env python3# fec_check.py: how many FEC sets does each feed deliver in full?# Point one destination at each port below, then run this on that one machine: python3 fec_check.py [seconds]import selectors, socket, struct, sys, timefrom collections import Counter
FEEDS = {"current": 20001, "hypershreds": 20002} # feed name -> UDP port on this machineSECONDS = int(sys.argv[1]) if len(sys.argv) > 1 else 60HEADER = 83 # common shred header; a coding shred adds num_data, num_coding and position (u16 each)
def kind(variant): # "data", "code", or None for a variant this script does not know if variant == 0xA5 or variant & 0xF0 in (0x80, 0x90, 0xB0): return "data" if variant == 0x5A or variant & 0xF0 in (0x40, 0x60, 0x70): return "code"
sel = selectors.DefaultSelector()for name, port in FEEDS.items(): sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.setsockopt(socket.SOL_SOCKET, socket.SO_RCVBUF, 8 << 20) sock.bind(("0.0.0.0", port)) sock.setblocking(False) sel.register(sock, selectors.EVENT_READ, name)
new = lambda: {"data": set(), "code": set(), "need": None} # data indexes, coding positions, data shreds in the setsets = {name: {} for name in FEEDS} # feed -> (slot, fec set) -> new()end = time.monotonic() + SECONDSwhile time.monotonic() < end: for key, _ in sel.select(timeout=1): while True: try: pkt = key.fileobj.recv(2048) except BlockingIOError: break if len(pkt) < HEADER or pkt.startswith(b"SHREDCAST-VERIFY") or not kind(pkt[64]): continue slot, index = struct.unpack_from("<QI", pkt, 65) (fec_set,) = struct.unpack_from("<I", pkt, 79) fec = sets[key.data].setdefault((slot, fec_set), new()) if kind(pkt[64]) == "data": fec["data"].add(index) elif len(pkt) >= HEADER + 6: need, _, position = struct.unpack_from("<HHH", pkt, HEADER) fec["code"].add(position) fec["need"] = need
def verdict(fec): if fec["need"] is None: return "unknown" # no coding shred seen, so the size of the set is not known if len(fec["data"]) >= fec["need"]: return "complete" # every data shred arrived if len(fec["data"]) + len(fec["code"]) >= fec["need"]: return "recoverable" # some are missing, but enough shreds arrived to rebuild them return "incomplete"
both = {} # what you would hold if you ran both feeds and combined themfor view in sets.values(): for key, fec in view.items(): merged = both.setdefault(key, new()) merged["data"] |= fec["data"] merged["code"] |= fec["code"] merged["need"] = merged["need"] or fec["need"]
slots = {key[0] for key in both}partial = {min(slots), max(slots)} if slots else set() # the first and last slots are only partly capturedprint(f"{'':13}{'sets':>6}{'complete':>10}{'recoverable':>13}{'incomplete':>12}{'unknown':>9}")for name, view in {**sets, "both feeds": both}.items(): kept = [fec for key, fec in view.items() if key[0] not in partial] count = Counter(verdict(fec) for fec in kept) share = lambda v: f"{count[v] / len(kept):.0%}" if kept else "-" print(f"{name:13}{len(kept):6}{share('complete'):>10}{share('recoverable'):>13}{share('incomplete'):>12}{share('unknown'):>9}")packets received: {'current': …, 'hypershreds': …}shreds seen on both feeds: …hypershreds first on …% of them: median … ms ahead, 95th percentile … ms sets complete recoverable incomplete unknowncurrent … …% …% …% …%hypershreds … …% …% …% …%both feeds … …% …% …% …%- Complete: every data shred of the set arrived. Recoverable: some are missing, but enough shreds arrived to rebuild them.
- Incomplete: not enough arrived to rebuild the set. Unknown: no coding shred was seen, so the size of the set could not be read.
- The "both feeds" row is what you would hold if you ran both feeds and combined them yourself.
- Run them on the server you will trade from. Latency depends on where that server sits.
- Python is accurate to about a millisecond. Use kernel timestamps if you need finer.
- The packet counts tell you if a feed is not arriving before you read anything into the rest.
Included in Max and Enterprise. $250 a month on Pro and Ultra
Take the plan that includes it, or add it to the one you have.
One HyperShreds destination is $250/mo. Max and Enterprise include it.
Pro
$49/moHyperShreds stands on its own: it does not need Ultra.
$299/moplan + $250 add-onUltra
$199/moKeep your Shredstream destination and add a HyperShreds one. They are separate allowances.
$449/moplan + $250 add-onMax
$300/moHyperShreds included. 1 HyperShreds destination, plus HyperStreams and higher limits than Ultra.
$300/moplan, includes HyperShredsEnterprise
$500/moHyperShreds included. 2 HyperShreds destinations, a dedicated cluster and a committed SLA.
$500/moplan, includes HyperShreds
$149/moless on Max than Ultra plus HyperShreds, and Max also includes HyperStreams and higher limits than Ultra.
Start receiving HyperShreds in four steps
- 1
Get HyperShreds
Take Max or Enterprise, or add HyperShreds to Pro or Ultra for $250 a month.
- 2
Register a destination
Enter a public IPv4 address and a UDP port in the dashboard, or call the API with class hypershreds.
- 3
Verify it
We send one SHREDCAST-VERIFY packet. Paste its token back to prove the address is yours.
- 4
Receive
Packets start arriving. Check them with tcpdump, then point your deshredder at the port.
Add and verify a destination with your API key
# add a destination (class: shreds or hypershreds)curl -s -X POST https://shreds.mainnet.solana.nolimitnodes.com/v1/shreds/destinations \ -H "x-api-key: $NLN_API_KEY" \ -H "content-type: application/json" \ -d '{"class": "hypershreds", "ip": "203.0.113.10", "port": 20000, "label": "trading box"}'
# on the receiving machine, read the SHREDCAST-VERIFY packetnc -u -l 20000
# send the token backcurl -s -X POST https://shreds.mainnet.solana.nolimitnodes.com/v1/shreds/destinations/$ID/verify \ -H "x-api-key: $NLN_API_KEY" \ -H "content-type: application/json" \ -d '{"token": "<token from the packet>"}'Open the port, then watch the packets
# open the UDP port (replace 20000 with yours)sudo ufw allow 20000/udp
# start capturing before you save the destinationsudo tcpdump -n -i any "udp and dst port 20000"Full guides: dashboard setup, the destinations API and firewall setup.
HyperShreds: questions
Not here? Email [email protected] or talk to sales.
What is HyperShreds?
HyperShreds is NoLimitNodes’ premium Solana shred feed. A shred is one of the small packets a block is split into as the leader sends it out. HyperShreds delivers raw data and coding shreds over UDP to an IPv4 address and port you control, through our ultra-low-latency fanout. It costs $250 a month per destination, and Max and Enterprise include it.
How is HyperShreds different from Shredstream?
Both deliver raw, Jito-compatible shreds over UDP to a destination you register. Shredstream uses our standard delivery, and HyperShreds delivers the same shreds on our lower-latency delivery. They are separate products with separate allowances, so one account can hold both.
Where do HyperShreds shreds come from?
We buy shreds from the most expensive providers and deliver them to you through our own ultra-low-latency fanout. We do not name the providers. Bought one at a time, such feeds cost thousands of dollars a month, and we share that cost across our customers.
Why do good shred feeds cost thousands of dollars a month?
Providers price the earliest shreds for trading firms, for whom seeing a block sooner is worth real money, and that puts the feeds out of reach for most developers. HyperShreds exists to close that gap: we buy the feeds and fan them out, and one destination costs $250 a month.
How much does HyperShreds cost?
$250 a month per destination, or $2,500 a year with two months free. Max ($300 a month) includes one destination and Enterprise ($500 a month) includes two. On Pro and Ultra you add it for $250 a month.
Is HyperShreds the same as buying a feed directly?
No. You receive the shreds through our fanout, not over a direct connection to the provider, so we cannot promise the latency of a private line. What you get is premium shreds for $250 a month instead of thousands. Run the receiver on this page against both feeds and compare them on your own server.
What is FEC completeness?
Solana splits each block into FEC sets: data shreds plus the coding shreds that protect them. A set rebuilds only when you hold at least as many of its shreds as it has data shreds. A feed is FEC-complete when it delivers enough of every set. If it does not, part of the block stays incomplete on your side even though the feed was running.
Do I need more than one premium shred feed?
In some cases, yes. Many premium feeds are built and priced on the assumption that you also subscribe to others, so one feed on its own may not give you enough of every FEC set. Combining feeds yourself multiplies the bill and leaves the merging to you. HyperShreds draws on several premium feeds and delivers them to one destination for $250 a month.
How can I check whether a feed is FEC-complete?
Run fec_check.py, shown on this page, on the server you trade from. It listens on one port per feed and reports, for each feed and for both together, how many FEC sets were complete, recoverable from the coding shreds, incomplete, or of unknown size.
What latency should I expect?
We do not publish a single number, because latency depends on where your server sits and the route to it. Measure it yourself: the script on this page prints which of two feeds delivered each shred first, from your own machine.
What format are the shreds in?
Raw Solana mainnet data and coding shreds in a Jito-compatible wire format, sent as UDP packets. Your receiver must deshred them into entries, drop duplicates and handle gaps and forks. Raw shreds carry no logs, balances, errors or commitment level.
Do I need Jito’s software to receive them?
No. The wire format is Jito-compatible, so a receiver built for that path works, and so does one you write yourself. You need a public IPv4 address, an open UDP port and a receiver that deshreds.
Does HyperShreds need an Ultra plan?
No. HyperShreds is its own product with its own allowance. You can add it to Pro, Ultra, Max or Enterprise, and Max and Enterprise include it.
Can I use HyperShreds with UltraSend or Yellowstone gRPC?
Yes. Use HyperShreds to see a block early, Yellowstone gRPC to confirm what happened with logs, balances and commitment, and UltraSend to send the transaction. They are separate products you can combine.
How do I start?
Take Max or Enterprise, or add HyperShreds to Pro or Ultra for $250 a month. Then register a public IPv4 address and UDP port in the dashboard or with the API, paste back the SHREDCAST-VERIFY token to prove you control it, and packets start arriving.
$250 a month. Included in Max.
Premium shreds without the premium bill. $2,500 a year if you pay yearly.
Questions first? Email [email protected] or talk to sales.