Repository navigation
Sync: v3.3.0-rc2 from protocol-internal - #832
Merged
Merged
Conversation
hieronx
force-pushed
the
sync/v3.3-rc2
branch
from
September 9, 2026 19:16
500a56c to
46bbe54
Compare
hieronx
enabled auto-merge (squash)
September 9, 2026 19:22
onnovisser
approved these changes
Sep 9, 2026
hieronx
disabled auto-merge
September 9, 2026 19:23
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
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.
Publishes the v3.3 protocol as of
protocol-internal#382, the fixes and hardening that followed the v3.3 audits.Everything in it is additive: 30 files, 1558 insertions, no file deleted and
env/untouched.VaultRouter.getVaultvalidates the vault it resolves against the full(poolId, scId, asset)tuple it was asked about.FreelyTransferableno longer strands deposit claims. Claim eligibility is now documented per entry point insrc/token/hooks/README.md, since which party the hook is asked about differs between the legs that hand out shares and the legs that pay out assets.ShareTokenRegistrar.burnno longer claims the caller's allowance survives the burn, andIBaseTransferHookno longer implies themaxRedeem/maxWithdraw/claimableCancelDepositRequestviews are what gate a claim.test/invariant/vaults/, reached withFOUNDRY_PROFILE=invariant), a hook permissiveness lattice, and a hook claim lifecycle suite pinning all four settlement legs across all four shipped hooks.docs/audits/out-of-scope/v3.3.0.mdextended with what the audits surfaced and this release accepts.Synced from protocol-internal#382