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

Allow multiple nodes to sign #915

Open
freak12techno opened this issue Jul 6, 2024 · 0 comments
Open

Allow multiple nodes to sign #915

freak12techno opened this issue Jul 6, 2024 · 0 comments

Comments

@freak12techno
Copy link
Contributor

I am unsure whether this is technically possible or safe, but hear me out.

I have an idea that consists of the following:

  • allow multiple nodes on the same network to connect to tmkms instance
  • generate signature once per each hrs and broadcast it every time it's requested, not signing it twice
  • multiple nodes broadcast the same signature, so it should not cause a double signing
  • if one node goes down (e.g. server crashed, resyncing etc.), then the other one would still broadcast the vote and validator won't skip blocks
  • it would only skip blocks if all of the nodes would die this way

I am in no way a Tendermint/CometBFT expert, but wonder if that's actually technically possible, and would it be safe (in theory, it sounds scary, but broadcasting the same vote twice should not trigger the double signature right?)

If that can be done, this might eliminate the specific node as a single point of failure, and the idea sounds really promising.

What do you guys think?

(If that's not technically possible, I suggest outlining it in the docs as this would be limited to the BFT level architecture then I guess)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant