The channel ID currently has two representations: as a [u8; 32] and as a Scalar. These representations do not have a bijective relationship -- there are more byte arrays than scalars.
We should make sure that the representation that is serialized, displayed, and stored in databases is not ambiguous.
I think there is not an operational bug related to this, but printing it out (Display) sometimes shows a different value than the serialized version.
The channel ID currently has two representations: as a
[u8; 32]and as aScalar. These representations do not have a bijective relationship -- there are more byte arrays than scalars.We should make sure that the representation that is serialized, displayed, and stored in databases is not ambiguous.
I think there is not an operational bug related to this, but printing it out (Display) sometimes shows a different value than the serialized version.