Keystate sequence number of delegate multisig participants not updated after keystate refresh of multisig participant while delegated rotation is in progress

Open fanofvlei opened this issue 10 months ago • 1 comments

Description: I am performing some tests on rotating delegated multisig with GAR repo (plays as GARs) and Signifyts + Keria (play as QARs). In the process of rotation, GARs may use query-contact.sh in the GAR repo to query the keystates of QARs. However, some of the returned QAR keystates are "Seq No: 0", though all QARs have already done the key rotation. If GARs ignore this and proceed with delegate confirmation, the delegated rotation can still be done. Further, if GARs do query again after that, the returned QAR keystates are updated to "Seq No: 1".

Expected behavior: Sequence number should always update to latest after keystate refresh even during a delegated rotation operation.

SDKs used: Signifyts 0.3.0 Keria 0.2.0-rc2 GAR commit 0391ad5f579e239826656da04e071009e65fa7ef

Mar 12 '25 09:03 fanofvlei

I saw this issue as well. The sequence number was stale even after a key state refresh, which was unexpected.

Mar 13 '25 22:03 kentbull