feat(privacy): a delegated depositor names its deposits' associated addresses - #949
Open
avi-starkware wants to merge 1 commit into
Open
Conversation
This was referenced Aug 12, 2026
Collaborator
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Aug 12, 2026
avi-starkware
marked this pull request as ready for review
August 12, 2026 08:54
avi-starkware
force-pushed
the
avi/screening-v3/timestamp-cheat-helpers
branch
from
August 17, 2026 18:52
38d94e3 to
acb73ff
Compare
avi-starkware
force-pushed
the
avi/screening-v3/delegated-query
branch
from
August 17, 2026 18:52
586ad93 to
fd82f75
Compare
avi-starkware
changed the title
avi-starkware
force-pushed
the
avi/screening-v3/delegated-query
branch
2 times, most recently
from
August 18, 2026 10:43
b79c463 to
2a49606
Compare
avi-starkware
force-pushed
the
avi/screening-v3/timestamp-cheat-helpers
branch
from
August 18, 2026 13:45
acb73ff to
b0a31b3
Compare
avi-starkware
force-pushed
the
avi/screening-v3/delegated-query
branch
from
August 18, 2026 13:45
2a49606 to
dff5be0
Compare
…ddresses The Delegated policy reads those addresses out of the invoke's own return data, following the deposits, so the pool makes no second call: a depositor names them where it already answers. An empty span reverts and every address named goes through the same requirement collection. Leftover return data is still rejected, except from a depositor whose policy reads no addresses — a tolerance carrying a TODO, without which the anonymizer could fund nothing while listed anything but Delegated.
avi-starkware
force-pushed
the
avi/screening-v3/timestamp-cheat-helpers
branch
from
August 18, 2026 14:31
b0a31b3 to
3ef7d2b
Compare
avi-starkware
force-pushed
the
avi/screening-v3/delegated-query
branch
from
August 18, 2026 14:31
dff5be0 to
7e779ab
Compare
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.
An Invoke returning open-note deposits consults its target's OpenNoteScreeningPolicy:
Required—every unlisted address — makes the target the tx's screening subject,
Exemptraises norequirement, and
Delegatedasks the target which addresses to screen, through aget_screening_subjectscall carrying the invoke's own calldata. Only a compute-invoke isdelegated; a plain invoke is exempt, so a target offering both never has to guess which calldata it
is parsing. The query is fail-closed: any failure, a malformed answer, or an empty one reverts.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
This change is