Skip to content

Accountability with blinded routes#6

Closed
thomash-acinq wants to merge 6 commits intocarlaKC:outgoing-reputationfrom
thomash-acinq:accountability
Closed

Accountability with blinded routes#6
thomash-acinq wants to merge 6 commits intocarlaKC:outgoing-reputationfrom
thomash-acinq:accountability

Conversation

@thomash-acinq
Copy link

Blinded routes do not allow the sender to send custom payloads to nodes inside a blinded route (https://github.com/lightning/bolts/blob/master/04-onion-routing.md?plain=1#L315), instead all the payload data is chosen by the recipient and is put inside encrypted_recipient_data. For this reason, when using blinded routes, the upgrade_accountability must be set by the recipient inside encrypted_recipient_data and not in the payload by the sender.

carlaKC and others added 6 commits October 6, 2025 12:44
Once we have a signal from the recipient, we need a way to propagate
this information throughout the route. Including a signal in the onion
provides an uncorruptable way for the sender to propagate this signal.
If the sender is dishonest, this will eventually be detected by the
final recipient.

In the commits that follow we'll add reputation and resource management
that will allow nodes to use this signal to protect against jamming
attacks.
Follow naming convention by prefixing invoice fields with "invoice_".
@carlaKC
Copy link
Owner

carlaKC commented Jan 7, 2026

Upstreamed to the BOLT PR - thanks again!!

@carlaKC carlaKC closed this Jan 7, 2026
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.

2 participants