Guidelines of Request for Proposals (RFP)
I’m here once again trying to be a good part-time contributor to ApeCoin DAO by helping out where I can and do some good for the DAO and the community.
The following is a proposed guidelines and clarity for the how ApeCoin DAO is to conduct a Request for Proposals (henceforth known as RFP).
The recent ApeChain RFP has brought forth a need to adequately explain the conditions and rules governing how an RFP is to be conducted, under what circumstances, and what the voting structure is.
As best understood, there have been three executed RFPs in ApeCoin DAO History:
- An RFP in response to AIP-21 and AIP-22, in which Horizon Labs was selected.
- An RFP for selecting a Cayman Islands Administrator as a result of AIP-196 that was approved and explicitly stated that it would perform said RFP.
- The ApeChain RFP. While the RFP retroactively had the ApeChain Poll/Vote to decide if the ApeChain RFP vote would proceed, it still carried the same weight of whether the ApeChain RFP vote would proceed.
It was during the ApeChain RFP that the community realized that we do not have a proper framework and a understanding of the RFP process and that needed to change. As such this AIP is designed to inform the community and those who wish to pursue an RFP the steps necessary to conduct one.
The following are the guidelines for how to conduct an RFP.
- An RFP must clearly describe and detail all relevant information to potential authors, including but not limited to, the background for the RFP, the purpose of the RFP, various features or capabilities as part of the RFP, and a timeline for said RFP.
- An RFP has to be approved by the community in a vote or poll using an official ApeCoin DAO space on Snapshot.
- A proposal submitted in response to an RFP must adhere to the AIP guidelines.
- The time period in which a proposal can be submitted for an RFP shall be at least 21 days. An exception can be made for matters that are paramount to the survivability or continued operations of ApeCoin DAO.
- An RFP must have at least two proposals submitted, meet all the criteria for said RFP, and be eligible to be voted on, in order for a vote to occur. Otherwise, the proposal that was submitted for the RFP and that is in proper condition for a vote, will be voted on as a regular AIP.
- The Snapshot vote resulting from submitted proposals for the RFP shall include all proposals that are in condition to be voted on. There shall be no “Against”, “None of the Above” or equivalent option, as a decision must be made regarding the RFP.
The overall cost for this proposal is expected to be zero.
Why is there no “Against” or “None of the Above option”?
Previous RFPs have been in response to AIPs or a vote that were decided by the community. As such, because the community voted in favor of the AIPs or vote necessitating the RFP, then a decision must be made by the community.
Why list an exception for the time period to which a proposal can be submitted?
The future of Web3 and crypto is uncertain as laws and regulations are always subject to change. It behooves us to be ready and willing to act accordingly should the need arise to keep the DAO operational.
Why is this AIP needed?
This AIP is designed to provide clarity to the community and guidelines for those looking to initiate an RFP. While we can infer certain rules and best practices based on past precedence set forth on the previous RFPs, it is best to have a set of guidelines going forward.