{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":501020958,"defaultBranch":"main","name":"rust-lightning","ownerLogin":"wpaulino","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2022-06-07T22:18:17.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/9447167?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1726302328.0","currentOid":""},"activityList":{"items":[{"before":"05628300e89987461bd386e5ea9adea35496c43e","after":"183fd66497ff439a3eac2b47c033a8c9fa34d2b5","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-09-21T19:50:45.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"d9fd8f1e2f45d09f218176e2c6202ef0ff90ea69","after":null,"ref":"refs/heads/closing-signed-monitor-update","pushedAt":"2024-09-14T08:25:28.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"}},{"before":"9a66e878eab0774ac302ef2add599638dd298224","after":null,"ref":"refs/heads/bump-fees-conservatively","pushedAt":"2024-09-14T08:25:27.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"}},{"before":"6d458656ffc015ef2cf5f14f555949601b399d4d","after":null,"ref":"refs/heads/bump-tx-event-handler-weight-estimate-tests","pushedAt":"2024-09-14T08:25:25.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"}},{"before":"ceb0dec26a3029b7bce7ce9875aec4c25e434a08","after":"8b76adfa2afc4c5fdf6607bdf6900d6d6e9ceb85","ref":"refs/heads/quiescence","pushedAt":"2024-09-14T08:21:36.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Add fuzzing coverage for quiescence","shortMessageHtmlLink":"Add fuzzing coverage for quiescence"}},{"before":"bcdf60e197e51ae07faca9ae5bd4ff976c6259ce","after":"05628300e89987461bd386e5ea9adea35496c43e","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-09-12T19:56:07.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"574554b273143320c3730f4e04c32fdccc076cc6","after":"bcdf60e197e51ae07faca9ae5bd4ff976c6259ce","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-09-06T20:50:57.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"af3558d7f2cdc5c5a12de807dec5c1432ca71a1a","after":"ceb0dec26a3029b7bce7ce9875aec4c25e434a08","ref":"refs/heads/quiescence","pushedAt":"2024-09-06T20:06:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Add fuzzing coverage for quiescence","shortMessageHtmlLink":"Add fuzzing coverage for quiescence"}},{"before":"5c89d019050a4b2dd68610d2e59d45acbfee5775","after":"a76ec06d23801191f12688245584e12057bd3b10","ref":"refs/heads/main","pushedAt":"2024-07-28T08:06:03.000Z","pushType":"push","commitsCount":2321,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Merge pull request #3203 from lexe-app/pr/description-as-inner\n\nlightning-invoice: Add `Description::as_inner`","shortMessageHtmlLink":"Merge pull request lightningdevkit#3203 from lexe-app/pr/description-…"}},{"before":"11c18ec7cfd6df546c517482f050db55d87b2047","after":"574554b273143320c3730f4e04c32fdccc076cc6","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-05-18T05:23:17.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"b835e4f67af1689ab541c1b3ea26cc3a5b643374","after":null,"ref":"refs/heads/handshake-complete-timer-tick-occurred-race","pushedAt":"2024-04-15T21:47:21.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"}},{"before":"f381e41768089422bb68a13b79a3d56f11bd52ff","after":"b835e4f67af1689ab541c1b3ea26cc3a5b643374","ref":"refs/heads/handshake-complete-timer-tick-occurred-race","pushedAt":"2024-04-12T17:57:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Fix race between handshake_complete and timer_tick_occurred\n\nThe initial noise handshake on connection establishment must complete\nwithin a single timer tick. This timeout is enforced via\n`awaiting_pong_timer_tick_intervals` whenever a timer tick fires while\nour handshake has yet to complete. Currently, on an inbound connection,\nif a timer tick fires after we've sent act two of the noise handshake\nalong with our init message and before receiving the counterparty's init\nmessage, we begin enforcing such timeout. Even if we immediately\ncontinue to process the counterparty's init message to complete to\nhandshake, the timeout enforcement is not cleared. With the handshake\ncomplete, `awaiting_pong_timer_tick_intervals` is now tracked to enforce\na pong timeout, except a ping was never actually sent. If a single timer\ntick fires again without having received a message from the peer, or\nenough timer ticks fire to trigger the\n`MAX_BUFFER_DRAIN_TICK_INTERVALS_PER_PEER` logic, we'll end up\ndisconnecting the peer due to a timeout for a pong we'll never receive.\n\nWe fix this by always resetting `awaiting_pong_timer_tick_intervals`\nupon processing our counterparty's init message.","shortMessageHtmlLink":"Fix race between handshake_complete and timer_tick_occurred"}},{"before":"f27708645d793c539474d3ec8d2bc6e78f0e9cc2","after":"f381e41768089422bb68a13b79a3d56f11bd52ff","ref":"refs/heads/handshake-complete-timer-tick-occurred-race","pushedAt":"2024-04-12T17:48:43.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Fix race between handshake_complete and timer_tick_occurred\n\nThe initial noise handshake on connection establishment must complete\nwithin a single timer tick. This timeout is enforced via\n`awaiting_pong_timer_tick_intervals` whenever a timer tick fires while\nour handshake has yet to complete. Currently, on an inbound connection,\nif a timer tick fires after we've sent act two of the noise handshake\nalong with our init message and before receiving the counterparty's init\nmessage, we begin enforcing such timeout. Even if we immediately\ncontinue to process the counterparty's init message to complete to\nhandshake, the timeout enforcement is not cleared. With the handshake\ncomplete, `awaiting_pong_timer_tick_intervals` is now tracked to enforce\na pong timeout, except a ping was never actually sent. If a single timer\ntick fires again without having received a message from the peer, or\nenough timer ticks fire to trigger the\n`MAX_BUFFER_DRAIN_TICK_INTERVALS_PER_PEER` logic, we'll end up\ndisconnecting the peer due to a timeout for a pong we'll never receive.\n\nWe fix this by always resetting `awaiting_pong_timer_tick_intervals`\nupon processing our counterparty's init message.","shortMessageHtmlLink":"Fix race between handshake_complete and timer_tick_occurred"}},{"before":"ef0b355bc3a21c0d1484fef5b7fded7c09a238c1","after":"f27708645d793c539474d3ec8d2bc6e78f0e9cc2","ref":"refs/heads/handshake-complete-timer-tick-occurred-race","pushedAt":"2024-04-12T17:46:21.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Fix race between handshake_complete and timer_tick_occurred\n\nThe initial noise handshake on connection establishment must complete\nwithin a single timer tick. This timeout is enforced via\n`awaiting_pong_timer_tick_intervals` whenever a timer tick fires while\nour handshake has yet to complete. Currently, on an inbound connection,\nif a timer tick fires after we've sent act two of the noise handshake\nalong with our init message and before receiving the counterparty's init\nmessage, we begin enforcing such timeout. Even if we immediately\ncontinue to process the counterparty's init message to complete to\nhandshake, the timeout enforcement is not cleared. With the handshake\ncomplete, `awaiting_pong_timer_tick_intervals` is now tracked to enforce\na pong timeout, except a ping was never actually sent. If a single timer\ntick fires again without having received a message from the peer, or\nenough timer ticks fire to trigger the\n`MAX_BUFFER_DRAIN_TICK_INTERVALS_PER_PEER` logic, we'll end up\ndisconnecting the peer due to a timeout for a pong we'll never receive.\n\nWe fix this by always resetting `awaiting_pong_timer_tick_intervals`\nupon processing our counterparty's init message.","shortMessageHtmlLink":"Fix race between handshake_complete and timer_tick_occurred"}},{"before":null,"after":"ef0b355bc3a21c0d1484fef5b7fded7c09a238c1","ref":"refs/heads/handshake-complete-timer-tick-occurred-race","pushedAt":"2024-04-12T17:42:11.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Fix race between handshake_complete and timer_tick_occurred\n\nThe initial noise handshake on connection establishment must complete\nwithin a single timer tick. This timeout is enforced via\n`awaiting_pong_timer_tick_intervals` whenever a timer tick fires while\nour handshake has yet to complete. Currently, on an inbound connection,\nif a timer tick fires after we've sent act two of the noise handshake\nalong with our init message and before receiving the counterparty's init\nmessage, we begin enforcing such timeout. Even if we immediately\ncontinue to process the counterparty's init message to complete to\nhandshake, the timeout enforcement is not cleared. With the handshake\ncomplete, `awaiting_pong_timer_tick_intervals` is now tracked to enforce\na pong timeout, except a ping was never actually sent. If enough timer\nticks fire to trigger the `MAX_BUFFER_DRAIN_TICK_INTERVALS_PER_PEER`\nlogic, we'll end up disconnecting the peer due to a pong timeout.\n\nWe fix this by always resetting `awaiting_pong_timer_tick_intervals`\nupon processing our counterparty's init message.","shortMessageHtmlLink":"Fix race between handshake_complete and timer_tick_occurred"}},{"before":null,"after":"af3558d7f2cdc5c5a12de807dec5c1432ca71a1a","ref":"refs/heads/quiescence","pushedAt":"2024-04-06T07:47:05.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"WIP fuzzing","shortMessageHtmlLink":"WIP fuzzing"}},{"before":null,"after":"6d458656ffc015ef2cf5f14f555949601b399d4d","ref":"refs/heads/bump-tx-event-handler-weight-estimate-tests","pushedAt":"2024-04-06T07:02:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"WIP","shortMessageHtmlLink":"WIP"}},{"before":null,"after":"9a66e878eab0774ac302ef2add599638dd298224","ref":"refs/heads/bump-fees-conservatively","pushedAt":"2024-04-06T06:57:16.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Fix min relay feerate constant\n\nThe default is expressed in Bitcoin Core as 1000 sat/vkB. Its conversion\nrate to sat/kW is 1/4, but the inverse was applied. This led to our fee\nbumps overpaying by an additional 800% unnecessarily.","shortMessageHtmlLink":"Fix min relay feerate constant"}},{"before":"70e400182edddfeec886ed6d2d0faa8ede022819","after":null,"ref":"refs/heads/reserve-async-signing-channel-tlvs","pushedAt":"2024-04-01T16:02:57.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"}},{"before":"7be00bab9d3829523ba03a283e59c8eb96489999","after":"70e400182edddfeec886ed6d2d0faa8ede022819","ref":"refs/heads/reserve-async-signing-channel-tlvs","pushedAt":"2024-03-29T18:56:46.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Reserve async signing related channel TLV types\n\nA LDK user deployed to production a WIP version of the async signing\nbranch in which two new TLVs were added to channel. To prevent them from\nneeding to perform a migration, we can just new types for TLVs that have\nyet to be included in a release. A note has been added to ensure types\n45 and 47 are not used for another purpose.","shortMessageHtmlLink":"Reserve async signing related channel TLV types"}},{"before":null,"after":"7be00bab9d3829523ba03a283e59c8eb96489999","ref":"refs/heads/reserve-async-signing-channel-tlvs","pushedAt":"2024-03-29T18:53:23.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Reserve async signing related channel TLV types\n\nA LDK user deployed to production a WIP version of the async signing\nbranch in which two new TLVs were added to channel. To prevent from\nhaving to perform a migration, we can just new types for TLVs that have\nyet to be included in a release. A note has been added to ensure types\n45 and 47 are not used for another purpose.\n\nSigned-off-by: Wilmer Paulino ","shortMessageHtmlLink":"Reserve async signing related channel TLV types"}},{"before":"7c6cff370320c63d987beeeecc0bbbe54c07408d","after":"11c18ec7cfd6df546c517482f050db55d87b2047","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-03-29T01:57:16.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"fe6564816a6275e45dcd91dd0320c30ebb1f38de","after":null,"ref":"refs/heads/decode-htlc-onion-when-committed","pushedAt":"2024-03-28T22:20:19.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"}},{"before":"4210c01840ff6ffcf7059280959b4bffb7437edc","after":"7c6cff370320c63d987beeeecc0bbbe54c07408d","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-03-27T21:29:22.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"2d77292056ba21e9f656cfd529e6eaa85aff8093","after":"fe6564816a6275e45dcd91dd0320c30ebb1f38de","ref":"refs/heads/decode-htlc-onion-when-committed","pushedAt":"2024-03-27T21:29:12.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Decode update_add_htlc onions before forwarding HTLCs\n\nThis commit completes all of the groundwork necessary to decode incoming\n`update_add_htlc` onions once they're fully committed to by both sides.\nHTLCs are tracked in batches per-channel on the channel they were\nreceived on. While this path is unreachable for now, until\n`InboundHTLCResolution::Resolved` is replaced with\n`InboundHTLCResolution::Pending`, it will allow us to obtain\n`HTLCHandlingFailed` events for _any_ failed HTLC that comes across a\nchannel.","shortMessageHtmlLink":"Decode update_add_htlc onions before forwarding HTLCs"}},{"before":"b66e094f5f476785a967436d1d13eafa0ebfa5e3","after":"4210c01840ff6ffcf7059280959b4bffb7437edc","ref":"refs/heads/enable-decode-htlc-onion-until-committed","pushedAt":"2024-03-22T18:33:03.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Enable decoding new incoming HTLC onions when fully committed\n\nThis commit ensures all new incoming HTLCs going forward will have their\nonion decoded when they become fully committed to decide how we should\nproceed with each one. As a result, we'll obtain `HTLCHandlingFailed`\nevents for _any_ failed HTLC that comes across a channel.\n\nWe will now start writing channels with the new serialization version\n(4), and we will still be able to downgrade back to the commit that\nintroduced it since reading version 4 is supported.\n\nNote that existing pending inbound HTLCs may already have their\nresolution if they were received in a previous version of LDK. We must\nsupport those until we no longer allow downgrading beyond this commit.","shortMessageHtmlLink":"Enable decoding new incoming HTLC onions when fully committed"}},{"before":"d1e9231dcbfbd55b4382e512ec02c03512718d17","after":"2d77292056ba21e9f656cfd529e6eaa85aff8093","ref":"refs/heads/decode-htlc-onion-when-committed","pushedAt":"2024-03-22T18:32:40.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Decode update_add_htlc onions before forwarding HTLCs\n\nThis commit completes all of the groundwork necessary to decode incoming\n`update_add_htlc` onions once they're fully committed to by both sides.\nHTLCs are tracked in batches per-channel on the channel they were\nreceived on. While this path is unreachable for now, until\n`InboundHTLCResolution::Resolved` is replaced with\n`InboundHTLCResolution::Pending`, it will allow us to obtain\n`HTLCHandlingFailed` events for _any_ failed HTLC that comes across a\nchannel.","shortMessageHtmlLink":"Decode update_add_htlc onions before forwarding HTLCs"}},{"before":"588617e853ad5fc81500b58a6e0b8ab5b02a6edd","after":"d1e9231dcbfbd55b4382e512ec02c03512718d17","ref":"refs/heads/decode-htlc-onion-when-committed","pushedAt":"2024-03-22T18:26:44.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Decode update_add_htlc onions before forwarding HTLCs\n\nThis commit completes all of the groundwork necessary to decode incoming\n`update_add_htlc` onions once they're fully committed to by both sides.\nHTLCs are tracked in batches per-channel on the channel they were\nreceived on. While this path is unreachable for now, until\n`InboundHTLCResolution::Resolved` is replaced with\n`InboundHTLCResolution::Pending`, it will allow us to obtain\n`HTLCHandlingFailed` events for _any_ failed HTLC that comes across a\nchannel.","shortMessageHtmlLink":"Decode update_add_htlc onions before forwarding HTLCs"}},{"before":"59bfe6d68f99ca6fe44ef0e153f1a068f7bb9f03","after":"588617e853ad5fc81500b58a6e0b8ab5b02a6edd","ref":"refs/heads/decode-htlc-onion-when-committed","pushedAt":"2024-03-13T23:45:09.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Decode update_add_htlc onions before forwarding HTLCs\n\nThis commit completes all of the groundwork necessary to decode incoming\n`update_add_htlc` onions once they're fully committed to by both sides.\nHTLCs are tracked in batches per-channel on the channel they were\nreceived on. While this path is unreachable for now, until\n`InboundHTLCResolution::Resolved` is replaced with\n`InboundHTLCResolution::Pending`, it will allow us to obtain\n`HTLCHandlingFailed` events for _any_ failed HTLC that comes across a\nchannel.","shortMessageHtmlLink":"Decode update_add_htlc onions before forwarding HTLCs"}},{"before":"775fe9d09c8fd88698e9f3a94908fd856a848375","after":"59bfe6d68f99ca6fe44ef0e153f1a068f7bb9f03","ref":"refs/heads/decode-htlc-onion-when-committed","pushedAt":"2024-03-12T17:11:56.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"wpaulino","name":"Wilmer Paulino","path":"/wpaulino","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/9447167?s=80&v=4"},"commit":{"message":"Decode update_add_htlc onions before forwarding HTLCs\n\nThis commit completes all of the groundwork necessary to decode incoming\n`update_add_htlc` onions once they're fully committed to by both sides.\nHTLCs are tracked in batches per-channel on the channel they were\nreceived on. While this path is unreachable for now, until\n`InboundHTLCResolution::Resolved` is replaced with\n`InboundHTLCResolution::Pending`, it will allow us to obtain\n`HTLCHandlingFailed` events for _any_ failed HTLC that comes across a\nchannel.","shortMessageHtmlLink":"Decode update_add_htlc onions before forwarding HTLCs"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"startCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wOS0yMVQxOTo1MDo0NS4wMDAwMDBazwAAAAS828E8","endCursor":"Y3Vyc29yOnYyOpK7MjAyNC0wMy0xMlQxNzoxMTo1Ni4wMDAwMDBazwAAAAQTpmKU"}},"title":"Activity · wpaulino/rust-lightning"}