Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NUT-06: Mint should announce multiple endpoints that it is reachable from #62

Open
callebtc opened this issue Nov 11, 2023 · 2 comments

Comments

@callebtc
Copy link
Contributor

Mint should announce https / Tor addresses in the info response at which it is reachable from.

@Egge21M
Copy link
Contributor

Egge21M commented Jun 24, 2024

Can we use nostr-protocol/nips#1110 as a way for a mint to announce changes to their npub?

  1. Client connects to mint
  2. Clients retrieves nostr pubkey from /info
  3. Client periodically checks the pubkey on nostr for updates

@callebtc
Copy link
Contributor Author

Can we use nostr-protocol/nips#1110 as a way for a mint to announce changes to their npub?

  1. Client connects to mint
  2. Clients retrieves nostr pubkey from /info
  3. Client periodically checks the pubkey on nostr for updates

That sounds like a good idea but I think it would be an overkill right now. If we go further down the nostr route, the mint should probably announce a lot more than just the mint URLs (whole info endpoint for example, and keys etc). Since the chance of your DNS getting rugged is really small, I wouldn't consider this a pressing issue right now though.

@thesimplekid thesimplekid changed the title NUT-09: Mint should announce multiple endpoints that it is reachable from NUT-06: Mint should announce multiple endpoints that it is reachable from Jun 26, 2024
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

No branches or pull requests

2 participants