gm friends
There are a lot of unanswered questions in this RFC. Its purpose at this stage is to relay and seek feedback on an opportunity that has become available to the DAO to see if the idea has support and discuss how we might approach it if it does.
Topics not covered included: architecture, team, costs
What is the Developer DAO RPC Gateway?
The idea is for the DAO to build an RPC Gateway in the POKT Network ecosystem to give cheap access to high-quality RPC endpoints, give members an opportunity to build something for the DAO and help sustain the DAO with a consistent revenue stream.
Imagine your app/wallet was powered by chain.rpc.developerdao.com
Why build an RPC Gateway for Developer DAO?
Our preferred RPC Partner POKT Network has made it possible for teams to deploy their own RPC gateways on-top of resilient and high-performance decentralised infrastructure at a fraction of the set-up (and running cost) compared to centralised alternatives on a pay-per-use model. This unlocks a realistic opportunity to create an RPC product to compete using the DAO’s strengths: Brand and Distribution.
Some of the benefits of creating a Developer DAO RPC Gateway that are aligned with our mission, values and goals:
- Dog Food and support POKTs efforts to decentralise core blockchain infrastructure
- Provide members the opportunity to work on a commercial open source project to help develop their skills and earn returns if successful.
- Build a meaningful project in the DAO that both showcases what we can do and helps to fund the DAO’s long-term sustainability.
POKT Network removes the vast majority of the upfront costs associated with building and running RPC Node infrastructure, leaving the remaining primary costs as the service layer (SaaS UI/Account management etc.), customer acquisition and support.
This unlocks a far more achievable path towards profitability, particularly given we have an existing brand and distribution to the products target audience.
How do we create a Developer DAO RPC Gateway?
There are 3 ways we could approach this highlight in the table below in order of complexity and overhead - easiest/cheapest to hardest/most expensive.
Option | Description |
---|---|
Build on top of an existing Gateway | Build a SaaS application on top of Grove and or Nodies Gateway that manages user accounts, authentication & API keys, payments, but refers all traffic to their gateways. |
Build our own sovereign gateway using GatewayKit | Everything above plus build and manage our own RPC Gateway using the OS GatewayKit being developed by Nodies and POKT |
Build our own sovereign Gateway from scratch. | Build everything from scratch. |
Potential Business models
Model |
---|
Flat monthly fee for all users |
Flat monthly fee for non-members, discounted accounts for members |
Flat monthly fee for non-members, free accounts for members rolled into the idea of a DAO NFT Membership (this would only work in a world where membership were recurring to cover the on-going costs of providing the RPC) |
*This assumes we don’t follow the high-cost growth model of centralised RPCs and charge for all accounts from the get go as we don’t currently have the capital to fund such a model
Potential Funding Routes
Funding | |
---|---|
Revenue split for contributors on project | % split of revenue generated from sales |
Grant funding | POKT Quick Grants POKT RPF/POP - Gateway Demo Other grant programs (we may be able to persuade some foundations to issue small grants to support the work, maybe in return for discounts for their token holders for example) |
Retroactive public goods funding | POKT Network RPGF Optimism RPGF |
Combination of the above | Combination of these approaches |
As well as general feedback on the idea and options presented, it would be great to hear from the community on how we might approach such a project. One interesting option could be opening up an RFP process for members to pitch to create it with a vote.
Thanks to @mannyornothing for helping me put this together & @Billyjitsu for participating in discussions with POKT, Grove and Nodies.
Tagging @Crypdough.eth as he asked to be kept in the loop