Speak to a Governance Facilitator (currently @prose11 and @Patrick_j). The best way to get in contact is via the official MakerDAO Discord or the official MakerDAO forum. Please do not use email.
The canonical Code of Conduct is located here. Sign-up can be as fancy or not-fancy as you like. Some options include:
- Signing a message on-chain.
- Confirming that you have read and agreed to it within your Recognized Delegate Platform post (described in 3 below).
- Uploading a copy of the CoC to IPFS along with a statement saying that you have signed on to it.
The canonical template is located here. Deviation from the template is acceptable, but you should try to cover everything in the template. Contact details and Conflict of Interest disclosures are not optional (except where marked as such).
This is a chance to lay out what you stand for as a delegate within MakerDAO. Make what you stand for and why as clear and unambiguous as possible. This is the lens through which MKR Holders will see you and your actions. Try to make it attractive!
The Governance Facilitators will schedule this in collaboration with you and will host and record the meeting. The recording will be uploaded to the official MakerDAO YouTube channel. The recording can be removed in the future if you wish to cease being a Recognized Delegate.
Previous Meet Your Delegate calls can be found here.
This can be done using the official MakerDAO voting UI, using the account page.
There are two guides that explain how to get your delegate contract verified on Etherscan. They can be found here and here.
It is strongly recommended that delegates verify their contract, as many MKR Holders will not be comfortable interacting with an unverified smart contract.
An example of what is required can be found here. These files should be copied to a new folder such that the folder name matches the delegate contract address.
Recognized Delegates need to replace the profile.md and profile.jpg files. The file named metrics.md should be left as it is in the template; it will be updated by GovAlpha.
Other examples for existing delegates can be found in the delegates folder.
If you are completely unfamiliar with GitHub, GovAlpha is available to assist with this procedure.
Participation tracking is currently done manually by GovAlpha, but will hopefully be automated in the future. Abstain votes count as valid votes for the purposes of poll participation.
Failing to vote on an Executive Vote is valid and may occur in an emergency situation, or when a Recognized Delegate has fundamental disagreement with the contents. Failing to vote for an Executive Vote does not count against you as part of the participation tracking if you are able to provide sound reasoning for your abstention. The outcome of an Executive Vote will have no bearing on participation tracking for that Executive Vote. GovAlpha strongly recommends that Recognized Delegates and MKR holders consider the security and operational risks that opposing an Executive Vote poses to the Maker Protocol.
Forum and community participation will also be tracked, specifically in relation to voting. Recognized Delegates are expected to communicate their reasoning for voting when they vote. This can be in whichever format delegates feel is most appropriate, but must be communicated publicly so that GovAlpha can update the Recognized Delegate's metrics.
Updates to the participation metrics are manual and will be performed on a weekly basis.
Page last reviewed: 2022-10-26
Next review due: 2023-10-26