feat: WIP allow non-ed keys in EndpointID

[rklaehn]

Description

This is the latest attempt that leaves more internals alone.

Replaces #3576

The basic approach is to first replace the EndpointId type alias with PublicKey everywhere and then reintroduce EndpointId as a new type only in public APIs. The entire relay crate, despite being public, still works with PublicKey.

Every place where we have a PublicKey and need an EndpointId on the outside we can just use .into(). In tests it is Ok to go from EndpointId to PublicKey using .expect_ed().

Discovery works with EndpointId, but discovery services that fundamentally require ed keys, such as pkarr, will just do nothing for non ed keys.

Todo:

• tickets need a new version which has a variant identifier for the key
• tostring/parse roundtrip
• check public iroh api for remaining PublicKey
• bikeshed how the tostring for an EndpointId should look like
• remove or change Endpoint::secret_key

Todo (later?):

• change encoding for mdns to be able to encode an actual endpoint id, not just a public key

The relay protocol of course remains fully based on ed keys. Changing that to support different keys would be a major effort, but with multipath we might be able to just add a second one using whatever new keys we support.

Breaking Changes

Notes & open questions

Change checklist

• Self-review.
• Documentation updates following the style guide, if relevant.
• Tests if relevant.
• All breaking changes documented.
  • List all breaking changes in the above "Breaking Changes" section.
  • Open an issue or PR on any number0 repos that are affected by this breaking change. Give guidance on how the updates should be handled or do the actual updates themselves. The major ones are:
    • quic-rpc
    • iroh-gossip
    • iroh-blobs
    • dumbpipe
    • sendme

[github-actions]

Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3653/docs/iroh/

Last updated: 2025-11-13T16:32:56Z