You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Implement PendingHTLCsRelayable Event to split acceptance/relay checks #680
Currently, we apply both BOLT-2 incoming channels settings checks and BOLT-4 relay checks at update_add_htlc reception. We should split relay checks and get incoming HTLC acceptance generate a Event::PendingHTLCsRelayable. This event could be consumed by process_pending_htlc_relayable and should generate a PendingHTLCsForwardable. In between any kind of client custom function can be implemented support for stricter relay policy, on-the-flight generated outgoing zero-conf channel, delayed relay, trampoline-style of routing, ...
Activity
TheBlueMatt commentedon Aug 28, 2020
This could also allow live-rebalancing on the client's end, which would be cool.
ariard commentedon Sep 8, 2020
Also fix current bug : #633 (comment)
TheBlueMatt commentedon Nov 12, 2020
Note that the bug at #633 (comment) has been fixed in #690.
ariard commentedon Jul 5, 2021
Might serve to address few timing attacks : #975 (comment)
ariard commentedon Jul 5, 2021
Might serve as iptables for routing nodes : #975 (comment)
ariard commentedon Oct 19, 2021
Maybe also addressing that at the same time : #1119 (comment)
TheBlueMatt commentedon Feb 16, 2022
May need to rely on #1302
TheBlueMatt commentedon Aug 22, 2022
Turns out we're not gonna rely on this for #1302, so there's no reason for this to have a very-soon milestone.
TheBlueMatt commentedon Jul 7, 2025
Enabled by the work in #1302.