WIP: nostr node validation #525
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
heyhowareya @apotdevin |
|
Hey! Woah - deep integration and an interesting idea! Will check and come back with some comments |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a WIP from the Satsby hackaton project Auntie LN.
Auntie LN adds a Nostr tab to ThunderHub. The Nostr tabs creates (or imports) a nostr to create a validated Lightning node. Nodes are validated by signing a message from the node with the messaging being the npub of the nostr account. An event is created (kind 80081) as a node attestation. The Nostr service then follows all lightning peers that have broadcasted a node attestation.
The inspiration for the project is an uncensoreable, verifiable communication service for nodes.
This PR is marked as WIP for code review that we are following the standards of Thunderhub.