fshy

Home / Storage

hyperswarm / hyperdht blind relay as free bulk infrastructure

deepwiki.com/holepunchto/hyperdht/3.5-connection-relayingstorage/hyperswarm-hyperdht-blind-relay-as-free-bulk-infrastructJSONcomparereport an errorprovider JSON

Free allowance
Blind relay exists — any willing peer forwards ciphertext when both sides are behind randomized NAT — but there is no operated free relay fleet to draw on; relayThrough is something you…
Verdict
self-hosted, last resortverdict fails-quota: the free allowance is too small to matter. Self-hosted options are listed last, because this site is for users who have no hardware.
Cost
not stated
Identity
email?placeholder, not evidence; card unknown, phone unknown
Binding limit
noneno named constraint binds
Evidence
reported3 sources; a third party said so
Freshness
stale on 2026-11-05checked 2026-10-21 (inherited); stale on 2026-11-05
Free tierBlind relay exists — any willing peer forwards ciphertext when both sides are behind randomized NAT — but there is no operated free relay fleet to draw on; relayThrough is something you…
unit none; metered on none
Pricenone stated
Identityemail (placeholder) not published
Egressnot recorded
Interfaceunknown
Toolingnot recorded
Evidence 3
datesourcewhat it proved
2026-10-21deepwiki.com/holepunchto/hyperdht/3.5-connection-relayingthe text of Free tier, above
2026-10-21github.com/holepunchto/hyperswarm-dht-relaycited as the basis of the rejection: Blind relay exists — any willing peer forwards ciphertext when both sides are behind randomized NAT — but there is no operated free relay fleet to draw on; relayThrough is something you su
2026-10-21docs.pears.com/reference/building-blocks/hyperswarm/cited as the basis of the rejection: Blind relay exists — any willing peer forwards ciphertext when both sides are behind randomized NAT — but there is no operated free relay fleet to draw on; relayThrough is something you su
More fields 1
dead end{"failure_class": "quota","why": "Blind relay exists — any willing peer forwards ciphertext when both sides are behind randomized NAT — but there is no operated free relay fleet to draw on; `relayThrough` is something you…","retry_when": null,"first_recorded": "2026-10-21"}
Unknown values 7
  • chaining: no value was recorded for this field
  • egress terms: no value was recorded for this field
  • interface: the access interface was not established
  • per object cap notes: no value was recorded for this field
  • per object cap stated: no value was recorded for this field
  • retention stated: no value was recorded for this field
  • tooling: no value was recorded for this field