Skip to content

Remove high-S signature handling from miners and signers - #7484

Open
benjamin-stacks wants to merge 3 commits into
stacks-network:mainfrom
benjamin-stacks:chore/remove-high-s-special-casing
Open

Remove high-S signature handling from miners and signers#7484
benjamin-stacks wants to merge 3 commits into
stacks-network:mainfrom
benjamin-stacks:chore/remove-high-s-special-casing

Conversation

@benjamin-stacks

@benjamin-stacks benjamin-stacks commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #7163 and #7337, where mempool admittance and block validation received special handling for those transactions. Now that we've transitioned into Epoch 4.0, those signatures are forbidden by consensus and no longer need to be special-cased.

Follow-up to stacks-network#7163 and stacks-network#7337, where mempool admittance and block
received special handling for those transactions. Now that we've
transitioned into Epoch 4.0, those signatures are forbidden by consensus
and no longer need to be special-cased.
@brice-stacks

Copy link
Copy Markdown
Contributor

Looks like mempool_setup_chainstate needs an update.

@brice-stacks brice-stacks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good aside from the failing test that needs to be updated.

Comment thread stackslib/src/chainstate/stacks/db/blocks.rs Outdated
This comment explained the additional function argument that was removed
in d6021f4, so it's no longer needed.
This section of the `mempool_setup_chainstate()` test was added in stacks-network#7163
to ensure that the mempool rejects high-S signatures. That was necessary
back then because this behavior differed from consensus behavior.

Now that high-S signatures are disallowed by consensus (this has test
coverage elsewhere), it's no longer necessary to check this special
case. And because this test does not run as Epoch 4.0, in this case the
check actively fails.
@benjamin-stacks

Copy link
Copy Markdown
Contributor Author

Looks like mempool_setup_chainstate needs an update.

1049eb6

@brice-stacks brice-stacks left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

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.

2 participants