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

Archive publicly-available testnet tx data #8939

Closed
Tracked by #8977
iAmMichaelConnor opened this issue Oct 2, 2024 · 2 comments · Fixed by #11192
Closed
Tracked by #8977

Archive publicly-available testnet tx data #8939

iAmMichaelConnor opened this issue Oct 2, 2024 · 2 comments · Fixed by #11192
Labels
A-privacy-leakage Area: Relates to privacy leakage. T-feature-request Type: Adding a brand new feature (not to be confused with improving an existing feature).
Milestone

Comments

@iAmMichaelConnor
Copy link
Contributor

We need to decide on sensible constants for all sorts of arrays of information that are emitted by the final tail private kernel circuit. This data will help infom such decisions.

Add a config option to testnet nodes to store all data of every tx they see. Perhaps we can exclude storing the "proof" (which is just incoherent maths), and only store the public inputs and underlying log data associated with a tx.

@iAmMichaelConnor iAmMichaelConnor added T-feature-request Type: Adding a brand new feature (not to be confused with improving an existing feature). A-privacy-leakage Area: Relates to privacy leakage. labels Oct 2, 2024
@github-project-automation github-project-automation bot moved this to Todo in A3 Oct 2, 2024
@rahul-kothari rahul-kothari added this to the TestNet milestone Oct 11, 2024
@joshklop
Copy link

Hi!

It looks like this will involve instrumenting the AztecKVTxPool here to collect public data (besides the proof) from the Tx structure here; is that on the right track?

@PhilWindle
Copy link
Collaborator

Hi @joshklop, yes I think that approach should work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-privacy-leakage Area: Relates to privacy leakage. T-feature-request Type: Adding a brand new feature (not to be confused with improving an existing feature).
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants