Signing Page - Sigit Not Updated With 2+ Signers #168
enes
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In my recent test, when there are more than 3 signers, and the creator is not the first signer, the state of the Sigit was not updated from the 2nd to the 3rd signer. It means that the 3rd Signer is not able to complete signing, as it still shows that we are waiting for the 2nd Signature.
While the root cause needs to be investigate, a potential safeguard mechanism could be to add a capability for any signer to "synchronise" or "check for updates" of the state of the sigit.
let's re-test
Haven't been able to reproduce.
But this part looks like a new feature, a way to invalidate processed events and try to get the correct state again?
This sounds like a useful thing (would potentially help with bricked accounts too) and like an opposite thing from "re-broadcast" feature, what do you think?
@b @eugene
having the ability to recreate a sigit from the originating events is definitely a feature we need, and would definitely fix bricked accounts
it's separate from this issue though I would say, and is dependent on a document (waiting on me) which delves into the raw detail of how SIGits get created