Skip to content

Conversation

@benesjan
Copy link
Contributor

@benesjan benesjan commented Oct 2, 2025

I started working on improving unconstrained tagging as proposed in this forum post and the initial step in implementing that is the following:

  1. store the tagging indexes requested during execution in a cache (just like we do with notes),
  2. when the execution is finished take the cache and along with a tx hash dump it into db.

Given that the cache will reside in PrivateExecutionOracle I now need to orchestrate the sync there.

When trying to do that (to be done in a PR up the stack) I realized that the current tagging-related API was cumbersome and this made me do the following in this PR:

  1. Have the API accept directionalAppTaggingSecret on the input instead of appTaggingSecret and recipient as now I can just compute it in the PrivateExecutionOracle and request info based on that,
  2. I moved the tagging functionality from stdlib to PXE as there was no reason to have it in stdlib,
  3. I simplified a bunch of random things.

This PR is a bit random so if something is not clear LMK.

@benesjan benesjan marked this pull request as draft October 2, 2025 10:20
@benesjan benesjan force-pushed the 10-02-refactor_tagging_related_cleanup branch from c8c5c4f to bcabcea Compare October 2, 2025 10:21
@benesjan benesjan force-pushed the 10-02-refactor_tagging_related_cleanup branch from b25d46f to 0a9c2b8 Compare October 2, 2025 11:20
@benesjan benesjan marked this pull request as ready for review October 2, 2025 11:20
@benesjan benesjan requested review from Thunkar and nventuro October 2, 2025 11:58
@benesjan benesjan force-pushed the 10-02-refactor_tagging_related_cleanup branch from bb2d7d4 to 6aa046a Compare October 2, 2025 14:21
@benesjan benesjan marked this pull request as draft October 3, 2025 13:25
@benesjan benesjan marked this pull request as ready for review October 4, 2025 09:11
Comment on lines 15 to 16
* @param localAddress - The complete address of entity 1 in the shared tagging secret derivation scheme
* @param localIvsk - The incoming viewing secret key of entity 1
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Compared to the original code I prefixed these 2 with "local" to communicate that they correspond to 1 entity. Then I think it's clearer that external corresponds to the entity 2.

@benesjan benesjan marked this pull request as draft October 6, 2025 10:20
externalAddress: AztecAddress,
): Promise<Point> {
const knownPreaddress = await computePreaddress(await localAddress.publicKeys.hash(), localAddress.partialAddress);
// TODO: #8970 - Computation of address point from x coordinate might fail
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copied this TODO here with the original code. Josie tackled that issue in this PR and I think we can afford to remove it from here as it seems fine that we throw in the toAddressPoint function on the next line if the address is invalid here.

Agree?

@benesjan benesjan marked this pull request as ready for review October 6, 2025 10:42
@benesjan benesjan requested a review from nventuro October 6, 2025 11:14
@benesjan
Copy link
Contributor Author

benesjan commented Oct 8, 2025

@nventuro managed to not rebase this with graphite so looking for changes since your last review should work.

I started working on improving unconstrained tagging as proposed in [this forum post](https://forum.aztec.network/t/on-note-discovery-and-index-coordination/7165) and the initial step in implementing that is the following:

1. store the tagging indexes requested during execution in a cache (just like we do with notes),
2. when the execution is finished take the cache and along with a tx hash dump it into db.

Given that the cache will reside in `PrivateExecutionOracle` I now need to orchestrate the sync there.

When trying to do that (to be done in a [PR up the stack](#17445)) I realized that the current tagging-related API was cumbersome and this made me do the following in this PR:
1. Have the API accept directionalAppTaggingSecret on the input instead of appTaggingSecret and recipient as now I can just compute it in the `PrivateExecutionOracle` and request info based on that,
2. I moved the tagging functionality from stdlib to PXE as there was no reason to have it in stdlib,
3. I simplified a bunch of random things.

This PR is a bit random so if something is not clear LMK.
@AztecBot AztecBot force-pushed the 10-02-refactor_tagging_related_cleanup branch from 2fb6ac9 to cb1c968 Compare October 14, 2025 08:42
@benesjan benesjan added this pull request to the merge queue Oct 14, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Oct 14, 2025
@benesjan benesjan added this pull request to the merge queue Oct 14, 2025
Merged via the queue into next with commit afc1ca4 Oct 14, 2025
15 checks passed
@benesjan benesjan deleted the 10-02-refactor_tagging_related_cleanup branch October 14, 2025 10:17
ludamad pushed a commit that referenced this pull request Dec 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants