feat: add optional additional scopes to wallet transaction API (backport #20487)#21549
Merged
nchamo merged 9 commits intoMar 13, 2026
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.
…on API (#20487) (with conflicts)
Resolved conflicts between v4-next's destructured return types (from offchain output changes) and the additionalScopes additions. Kept v4-next's destructured forms while adding additionalScopes parameters from the original PR.
The cherry-pick introduced a duplicate scopesFrom method since v4-next already had it.
…o claudebox/backport-20487-wallet-scopes-v4-next # Conflicts: # yarn-project/pxe/src/contract_function_simulator/oracle/private_execution_oracle.ts
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 #20487 to
v4-next.Adds an explicit
additionalScopesoption onsend(),simulate(), anddeploy()so callers can declare upfront which additional addresses' private state they need access to beyond the sender's. Removes auto-expansion of scopes for nested private calls to registered account contracts.Conflicts resolved
The main conflicts were between v4-next's destructured return types (from the offchain output changes where
send()returns{ txHash, ... }/{ receipt, ... }/{ contract, ... }) and the original PR'sadditionalScopesadditions. Resolution: kept v4-next's destructured forms while incorporatingadditionalScopesparameters.Also removed a duplicate
scopesFrommethod inbase_wallet.tssince v4-next already had it.Test plan
additionalScopesis available on send/simulate/deploy optionsClaudeBox log: https://claudebox.work/s/fff8a9728750d830?run=1