Skip to content

[relay] Support uncached resolve #161

@SeverinAlexB

Description

@SeverinAlexB

GCP and AWS are having issues communicating with the Mainline DHT. To get around this, all pkarr traffic could be redirected via relay in a different cloud.

Currently, the relay only supports cached resolve queries. resolve_most_recent() is not supported but is an important part of the client.
For republishing, the homeserver is dependent on resolving the users current packet with resolve_most_resent(). CAS will prevent the publishing of older packets but the republishing would still not succeed.

Adding an uncached resolve to the relay is obviously a more expensive operation. I see two ways to accomplish this:

  • Extend the config.toml so one can disable the cache. Practically, this relay would likely need to be gatekept from public access.
  • Add an option to the relay for uncached queries. This would need to be added cleverly to keep ensure compatibility with old pkarr clients + one needs to think about how to rate limit this api separately.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions