To help answer “what still needs to happen before the network can rely on Happy Families (and eventually stop depending on MyFamily)?”, we put together a small public dashboard that tracks the main rollout gates: https://metrics.1aeo.com/network-health.html#happy-families High-level flow: 1) Voting directory authorities upgrade (v0.4.9.x+) DAs need to be on v0.4.9.x+ so the network can move forward with the newer directory protocol pieces. 2) Consensus method moves to 35 Once a >2/3 voting DA majority supports method 35 (7/9), the consensus can adopt it. 3) Relays publish Happy Families material Relay families configure FamilyId so relays publish family-cert, which lets directory documents/micro descriptors carry the happy families identifier information. 4) Clients upgrade and use it As Tor clients (Tor Browser, tor, etc.) widely consume happy families identifiers, then deprecating MyFamily becomes possible. The dashboard shows live counts for DA readiness (v0.4.9.x+ and method-35 support), current consensus method, relay publication (family-cert), and a few “how much of the network is ready” slices (guards/exits/CW/bandwidth). References: - Relay operator guide (FamilyId / Happy Families setup): https://community.torproject.org/relay/setup/post-install/family-ids/ - Proposal 321: https://spec.torproject.org/proposals/321-happy-families.html Feedback welcome—especially if there are other readiness signals you’d like to track, or if you spot anything that looks off for your relays. On Tuesday, February 3rd, 2026 at 5:00 AM, Alexander Hansen Færøy via tor-relays <tor-relays@lists.torproject.org> wrote:
On 02/02/2026 22.36, tor_appliedprivacy.net via tor-relays wrote:
Today we enabled the happy family setup across all our relays.
Since all our relays run in a single /24 we also removed MyFamily at the same time. This should help reduce the overhead introduced by MyFamily.
This is not what any of us on the Network Team are recommending right now, but if others think this is a good idea despite that: please ensure that your IPv6 addresses, at the very least, are also within the same /32 in addition to the /16 requirement for IPv4. I am almost certain that is always the case, but please just be sure before you proceed.
We are very interested in hearing feedback on the 0.4.9.4-rc release candidate and in resolving any issues before we stabilize 0.4.9. Maybe the above approach will reveal some issues :-)
Cheers, Alex
-- Alexander Hansen Færøy _______________________________________________ tor-relays mailing list -- tor-relays@lists.torproject.org To unsubscribe send an email to tor-relays-leave@lists.torproject.org
