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

Multisig join never resolves #227

Closed
daviddm opened this issue Feb 26, 2024 · 8 comments
Closed

Multisig join never resolves #227

daviddm opened this issue Feb 26, 2024 · 8 comments

Comments

@daviddm
Copy link
Contributor

daviddm commented Feb 26, 2024

I've made a test where I try to add a third member to a already existing multisig with 2 members.
When the third member tries to join the multisig the join-operation never resolves.

4b7bd58#diff-4b7bd582572785ca7f073ccab8064051e5b42ef6

@2byrds
Copy link
Contributor

2byrds commented Apr 25, 2024

From our keri dev meeting, Provenant along with @pfeairheller recently added two people to their 'migrated' wallet (command line to signify/keria). Signifypy has a series of scripts to test this functionality (for the migration). Provenant did use signify-ts for the two new participants. This was a delegated multi-sig that required approval.
Supplying versions is helpful in order to determine where the fix is needed.
Possibly a signify-ts update has the fix. Or an improvement in the steps used.
Join functionality specifically.

@Sotatek-HocNguyena
Copy link

Hi @daviddm. Were you able to call the groups().join? When I called it, it threw me a "500 Internal Server Error" everytime.

@daviddm
Copy link
Contributor Author

daviddm commented Apr 30, 2024

I updated the test and made a PR with it #258

When running the tests the member that tries to join the multisig-group is able to do it and can add the agent end-role after "successful" join. However the join operation still does not resolve.

I'm not sure if something has changed since February, but I know that i didn't try to just disregard the operation status and continue as if it was successful.

So maybe this isn't a signify-ts issue but instead a keria issue?

When printing the join-operation it looks like this
{ name: 'group.EOXbjvZfhXMoTsT48d8IKFXFwU-7QwL4dEd8avBhGfl3', metadata: { sn: 0 }, done: false, error: null, response: null }
What seems weird is that the sequence number is 0, when the groups current sequence number is 2.
It seems hardcoded in keria for joining
https://github.com/WebOfTrust/keria/blob/421716684229195a33287dab3f6556a01b4f8df9/src/keria/app/grouping.py#L144
But example rotating it uses the serders sequence number
https://github.com/WebOfTrust/keria/blob/421716684229195a33287dab3f6556a01b4f8df9/src/keria/app/aiding.py#L598

Versions

Keria: 0.1.3
Signify-ts: latest-main fddaff2

@2byrds
Copy link
Contributor

2byrds commented Apr 30, 2024

Thank you for the additions! I'll be taking a look at this next week if it hasn't been addressed by then

@lenkan
Copy link
Collaborator

lenkan commented Apr 30, 2024

I tried fixing that line and run against a local keria image, then it resolves. WebOfTrust/keria#236

@lenkan
Copy link
Collaborator

lenkan commented May 30, 2024

When the test here passes, we can merge that and this issue is resolved. Currently that test is failing because it the KERIA images is not updated to include the fix.

2byrds added a commit to 2byrds/keria that referenced this issue Jun 21, 2024
pfeairheller pushed a commit to WebOfTrust/keria that referenced this issue Jun 22, 2024
* improved design and logic per review comments, still need to track the dip process by the delegator

Signed-off-by: 2byrds <[email protected]>

* delegator endpoint processes dip as a long running processes. tests pass

Signed-off-by: 2byrds <[email protected]>

* small fixes to op checks

Signed-off-by: 2byrds <[email protected]>

* small fixes on checking dip success

Signed-off-by: 2byrds <[email protected]>

* remove unnecessary loop for interact operation

Signed-off-by: 2byrds <[email protected]>

* point to keri main for now, will use 1.2.0-dev5 when it's available

Signed-off-by: 2byrds <[email protected]>

* refactored degator end to delegating.py and corresponding tests and used credentialing design for IdentifierResource end usage

Signed-off-by: 2byrds <[email protected]>

* consolidate to optype of 'delegation' and clean up tests

Signed-off-by: 2byrds <[email protected]>

* improve naming to be consistent with credentialing, and tested with signify-ts delegation updates

Signed-off-by: 2byrds <[email protected]>

* fixes and tests rotation. also tested with signify-ts integration tests that do rotation

Signed-off-by: 2byrds <[email protected]>

* fixed group end smids/rmids

Signed-off-by: 2byrds <[email protected]>

* fix smid list in multisig request on_post

Signed-off-by: 2byrds <[email protected]>

* fix for intermittent smid/rmid dict or str

Signed-off-by: 2byrds <[email protected]>

* moving approval into longrunning operation, need to make approveDelegation idempotent

Signed-off-by: 2byrds <[email protected]>

* successful delegated multisig integration testing with Signify-ts

Signed-off-by: 2byrds <[email protected]>

* set to tagged keripy 1.2.0.dev6

Signed-off-by: 2byrds <[email protected]>

* removed duplicate comment and simplified keria.dockerfile to leverage keripy image

Signed-off-by: 2byrds <[email protected]>

* Remove any smids/rmids state dict test problems

Signed-off-by: 2byrds <[email protected]>

* Removed unnecessary annotation

Signed-off-by: 2byrds <[email protected]>

* fix multisig join after original creation see WebOfTrust/signify-ts#227

Signed-off-by: 2byrds <[email protected]>

* cleanup docker image entrypoint and instructions

Signed-off-by: 2byrds <[email protected]>

---------

Signed-off-by: 2byrds <[email protected]>
@2byrds
Copy link
Contributor

2byrds commented Aug 15, 2024

@daviddm can this be closed now per #258 ?

@lenkan
Copy link
Collaborator

lenkan commented Aug 16, 2024

@2byrds Yes, thanks for notifying.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants