feat(policy): enforce receive policies in zones#516
Open
mattsse wants to merge 1 commit into
Open
Conversation
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
1 participant
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
Why
Recent Tempo TIP-1028 changes added per-account receive policies, but zones only decoded the event as ignored state and did not enforce inbound blocking locally. That allowed zone-side transfers and mints to miss the L1 receive-policy behavior.
Impact
Zone execution now mirrors L1 receive-policy behavior for T6+: token filters are evaluated before sender policies, blocked funds move to the guard, and guard claims are available through the upstream ReceivePolicyGuard precompile.