-
Notifications
You must be signed in to change notification settings - Fork 491
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BOLT7: reply_channel_range parameter #560
Conversation
node implementation different 1I send below
|
node implementation different 2c-lightning and eclair reply |
send:
receive from c-lightning/eclair/lnd:
I want to allow below:
|
We revisited this on master recently. If you asked for block 100 and number_of_blocks 4294967295 we got upset and the peer for trying to make us overflow. We now handle it correctly.
This answer is incorrect. It should cover the entire range. It may do so by simply sending two empty reply_channel_range: 0 to 1288194 and (1288195+165984) to 4294967295. |
We expect the encoding byte to exist. For us, I think, that's easier to create and interpret. Is there a reason you don't want the extra byte? |
Oh, I had misunderstanding: |
* `first_blocknum` and `number_of_blocks` mean checking range
Simply |
Superceded by #737 |
BOLT7
reply_channel_range
requirementsso,
first_blocknum
= short_ids[0].blocknumber_of_blocks
= short_ids[LAST].block -first_blocknum
+ 1