Skip to content

feat: support push_asset_amount on RGB channel open#19

Open
bitwalt wants to merge 1 commit intoRGB-Tools:rgbfrom
bitwalt:feat/push-asset-amount-rln
Open

feat: support push_asset_amount on RGB channel open#19
bitwalt wants to merge 1 commit intoRGB-Tools:rgbfrom
bitwalt:feat/push-asset-amount-rln

Conversation

@bitwalt
Copy link

@bitwalt bitwalt commented Mar 10, 2026

Implements #18

@bitwalt bitwalt force-pushed the feat/push-asset-amount-rln branch from d55ff5f to 125b5ab Compare March 10, 2026 16:42
@zoedberg
Copy link
Member

Thanks! I will review this ASAP, but please in the meantime do a self review and drop unnecessary changes (see lightning/src/ln/channel.rs)

@bitwalt bitwalt force-pushed the feat/push-asset-amount-rln branch 2 times, most recently from 890fbd5 to ee98355 Compare March 11, 2026 11:55
Copy link
Member

@zoedberg zoedberg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, please address the requested changes

Comment on lines +3134 to +3135
/// The RGB asset amount to push to the counterparty on channel open.
pub(super) push_asset_amount: Option<u64>,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would be better to move this to the FundingScope since it should be needed only during the funding phase. Same should be for consignment_endpoint, which I forgot to move when updating rust-lightning last time. Would you please move both?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, I kept only a derived is_colored flag in ChannelContext so the channel can retain that property without holding funding-only data there.

@bitwalt bitwalt force-pushed the feat/push-asset-amount-rln branch from ee98355 to ea15124 Compare March 12, 2026 12:33
@bitwalt
Copy link
Author

bitwalt commented Mar 13, 2026

Hi Zoe, thanks for the review. Requested changes should have been applied.

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