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

Have Tributary transactions bind to a block hash #642

Open
kayabaNerve opened this issue Jan 12, 2025 · 0 comments
Open

Have Tributary transactions bind to a block hash #642

kayabaNerve opened this issue Jan 12, 2025 · 0 comments
Labels
coordinator improvement This could be better

Comments

@kayabaNerve
Copy link
Member

Currently, Tributary transactions bind to the genesis block. Under full asynchrony, a malicious 34% may produce two distinct chains (splitting the honest validators) and convince each 33% the other are faulty by:

  • Obtaining synchrony on a block on one chain
  • Collecting the relevant preprocess transactions
  • Placing them on the other chain, before synchrony has been obtained

Since the signing protocol hasn't been whitelisted yet, this will cause a fatal slash. If the preprocess transactions did bind to the tip block of their blockchain, the other blockchain would refuse to accept these transactions.

In general, a malicious 34% shouldn't be able to cause fatal slashes. While this requires asynchrony and can be argued unlikely, we should still fix this as it does allow a malicious 34% to cause fatal slashes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
coordinator improvement This could be better
Projects
None yet
Development

No branches or pull requests

1 participant