fix: backport remove insecure SchnorrSingleKeyAccount contract to v4-next#21548
Merged
nchamo merged 10 commits intobackport-to-v4-next-stagingfrom Mar 13, 2026
Merged
Conversation
## Summary - Lower `SLASH_INACTIVITY_TARGET_PERCENTAGE` from 0.8 to 0.7 - Disable `SLASH_DUPLICATE_PROPOSAL_PENALTY` and `SLASH_DUPLICATE_ATTESTATION_PENALTY` (set to 0) - Increase `SLASH_GRACE_PERIOD_L2_SLOTS` from 1200 to 8400 - Reduce `perBlockAllocationMultiplier` from 2 to 1.2 ## Test plan - Verify generated config files are updated after running `yarn generate` in relevant packages - Deploy to devnet/testnet and confirm slasher behavior matches new parameters --------- Co-authored-by: Aztec Bot <49558828+AztecBot@users.noreply.github.com>
This PR was created because merging `v4` into `v4-next` resulted in conflicts. Please resolve the conflicts and merge this PR to keep `v4-next` up to date. This PR was auto-generated by the `pull-v4-into-v4-next` workflow.
Kept v4-next's existing migration notes and added the SingleKeyAccountContract removal note at the top of the TBD section. Removed duplicate 'aztec new' section that came from the incoming cherry-pick.
…cription The auto-generated CLI reference doc still had the old 'single-key account' description. Updated to match the source code change.
nchamo
approved these changes
Mar 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backport of #20766 to v4-next.
The
SchnorrSingleKeyAccountcontract and its TypeScript wrapperSingleKeyAccountContracthave been removed. This contract was insecure: it usedivpk_m(incoming viewing public key) as its Schnorr signing key, meaning anyone who received a user's viewing key could sign transactions on their behalf.Cherry-pick conflict resolution
The automatic cherry-pick failed due to a conflict in
docs/docs-developers/docs/resources/migration_notes.md. The v4-next branch had additional migration notes (getPublicEvents, simulate/send return types, aztec new changes) that don't exist on the original PR's base. Resolution: kept all v4-next content and added the SingleKeyAccountContract removal note at the top of the TBD section.Commits
ClaudeBox log: https://claudebox.work/s/6d5d6c906edf05f9?run=1