-
Notifications
You must be signed in to change notification settings - Fork 627
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
Update expired light client with x/group #3326
Comments
Maybe the right way to do this is to allow for a management address when instantiating the client and perhaps a list of functions that the management address can access. This way there could be a per client ability to different security features. |
No work is needed for this issue. Using the newly added gov v1
I document below the steps followed in more detail. Create a groupsimd tx group create-group <group-admin-address> "" members.json where {
"members": [
{
"address": "<group-member-address>",
"weight": "1",
"metadata": ""
}
]
} Create a group policysimd tx group create-group-policy <group-admin-address> 1 "" policy.json where {
"@type": "/cosmos.group.v1.ThresholdDecisionPolicy",
"threshold": "1",
"windows": {
"voting_period": "5m",
"min_execution_period": "60s"
}
} Submit governance proposal with
|
Great, that works for me, thank you very much. In that case it would be good to keep a record of this in the wiki when you get the chance :) |
Summary
If a light client is frozen or expired, currently the only method to recover the client is with a governance proposal. Consider enabling recovery of a client with the x/group module
Problem Definition
Currently you can only recover a client through governance, governance cycles can take weeks in some cases which is problematic for pending packets in the channel. Enabling client recovery through another means could reduce this wait time, although it would add in an additional trust assumption to the specified group with permission to recover the client. The group could be elected via governance.
Proposal
Enable client recovery using x/group, where the composition of the group could be determined with governance, there could also be another more preferable solution
cc @zmanian @jackzampolin
For Admin Use
The text was updated successfully, but these errors were encountered: