Skip to content

[snrc resolver] report expiry and availability correctly - #1861

Open
brenzi wants to merge 6 commits into
ab/resolver-labelhash-queryfrom
ab/snrc-resolver-expiry-and-availability
Open

[snrc resolver] report expiry and availability correctly#1861
brenzi wants to merge 6 commits into
ab/resolver-labelhash-queryfrom
ab/snrc-resolver-expiry-and-availability

Conversation

@brenzi

@brenzi brenzi commented Sep 3, 2026

Copy link
Copy Markdown
Collaborator

Problem with #1860 alone: It prepares the resolver to be used to query availability of names without revealing them, but the response can be misleading because we don't handle expiry and reserved status meaningfully.

  • An expired name beyond its grace period would still resolve although it is actually available again.
  • Reserved names would show as available although they aren't
  • taken-but-resolverless name 404s identically to a free one

This PR fixes the problems above

  • report expiry and reserved status (preparing for reporting a specific reason)
  • introduce meaningful http error codes and handle them in Names.hs

@brenzi brenzi changed the title report expiry and availability correctly [snrc resolver] report expiry and availability correctly Sep 3, 2026
@brenzi
brenzi force-pushed the ab/snrc-resolver-expiry-and-availability branch from 4b5c7bc to e4e3d0d Compare September 4, 2026 06:51
@brenzi
brenzi marked this pull request as ready for review September 4, 2026 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant