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

Cross-node nonce coordination #9129

Open
magik6k opened this issue Aug 5, 2022 · 1 comment
Open

Cross-node nonce coordination #9129

magik6k opened this issue Aug 5, 2022 · 1 comment
Labels
area/messages area/wallet Area: Wallet kind/feature Kind: Feature P2 P2: Should be resolved

Comments

@magik6k
Copy link
Contributor

magik6k commented Aug 5, 2022

It would be great to have some kind of a mechanism to coordinate nonces between separate/redundant lotus nodes

This would most likely be extending the message signer to be able to coordinate between chain nodes

This could be done by:

  • Making nodes talk to each other, and use some quorum based system to coordinate nonces
    • This is probably overkill
  • Create a separate implementation backed by some standard database, enabled through the node config.
    • Not entirely sure what database - if it's easy enough to use some generic cross-database thing, maybe we want that.
    • Alternatively instead of chosing the database, point nodes at a signing api which would also handle nonces itself
      • This could be done by just extending the existing remote wallet backend, and adding a config knob to enable remote nonce assigning
      • Possibly the cleanest/most flexible approach?
@magik6k magik6k added kind/feature Kind: Feature area/wallet Area: Wallet area/messages labels Aug 5, 2022
@jennijuju jennijuju modified the milestones: v1.17.1, v1.17.2 Aug 8, 2022
@jennijuju jennijuju removed this from the v1.17.2 milestone Aug 12, 2022
@jennijuju jennijuju added the P2 P2: Should be resolved label Aug 12, 2022
@jennijuju
Copy link
Member

We've decided to move away from this for 9130 atm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/messages area/wallet Area: Wallet kind/feature Kind: Feature P2 P2: Should be resolved
Projects
None yet
Development

No branches or pull requests

3 participants