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
It's true that, as mentioned in the code, OP_CSV only allows 16bit
offsets. However it is possible to have blocks that are more than
UINT16_MAX blocks apart, and lightning's accept_channel message contains
a 32bit block height offset for the minimum_depth field. Because of
this, the AcceptChannel type was mis-using the 32bit BlockHeight type to
represent a relative block height, even though BlockHeight is intended
to represent absolute block height.
For the sake of using types consistently I've changed BlockHeightOffset
to be 32bits and changed the type of AcceptChannel.MinimumDepth to be a
BlockHeightOffset.
letcheck4= check msg.MaxAcceptedHTLCs (<) config.MinMaxAcceptedHTLCs "max accepted htlcs (%A) is less than the user specified limit (%A)"
466
466
letcheck5= check msg.DustLimitSatoshis (<) config.MinDustLimitSatoshis "dust limit satoshis (%A) is less then the user specified limit (%A)"
467
467
letcheck6= check msg.DustLimitSatoshis (>) config.MaxDustLimitSatoshis "dust limit satoshis (%A) is greater then the user specified limit (%A)"
468
-
letcheck7= check (msg.MinimumDepth.Value)(>)(config.MaxMinimumDepth.Value |> uint32)"We consider the minimum depth (%A) to be unreasonably large. Our max minimum depth is (%A)"
468
+
letcheck7= check msg.MinimumDepth (>) config.MaxMinimumDepth "We consider the minimum depth (%A) to be unreasonably large. Our max minimum depth is (%A)"
0 commit comments