Iroh 1.0 - Dial Keys, not IPs
Iroh 1.0 is out. Now is the time to build.
all things iroh & development
A closer look at QUIC NEW_TOKEN tokens, why they exist, and what they buy you in iroh and noq.
Release of iroh v1.0.0-rc.1, the last release candidate before 1.0
Putting QUIC packet rejection to the test with a real iroh endpoint.
How Paycode used iroh to connect payment terminals to point of sale systems at highway toll booths, with no additional servers and full compliance.
Iroh and Media over QUIC are changing the game for video streaming
A look at how QUIC allows efficient rejection of invalid packets before they waste resources.
We combine the privacy of Tor onion services with the performance of Iroh via a custom transport.
Release of iroh v0.95
Read about iroh's approach to error handling
Walk through an example using message framing to create a protocol on iroh.
Learn about the new features in the new blobs API
Introducing the Canary Series of releases leading up to 1.0
It's just hashed data, what's so complex about a blob store anyway?
We are committing to releasing iroh 1.0 in the second half of 2025
FROST threshold signatures - or how to keep your private keys safe even if a device gets lost or compromised
In the upcoming v0.26.0 release, We're doubling down on iroh's networking stack as “what iroh is”, describing everything else as a custom protocol
Closing a QUIC connection without losing any data, using the Quinn API.
Documenting some painful lessons we learned while writing iroh using async Rust
How to discover iroh nodes by node id, using the Mainline Distributed Hash Table (DHT)
Describes the process that iroh-net uses to heal a connection after one side has changed networks or IP addresses.
iroh-dns uses domain name servers to resolve dialing details, so you can dial any device by its node identifier
How to discover iroh nodes by node id, using the Mainline Distributed Hash Table (DHT)
Thus far, Iroh has been built as an implementation of the InterPlanetary File System (IPFS) focused on interoperability with Kubo, the reference implementation of IPFS. In the near future Iroh will break interoperability with Kubo, with the goal of moving the IPFS project forward.