-
Notifications
You must be signed in to change notification settings - Fork 575
refactor: tagging related cleanup #17451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
c8c5c4f to
bcabcea
Compare
yarn-project/pxe/src/contract_function_simulator/oracle/private_execution_oracle.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/execution_data_provider.ts
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/execution_data_provider.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/pxe_oracle_interface.ts
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/pxe_oracle_interface.ts
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/tagging_utils.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/tagging_utils.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/tagging_utils.ts
Outdated
Show resolved
Hide resolved
b25d46f to
0a9c2b8
Compare
yarn-project/pxe/src/contract_function_simulator/tagging_utils.ts
Outdated
Show resolved
Hide resolved
bb2d7d4 to
6aa046a
Compare
yarn-project/pxe/src/storage/tagging_data_provider/tagging_data_provider.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/storage/tagging_data_provider/tagging_data_provider.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/tagging_utils.ts
Outdated
Show resolved
Hide resolved
yarn-project/pxe/src/contract_function_simulator/execution_data_provider.ts
Outdated
Show resolved
Hide resolved
| * @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 |
There was a problem hiding this comment.
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.
| 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 |
There was a problem hiding this comment.
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?
|
@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.
2fb6ac9 to
cb1c968
Compare

I started working on improving unconstrained tagging as proposed in this forum post and the initial step in implementing that is the following:
Given that the cache will reside in
PrivateExecutionOracleI 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:
PrivateExecutionOracleand request info based on that,This PR is a bit random so if something is not clear LMK.