You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 18, 2020. It is now read-only.
When node generates a secret (currently it happens at the beginning of 0-th slot of any epoch), it should add corresponding commitment to mpcLocalCommitments and put it into generated block later (if it's leader). Currently it's not done.
I don't know about openning for own locally stored secret, but it should also be added to local openings and to block.
The text was updated successfully, but these errors were encountered:
Done except shares. Ideally we also should ensure that our shares are in block created by us (if not in someone else's block). However, it's harder to do and is less important, because we don't need shares usually.
Approach is that secrets/openings are not put into local maps when they are generated or something, but they are put into MpcData which is result of getLocalMpcData.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When node generates a secret (currently it happens at the beginning of 0-th slot of any epoch), it should add corresponding commitment to
mpcLocalCommitments
and put it into generated block later (if it's leader). Currently it's not done.I don't know about openning for own locally stored secret, but it should also be added to local openings and to block.
The text was updated successfully, but these errors were encountered: