-
Notifications
You must be signed in to change notification settings - Fork 7
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
NIP-05: bob@trustroots.org #4
Comments
I'd like to try to set up a NIP-05 team@trustroots.org for this npub https://primal.net/p/npub1lt6a968lk4h6yqduqnxcha628cudulgy8xk607c4xyxn6d6w6kcsmgp8hj I used https://nostrtool.com/ to get the hex code: faf5d2e8ffb56fa201bc04cd8bf74a3e38de7d0439ada7fb15310d3d374ed5b1 Now if we put a static file containing |
Maybe returning the same npub for Maybe for the collective we could try to add a profile field for npub. Then we could add an API endpoint that resolves usernames into npubs and returns the appropriate JSON. Seems like quite a small change to the current codebase, but would open up nip05 options. Would lay the groundwork for simple trust verifications and so on. |
there's progress.. continue at Trustroots/trustroots#2692 |
Seems easy to implement early 2024:
npub field on user profile, which is not displayed initially"names": { "bob": "b0635d6a9851d3aed0cd6c495b282167acf761729078d975fc341b22650b07b9" } }
UPDATE: better provide nsecs for everyone right away
probably add another section here, replace ELSEWHERE with NOSTR:
(and NOSTR can even link to a page with apps that can use this)
The text was updated successfully, but these errors were encountered: