Fast start
Catch-up shreds
LiveTestnet
Restart and catch up in minutes: the slots since your snapshot, from Pipe's stored shreds, streamed into your validator's TVU by the pipe-shred-feeder tool, every shred checked against a signed manifest and its leader's signature first.
Included in: Fast start.
Each range manifest is signed by the service’s own key, listed in /attest/keys.json; the feeder checks every shred against it.
Endpoints
Served from http://186.233.184.235:8080. Send a key as Authorization: Bearer psol_…. Indexes and status files need no key.
/shred-range/status.json/shred-range/stream?from=<slot>&follow=1/shred-range/manifest/<bucket>.json
curl -fsS "http://186.233.184.235:8080/shred-range/status.json"
pipe-shred-feeder --rpc http://127.0.0.1:8899 --api-key-file ~/.config/pipe/api-keyTestnet
Free without a key under http://186.233.184.235:8080/testnet; testnet never counts against a plan or mainnet’s free tier. On its gated paths a key sent anyway is checked and served at testnet’s free limits, never charged; an unknown or revoked key gets 401.
/testnet/shred-range/status.jsonungated/testnet/shred-range/stream?from=<slot>&follow=1tn_feeds/testnet/shred-range/manifest/<bucket>.jsontn_feeds
tn_feeds(Testnet shreds): 10 requests a second, bursts of 20; 5 MiB/s per connection, without a key- The paths marked ungated answer with no testnet group’s limits.
- Its testnet statements are signed by testnet keys, listed in
/testnet/attest/keys.json; never check them against mainnet’s/attest/keys.json.
Access and limits
shred_range: Catch-up shreds: the range stream, its signed manifests and the caller's usage. Heavy (a slot is about 0.6 MB of data shreds; a catch-up reads every slot since the snapshot), so a group of its own, two connections per key.
| Plan | shred_range | Data a month |
|---|---|---|
| Fast start | 10 requests a second, bursts of 20; 64 MiB/s per connection | 2 TB per key |
Limits apply to each key; the free tier’s apply to each address. Prices for each plan are on the plans page.