Skip to content
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

[Onchain tracking] PoC #1056

Open
DaniSomoza opened this issue Nov 21, 2024 · 0 comments · May be fixed by #1057 or #1059
Open

[Onchain tracking] PoC #1056

DaniSomoza opened this issue Nov 21, 2024 · 0 comments · May be fixed by #1057 or #1059
Assignees

Comments

@DaniSomoza
Copy link
Contributor

Create a PoC testing the changes for onchain data tracking. We will test the code for both final ways of adding the identifier.:

  • Append the identifier hex encoded (keccak256) at the end of the Data
  • Use the refundReceiver field to set the hex encoded identifier.

We are still waiting for feedback from the Protocol team to understand if the first approach may have security concerns. This needs to be confirmed after Devcon.

Coordinate with analytics team how they plan to gather the data

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant