Skip to content

Carrier: move to iroh 1.4 with its own network acceptance (step 1 of #345) #570

Open

Description

@andersalm

Decision (Anders, 20 Oct, #345). The Runtime moves to iroh 1.4 before #345 or draft PR #354 switches on any relay. The upgrade gets its own network acceptance first.

Today. 2.0.1 pins iroh 1.0.2 and iroh-gossip 0.101.0 (elastos/Cargo.lock at v2.0.1). Current releases are iroh 1.4.1 and iroh-gossip 0.102.0 (crates.io, 11 Nov).

Version decision (Main, 12 Nov). iroh moves to 1.4.1 first, with iroh-gossip at 0.101. Then distributed-topic-tracker is removed: Homes and Community already use iroh-gossip directly. The library only wraps sending with timeouts (carrier.rs:1341, replaced by a few lines of our own), and its DHT discovery serves only the hidden developer command elastos chat, which joins through the Community node like everything else or is retired. iroh-gossip then moves to 0.102, which brings send-queue, rejoin and lost-join fixes. No fork and no upstream PR.

Scope. Upgrade iroh, iroh-gossip and iroh-dns in the Runtime and every capsule lockfile that carries them. Production Carrier stays direct-only in this step; nothing a person sees changes. This is the first of the three steps in #345.

Done means

  • One iroh version across all lockfiles, listed per lockfile in the PR.
  • Community posts, direct messages on one network, and an update fetched over Carrier all pass on installed Homes (Mac and Linux).
  • The existing installed update journeys pass in CI.
  • cargo audit clean. Coordinate with the hickory-proto bump, since iroh-dns brings it in.
  • Review by a different model family from the writer, plus Irzhy for Carrier.

Acceptance (Main, 13 Nov; develop 82880c8da, after #585 and #587)

Activity

  1. added this to the 2.0.2 milestone on Nov 11, 2026
  2. andersalm commented on Nov 12, 2026

    @andersalm
    ContributorAuthor

    Round 2 stopped at the required local disk reserve before the remaining lockfile and verification work could run.
    Runtime lock resolves iroh 1.4.1 with gossip 0.101.0 and tracker 0.3.5; the local candidate remains incomplete.
    Next owner: Main restores disk reserve; the dependency lane then finishes both graphs and the required gates.

  3. andersalm commented on Nov 12, 2026

    @andersalm
    ContributorAuthor

    Blocker: the Mac disk reserve stopped the object-provider test build and its queued retry. Its three tests still need to run.
    Next owner: Main restores the reserve; the #570 lane integrates current develop and runs the remaining tests.

  4. andersalm commented on Nov 12, 2026

    @andersalm
    ContributorAuthor

    Root's fresh read-only disk check is above the required 10% reserve. The three previously refused object-provider tests still need completed results; this sample establishes disk space only.

  5. added a commit that references this issue on Nov 13, 2026
  6. andersalm commented on Nov 13, 2026

    @andersalm
    ContributorAuthor

    Root checked #598’s completed mixed-version receipts: all four released/candidate arrangements passed on Linux x86-64 on one host, with 56 distinct fresh texts across start, node restart, fresh join and member restart; cleanup receipts passed.
    This extends compatibility proof at #598’s checked candidate. Mac/ARM mixed-version and real-network coverage remain open; #599’s later receipt/retry change keeps its own installed acceptance.
    #570’s remaining review record stays with Main’s ordered queue: #585 Carrier review and the different-family verdicts. #410’s consent/history journey and #409’s replay/Undo acceptance remain separate.

  7. added 2 commits that reference this issue on Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions