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.

Sign up for GitHub

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

Jump to bottom

Audit transaction arity implications for client fingerprinting #3379

Closed
Tracked by #3377
aubrika opened this issue Nov 15, 2023 · 1 comment
Closed
Tracked by #3377

Audit transaction arity implications for client fingerprinting #3379

aubrika opened this issue Nov 15, 2023 · 1 comment
Assignees
@TalDerei
Labels
A-client Area: Design and implementation for client functionality C-design Category: work on the design of Penumbra _P-V1 Priority: slated for V1 release
Milestone
Sprint 6

Comments

@aubrika
Copy link
Contributor

aubrika commented Nov 15, 2023 •
edited
Loading

Penumbra transactions reveal the arity of their actions: how many spends, outputs, etc. Prior to committing to the transaction format, we should audit it to see whether there are any opportunities to close information leaks. For instance, should we place restrictions on how actions are ordered? Or should that be a client-side concern?

Why this feature is required pre-mainnet

We need to do this prior to stabilizing the transaction format

What we need to implement

Unclear; this would primarily be a design review with presumably minor changes to the transaction format or transaction building.
@aubrika aubrika mentioned this issue Nov 15, 2023
Closed
11 tasks
@aubrika aubrika added the _P-V1 Priority: slated for V1 release label Nov 15, 2023
@TalDerei TalDerei self-assigned this Mar 22, 2024
@TalDerei
Copy link
Collaborator

Tangentially related to #3435 and tracked by #3467

@conorsch conorsch added this to the v1 milestone Mar 25, 2024
@github-project-automation github-project-automation bot moved this to 🗄️ Backlog in Penumbra Mar 25, 2024
@conorsch conorsch removed this from the v1 milestone Mar 25, 2024
@aubrika aubrika added this to the Sprint 3 milestone Mar 25, 2024
@TalDerei TalDerei moved this from 🗄️ Backlog to Todo in Penumbra Mar 25, 2024
@TalDerei TalDerei moved this from Todo to In progress in Penumbra Mar 26, 2024
@cratelyn cratelyn modified the milestones: Sprint 3, Sprint 4 Apr 8, 2024
@cratelyn cratelyn modified the milestones: Sprint 4, Sprint 5 Apr 22, 2024
@TalDerei TalDerei mentioned this issue May 3, 2024
Merged
@TalDerei TalDerei added A-client Area: Design and implementation for client functionality C-design Category: work on the design of Penumbra labels May 4, 2024
@aubrika aubrika added the friction something made this fall into the following milestone & the reason should be noted in a comment label May 6, 2024
@aubrika aubrika modified the milestones: Sprint 5, Sprint 6 May 6, 2024
@cratelyn cratelyn removed the friction something made this fall into the following milestone & the reason should be noted in a comment label May 6, 2024
hdevalence pushed a commit that referenced this issue May 6, 2024
@TalDerei
refactor(transaction): Implement canonical ordering in `TransactionPl…
f0e7696 
…an` (#3467)

References #3435 and
#3379

---------

Signed-off-by: Tal Derei <[email protected]>
@TalDerei TalDerei closed this as completed May 6, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Penumbra May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@TalDerei TalDerei

Labels
A-client Area: Design and implementation for client functionality C-design Category: work on the design of Penumbra _P-V1 Priority: slated for V1 release
Projects
Penumbra
Archived in project
Testnets
Status: No status
Milestone
Sprint 6
Development

No branches or pull requests
4 participants
@conorsch @cratelyn @TalDerei @aubrika