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

Reject a tx with existing nullifier. #1809

Closed
LeilaWang opened this issue Aug 25, 2023 · 0 comments
Closed

Reject a tx with existing nullifier. #1809

LeilaWang opened this issue Aug 25, 2023 · 0 comments
Labels
T-optimisation Type: Optimisation. Making something faster / cheaper / smaller

Comments

@LeilaWang
Copy link
Collaborator

Currently we always add a tx to the pool, and let the sequencer check everything. We can probably do some basic checks in the AztecRPCServer before sending it to the node. Reject a tx immediately if it has a nullifier that's already in a settled tx.

@github-project-automation github-project-automation bot moved this to Todo in A3 Aug 25, 2023
@iAmMichaelConnor iAmMichaelConnor added the T-optimisation Type: Optimisation. Making something faster / cheaper / smaller label Aug 25, 2023
@benesjan benesjan self-assigned this Aug 30, 2023
@benesjan benesjan moved this from Todo to In Progress in A3 Aug 30, 2023
@benesjan benesjan removed their assignment Aug 31, 2023
@github-project-automation github-project-automation bot moved this from In Progress to Done in A3 Oct 21, 2024
@iAmMichaelConnor iAmMichaelConnor removed this from A3 Oct 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-optimisation Type: Optimisation. Making something faster / cheaper / smaller
Projects
None yet
Development

No branches or pull requests

3 participants