-
Notifications
You must be signed in to change notification settings - Fork 2.2k
docs: add a new category of docs -> databases to explain sphinx replay #9616
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
Open
shivansh-bhatnagar18
wants to merge
1
commit into
lightningnetwork:master
Choose a base branch
from
shivansh-bhatnagar18:documentSphinxReplay
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Understanding Sphinx Replay Protection | ||
|
||
Sphinx is a protocol enabling anonymous and untraceable messaging in networks, commonly used in Lightning's onion routing. To prevent replay attacks, a Sphinx replay database stores message hashes along with metadata (e.g., timestamp, sender ID). | ||
|
||
## How It Works | ||
1. **Message Check**: When a message is received, its hash is compared against stored entries. | ||
2. **Replay Prevention**: If the message exists, it is discarded; otherwise, it is added to the database. | ||
3. **Network Integrity**: This ensures that previously sent messages cannot be resent maliciously. | ||
|
||
## Onion Routing in Lightning | ||
Sphinx follows source-based onion routing, where messages are encrypted in nested layers. Each node peels one layer, revealing only the next hop, ensuring sender anonymity and path secrecy. | ||
|
||
Lightning’s **Sphinx Mix Format** differs from Tor, offering enhanced security tailored to payments. | ||
|
||
For deeper insights, refer to [Chapter 10 of the Lightning Network Book](https://github.com/lnbook/lnbook/blob/develop/10_onion_routing.asciidoc). | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you wrap the lines at 80 characters please?