Please note that the Nexus Program is temporarily suspended. The information in this document is outdated, and this page has been archived until further notice.
Overview
We know that we have very creative community members that come up with ideas they would like to be implemented. However, many of these are not achievable by the Sipher team alone given that our current top priority is building a game that provides a fun and enjoyable experience where you can earn while you play.
This program and the proposal process have been established to make some of these ideas possible. Projects or initiatives could be planned, organized, and described in detail as part of a proposal that could potentially turn these ideas into a reality.
Idea and Proposal Sources
With this system, we expect there to be three primary sources for ideas or proposals:
- Self-initiated Community Project Proposals
- Council-Driven Project Requests
- Financier-Driven Project Requests
Self-initiated Community Project Proposals (SCP)
The council will serve as the first point of contact that will evaluate the proposals and communicate with the Builders throughout the process. Afterward, those proposals that are accepted will be evaluated by the community and voted on (
The following list includes the steps in this Proposal Process:
- Proposal Submission
To apply for a grant and turn an idea into an active project, Builders should first submit a proposal. This proposal must follow a specific template that asks for key criteria which will be used by the Council to filter, curate, and evaluate each proposal. You can find the template and an example below:
SCP Project Proposal Template
SCP Project Proposal Template - Pre-filled Example
2. Evaluation and Follow-up
After receiving proposals, the Council will review and evaluate each one of them. If there are any questions, concerns, or potential feedback to the Builders, there will be a set period (standard for each proposal) to do so.
- If the council believes that the proposal does not include all requirements as specified on the template, that the initiative or project does not align with Sipher's goals, vision, or mission, or they determine that it does not benefit the community, then they may reject the proposal in its entirety.
- If the council believes that the timeline and/or budget are not reasonable, they may either reject the proposal completely, or they may provide the Builders with an opportunity to update the proposal with a more reasonable timeline and/or budget.
3. Proposal Selection
After the proposal has been thoroughly reviewed by the Council and determined to have met the requirements stated in Point 2 (as above), the proposal will be made available to the community to view, and an official vote will be held for the community to decide on its outcome. (
Council-Driven Project Requests (CDPR)
These are requests created by the Council, which are based on ideas that originate from the Council itself. Requests should follow a specific request template and they will be posted for the community to see. Afterward, potential Builders could create their proposal or find other team members to assist. They would then need to perform all the steps of the same proposal process as the "Self-Initiated Community Project Proposals" above.
Financier-Driven Project Requests (FDPR)
These are requests created by the Financiers (or Sipher Team acting as Financier), which either originate from either the Financiers themselves or from ideas shared by the community. These will follow the same request template as for CDPRs and will be posted for the community to view. Same as for CDPRs above, potential Builders can create their proposal for these requests, which would go through the normal proposal process described in the "Self-Initiated Community Project Proposals" above.
Alternatively, Financiers (or the Sipher Team) could directly sponsor a project or initiative, but this would happen outside of the proposal process given that it is being managed and funded externally.
