Unlike any other development platform, ours is built on the Ethereum blockchain. This provides unique functionality by integrating payments and immutability. The portal is divided into departments which are mini-DAOs, and work is listed under their relevant department. Each department will have a collection of verified contributors (VC). These VCs are identifiable by a D-Keeper NFT. VCs are responsible for creating jobs, allocating funding, verifying completed work, and adding or removing other VCs. A job is listed within a department, and publicly accessible. Every job is posted as a business requirement document (BRD) which will outline a set budget, scope of work, and deadline; everything a developer needs to get the job done. Because the portal is integrated with the Ethereum blockchain, contributors can be confident that their work will be recognized, and they will be paid. When funding is allocated to a job, it is sent to a smart contract to be held in escrow until the job is completed, where it will then be sent to the contributor; no need to worry about chasing up unpaid invoices or dodgy dealings. Listed jobs will also link to the social channels, such as discord, for that department, where the public can engage with VCs and other contributors. Users can also book meetings with VCs if they feel it is required. 

​

Addressing Pain points in Opensource and DAOs

​

Open source communities have a variety of problems when it comes to development and coordination. Challenges exist when holding contributors accountable and adhering them to any sort of laws. By implementing a DAO structure, core teams are able to assemble and create a structure that enables them to become the final decision makers for a variety of responsibilities. 

However, we need an environment to leverage the developer experiences where developers can perform better, while maintaining a truly decentralized governance. These are issues that we specifically addressed with our R&D development portal. We aim to  improve the developer experience, while maintaining some control of the development, and introduce mechanisms to incentivize proper behavior and developer empowerment. Importantly, we wanted this portal to scale as we do, and not limit our ability to grow or be agile. 

​

​

Scalable and accountable project management

​

A big problem in web3 is scalability. Often it is discussed in the context of technology capabilities and throughput. However, it is the context of scalable democratic decision making that is relevant here. As a project and its community grow in size, it becomes harder to make decisions in the interest of the project. As decision-making power spreads to more people, and becomes concentrated in parties with lots of project tokens, the interests of the project won’t always align with the interests of the parties with power, and situations can arise where the majority of voters make a decision that is harmful for the project in the long run. Additionally, voting conducted on a tokenholder basis is a waste of resources, in terms of gas fees, but also because these important decisions need to be advertised so tokenholders are aware which drains a project’s resources. Often it becomes a situation of “too many chefs in the kitchen”. 

It is for this reason that we introduced the concept of verified contributors (VC). VCs are trusted members of the community that are responsible for the decisions of a department. VCs are identified by a D-Keeper NFT. The voting power of each VC is equal, and not weighted by any other factor, such as the number of native tokens they have. The proper behavior of VCs is incentivized by their D-Keeper NFT, which entitles them to staking rewards, and bonuses. VCs are able to vote another VC out, and nominate other community contributors to become a VC (This power is limited to one nomination per VC every 6 months). By keeping the voting power in a small subset of the community which are trusted, as well as incentivized, to do the right thing, it is much easier for our project to scale, make the right decisions, and remain agile. Importantly, having a subset of the community that are invested in the project’s success makes project management and coordination much easier too.

​

​

Empowering developers and engineers

​

Empowering developers is crucial to scaling engineering. There are a variety of obstacles within centralized businesses that prohibit developers from owning their work and sharing it. Using a platform like ours, developers will have a more liberating experience that provides access to job postings with complete transparency.

​

Freelance developers are often overlooked or treated unfairly because of how diluted the market is. It can be difficult to find work, and there are lots of issues and overhead work that must be done to ensure the job is done properly AND you are paid. We wanted to specifically address these issues, and offer the freelance developer a much better experience in the hopes of attracting the best talent to our project. One major issue that developers deal with is the protection of previous work by NDAs. These kinds of arrangements prevent developers from showcasing amazing tech that they have worked on or built. Our development portal specifically addresses this issue and doesn’t just keep our work public, it also records you, the developer, as the person who completed the work and this record is immutably stored on-chain. This enables developers to share the BRDs of their completed jobs within their portfolio. 

This was already possible with some open source work by sharing your contributions through GitHub, but the added benefit with our portal comes with the BRDs, which are concise, descriptive documents outlining your work in a way that non-technical people, such as hiring managers, can understand. We believe this will empower the developer by giving them the ability to build better portfolios.