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

Zcash transactions come with a kind of finality which protects the users as much as possible against all possible attacks, and is sufficient for services such as cross-chain bridges and centralized exchanges. #18

Open
shielded-nate opened this issue Nov 13, 2024 · 3 comments
Labels
Deployment Goals Top-level deployment goals from Scoping.md Scoping Related to Scoping.md

Comments

@shielded-nate shielded-nate added the Deployment Goals Top-level deployment goals from Scoping.md label Nov 13, 2024
@shielded-nate
Copy link
Contributor Author

We should be more precise than "all possible attacks" because introducing finality in the first place enables denial-of-service attacks.

The kinds of attacks finality protects against are rollback attacks, double/multi spends, and certain kinds of eclipse attacks. (T/F?)

@shielded-nate shielded-nate added the Scoping Related to Scoping.md label Nov 13, 2024
@shielded-nate
Copy link
Contributor Author

Responding to myself from last comment: we still protect as much as possible against denial-of-service attacks, even though finalizing protocols introduce a new kind of DoS vector.

@shielded-nate
Copy link
Contributor Author

Is #41 actually a prerequisite for this ticket?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Deployment Goals Top-level deployment goals from Scoping.md Scoping Related to Scoping.md
Projects
None yet
Development

No branches or pull requests

1 participant