Skip to content

Conversation

@t-bast
Copy link
Member

@t-bast t-bast commented Nov 5, 2025

While 73 bytes der-encoded signatures aren't standard (they're only possible with high-S signatures), miners could accept such signatures.

Most of our tests use 72 bytes der-encoded signatures because we will never generate 73 bytes der-encoded signatures ourselves. But it's more safe to use a 73 bytes signature in our weight estimation because:

  • it's what the BOLTs recommend
  • it's what other implementations use (e.g. LDK) which means they may reject our interactive-tx attempts by thinking we're under-paying fees

While 73 bytes der-encoded signatures aren't standard (they're only
possible with high-S signatures), miners could accept such signatures.

Most of our tests use 72 bytes der-encoded signatures because we will
never generate 73 bytes der-encoded signatures ourselves. But it's more
safe to use a 73 bytes signature in our weight estimation because:

- it's what the BOLTs recommend
- it's what other implementations use (e.g. LDK) which means they may
  reject our interactive-tx attempts by thinking we're under-paying
  fees
@t-bast t-bast requested a review from sstone November 5, 2025 14:03
@t-bast t-bast merged commit 817301a into master Nov 6, 2025
2 checks passed
@t-bast t-bast deleted the der-encoding-size branch November 6, 2025 08:30
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.

3 participants