[relay-hops] Extensibility of HOP_PATH characteristics/traits

[afrind]

In the current rev, the only metric that is conveyed is the number / topology of the hops. It would be significantly more interesting if the hop-path contained an extensible struct or hop characteristics, eg:

TRAIT {
  Type (vi64),
  Value (vi64)
}

HOP {
  ID (vi64)
  Number of Traits (vi64)
  [Trait (..) ...]
}

HOP_PATH {
  Length (vi64),
  Hop (..) ...
}

Example Traits could be latency, cost ($) or a synthetic metric computed via logic specific to the network's deployment. You could start with a simple IANA registry in your doc of common traits, and define an app specific range that can be used without registration.

[coderabbitai]

🔗 Related PRs

#48 - moq-relay-hops: carry HOP_PATH on NAMESPACE via an extended Parameters field [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!