You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 and r/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.
Why does a "glue" contract is needed ? Can't just a gno script do the trick ?
Also, why not just add a link in the Valoper struct to a r/demo/profile ?
On another topic, on the Update function, i don't understand why there is no security checking if it's the validator that self-update his informations (with std.PrevRealm / std.GetOrigCaller) ?
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.
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: