Skip to content
This repository has been archived by the owner on May 22, 2023. It is now read-only.

Error after opening a new keep: could not check awaiting signature of digest [000...] #550

Open
pdyraga opened this issue Sep 21, 2020 · 0 comments
Open

Error after opening a new keep: could not check awaiting signature of digest [000...] #550

pdyraga opened this issue Sep 21, 2020 · 0 comments
Labels
📟 client
Milestone
v1.9.0

Comments

@pdyraga
Copy link
Member

pdyraga commented Sep 21, 2020

Once the client completes key generation for a new keep it is a member of, it starts watching signing events from that keep. It often happens that the client logs:

could not check awaiting signature of digest [0000000000000000000000000000000000000000000000000000000000000000] for keep [0xeFdCD4335d4164fe29DcE25b3DCe82a94f584143]

This could be about synchronization between Ethereum client nodes.
@pdyraga pdyraga added this to the v1.2.1 milestone Sep 21, 2020
@pdyraga pdyraga modified the milestones: v1.2.1, v1.2.2 Sep 26, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
📟 client
Projects
None yet
Milestone
v1.9.0
Development

No branches or pull requests
1 participant
@pdyraga