-
Notifications
You must be signed in to change notification settings - Fork 391
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
Improve r/gnoland/valopers to onboard new validators #3567
Comments
Here are the reference to two initiatives for collecting validators details on two initiatives, https://github.com/atomone-hub/govgen-validators |
Why does a "glue" contract is needed ? Can't just a Also, why not just add a link in the Valoper struct to a On another topic, on the I'm probably missing something |
Glue contracts offer better auditability. While a Gno script could accomplish the task, I prefer to release my recurring script needs as contracts, which could be called "templated actions contracts." I will reserve my more private and unique scripting needs for Gno scripts. |
We confirm we can work on it at Berty. We'll be back with updates shortly. |
Just to be sure what Manfred wants, I want to reformulate. This PR should do 2 main things:
Other small things to do:
Does that sound correct? |
The current version of the validator registration contract can be found here. We need to make a few changes, starting with removing the dependency on
r/sys/validators
. This contract should not be directly tied to the r/sys contracts; it is intended for validator operators to self-register, similar to a "call for papers." Later, a separate external contract (a glue contract) will interact with both this contract andr/sys/validators
to propose templated changes to GovDAO. We can also remove the /v2 suffix since we are eliminating the dependency on r/sys/validators.The contract should focus on allowing validators to register and update parameters as needed. It may optionally link with
r/demo/profile
and should include a list of questions inspired by the recent Atom One launch, using their GitHub or Google Forms as a reference. The contract should display a list of current proposals, along with a brief introductory text and a link to a page that can be easily updated—either a README or a meta issue, as the explanations will need to be refined.cc @sw360cab @albttx @zivkovicmilos
The text was updated successfully, but these errors were encountered: