This is a fork, and it carries no functional change.
It exists to repoint five dependency lines —
iroh,iroh-base,iroh-dnsin the two member manifests — from crates.io atagent-habilis/iroh. Nothing else differs from upstreamn0-computer/iroh-address-lookups, and nothing here is upstreamable: n0 will never point their crates at our fork.Why it has to exist. These two crates sit between
habilis-networkand iroh. habilis-network needs a forked iroh (relay-teardown and mapped-addrs fixes); these named the crates.io one, so every graph containing both got two irohs, and theAddressLookupimpls stopped satisfying the trait the forkedEndpointhands back — anE0308on types that look identical. A dependency declaration cannot redirect a third party's edge; only[patch.crates-io]can, and cargo honours that only in a workspace root and never inherits it. So the alternative was every consumer of habilis-network restating the same three patch lines by hand, silently broken the moment one drifted.Delete this fork the moment the underlying iroh patches land upstream and habilis-network can name the published crates again.
Optional Address Lookup services for iroh.
iroh-mainline-address-lookup— pkarr-based publish/lookup over the BitTorrent Mainline DHT.iroh-mdns-address-lookup— mDNS-based discovery for endpoints on the local network.
Copyright 2025 N0, INC.
This project is licensed under either of
- Apache License, Version 2.0, (LICENSE-APACHE or http://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or http://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this project by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.