Shashwat Vangani
Shashwat Vangani
**Updated:** [*.04 → .05*](https://github.com/shaavan/rust-lightning/compare/pr4152.04..pr4152.05) Changes: - Fixed the third test. @TheBlueMatt > This shouldn't be an issue? We should be failing all blinded path receives with invalid_onion_blinding and we should...
**Updated:** [*.05 → .06*](https://github.com/shaavan/rust-lightning/compare/pr4152.05..pr4152.06) ### Changes: Cleaned up the commits for clarity and flow. ### Note With this update, the first full version of Payment Dummy Hops for Blinded Payment...
**Updated:** [*.06 → .07*](https://github.com/shaavan/rust-lightning/compare/pr4152.06..pr4152.07) Addressed @TheBlueMatt’s comment — updates: - Added a debug-assert during blinded payment path construction to ensure all hops (except the final recipient) serialize to the same...
**Updated:** [*.07 → .08*](https://github.com/shaavan/rust-lightning/compare/pr4152.07..pr4152.08) Thanks, @jkczyz - Changes: - Renamed ForwardInfo -> NextHopForwardInfo for clarity - DRYed up code, and test helpers - Corrected, and expanded documentation
**Updated:** [*.08 → .09*](https://github.com/shaavan/rust-lightning/compare/pr4152.08..pr4152.09) 1. Cleared up test reasoning. 2. Updated re-enqueuing dummy htlc logic to prevent unintentional payment loss.
**Rebased:** [*.09 → .10*](https://github.com/shaavan/rust-lightning/compare/pr4152.09..pr4152.10)
**Fix rustfmt:** [*.10 → .11*](https://github.com/shaavan/rust-lightning/compare/pr4152.10..pr4152.11)
With the current version of PR, I am seeking concept/approach ACKs before I start working on the test suite. A gentle ping, @jkczyz :) Thanks!
Updated from [pr2380.01](https://github.com/shaavan/rust-lightning/commits/p2830.01) to [pr2830.02](https://github.com/shaavan/rust-lightning/commits/pr2830.02) ([diff](https://github.com/shaavan/rust-lightning/compare/p2830.01..pr2830.02)): Address @TheBlueMatt comments 1. Removed custom_tlvs for ForwardTlvs, as they don't seem logically feasible. 2. Added custom_tlvs for BlindedPaths::payment:: ReceiveTlvs 3. Fixed issues as...
The are still some conceptual kinks to be ironed out before finalising the custom TLV's implementation. So Drafting up the PR for now! ♻️