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
When receiving an onion error, the spec says that we should verify it's no larger than 256 bytes.
But this is just a SHOULD, not a MUST, and it could be useful in the future to make this larger.
We currently don't support lengths greater than 256 byte, but this should be easy to change now on the reader side without creating any backwards-compatibility issue, and we will allow us to introduce bigger errors in the future once everyone supports reading them.
The specification recommends using a length of 256 for onion errors, but
it doesn't say that we should reject errors that use a different length.
We may want to start creating errors with a bigger length than 256 if we
need to transmit more data to the sender. In order to prepare for this,
we keep creating 256-bytes onion errors, but allow receiving errors of
arbitrary length.
See the specification here: lightning/bolts#1021Fixes#2438
When receiving an onion error, the spec says that we should verify it's no larger than 256 bytes.
But this is just a SHOULD, not a MUST, and it could be useful in the future to make this larger.
We currently don't support lengths greater than 256 byte, but this should be easy to change now on the reader side without creating any backwards-compatibility issue, and we will allow us to introduce bigger errors in the future once everyone supports reading them.
See lightning/bolts#1021 for more context.
The text was updated successfully, but these errors were encountered: