top of page

The Upwork of Web3 

 

Deeplink is the proponent of the world’s first R&D portal on Ethereum. We are empowering developers, engineers alike, and DAOs to improve developer experience and software project management through a truly decentralized R&D platform built for scaled innovation and distributed engineering. 

 

We are implementing an Upwork-style platform where jobs are listed and anyone in the world can come and contribute AND get paid for it. This new portal will be the home of our research and development. It is an open and accessible platform where anyone can get real time progress updates on all our R&D work, and start contributing at the click of a button.

S67-BQmtDeIVGC5kgbOOziEoIiOxVucMU3noVPgEfmeR1dTobNYz2fJIyj0rC86T_zYOfIzF8sCPtv2lOr0d163WPW
THE UPWORK OF WEB3

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. 

nPQH5Nxq2YcLbz-L82jUq9w42OebpvFAy0-wnoJKaHOJUg4tGzCHWht4hNo1xKwzSFEf3Ix7o5_IPxWDT9WuBdsQwE
Addressing Pain points in Opensource and DAOs
Scalable and accountable project management
Empowering developers and engineers
Incentivizing developers and engineers as verified contributors

Good behavior as a verified contributor is rewarded with Dkeeper staking rewards. This adds bonuses to the work being done and keeps verified contributors motivated to continue growing the project. 

If a verified contributor is performing poorly then they can also be voted out. In turn, their Dkeepr will by disabled, causing all benefits to be shut off. Contributors that have been voted out can still work for the project and re-apply as a verified contributor. 

DAO Framework

The Research & Development portal uses a parent DAO that encompasses all of DeepLink. That DAO is then split up into smaller data departments called Child DAOs and populated with verified contributors. 

The Deeplink DAO is a decentralized autonomous organization, a bottom-up entity structure with no central authority. The Deeplink DAO is a decentralized autonomous organization, a bottom-up entity structure with no central authority. Members of a DAO, who own tokens of the DAO, and members can vote on initiatives for the entity. Smart contracts for the DAO are implemented, and the code governing the DAO's operations is publicly disclosed. Deeplink DAO serves as the parent or the protocol DAO. It allocates funds to the Child DAOs through a smart contract.

 

The Child DAOs on the other hand are the different departments within the protocol. Examples of Child DAO are the data department, blockchain department, DevOps, and machine learning. These departments have their participants and their projects, and each has its treasury and voting mechanism.

All these child DAOs have voters or participants with voting rights called verified contributors. So these individuals can access the DAO using their ERC20 and logging in to their wallet.

 

Deeplink DAO serves as the parent or the protocol DAO. It allocates funds to the Child DAOs through a smart contract.

 

The Child DAOs on the other hand are the different departments within the protocol. Examples of Child DAO are the data department, blockchain department, DevOps, and machine learning. These departments have their participants and their projects, and each has its treasury and voting mechanism.

All these child DAOs have voters or participants with voting rights called verified contributors. So these individuals can access the DAO using their ERC20 and logging in to their wallet.

 

Parent DAO and Child DAOs

The Research and Development Portal looks like a work management system where freelance developers are able to visit the platform, connect their Ethereum wallets, and begin working on available tasks. 

The portal would show a similar structure that of a traditional company wiki composing of departments we call child DAO, where the Parent DAO is Deeplink protocol itself. The child DAO’s are our different departments like data, blockchain, devOps and machine learning department etc.

Each of the child DAOs have their own participants, projects, treasury, and voting mechanism. All these child DAOs are part of the parent DAO or the Deeplink DAO. 

 

Each child DAO has voters or participants with voting rights called contributors and these individuals are listed as ERC721 wallet holders. Their job is to create, monitor proposals, approve proposals, and work in the department to ensure everyone will work collaboratively to execute their department objectives.

 

This splits up the work between verified contributors who organize tasks and maintain progress. Contact links to verified contributors are provided along with a public calendar so that developers can join meetings to discuss the project. 

Essentially, clicking on any department will show a business requirement document or the job details, approved budget, deadlines, and the contributors.

Funding is pre-loaded onto the platform to ensure that the developer will be paid via a smart contract. This avoids the issue of clients that refuse to pay because the pay is already set up to be given to the freelance developer upon completion of the tasks.

4zZXi0XlZYF2I1TmV3aDCw82DQGN2EPwo8AslOTJRKrrcWpIMtw58N8rnwtDLf6fhA_i-a1QkGnMMpAPAYMdLe6jzz
Incentivizing developers and engineers as verified contributors
DAO Framework
Parent DAO and Child DAOs
Proposals

A verified contributor can create a proposal by connecting through their metamask wallets and going into their dashboards. The proposal can be structured with a title, background, purpose, proposed budget, deadline, proposed team members, and detailed tasks.

 

The verified contributor can create this proposal for anyone to take as a project, or assign to himself. Once a proposal has been submitted, it appears as a new proposal for the governance or community to vote for within the verified contributor’s respective department or child DAO. As mentioned, a child DAO has their own ecosystem.

 

When one submits a proposal, the proposal appears in the “proposals draft” where anyone can see number of votes and approval status. In a department of 5 people, in terms of voting, the vote for a proposal must be or exceed 33%. If there are ten contributors in a department/child DAO, only 3 votes/signatures are needed. If there are a hundred members, 33% of votes is needed. The percentage can be lowered down to 20% to keep it more efficient.  In Yearn governance, we can see a tab for proposals with the number of votes, etc. 

 

The proposer can talk to the verified contributors and personally say “Hey guys, can you approve this?” Once the proposal is approved and is live, it will be visible to everybody and the public.  If you're the developer, you can create this and assign it to yourself. 

Live Proposals/Live tasks

vPtdLTolv_ZrSqQF40UqKpjFT24QeC2g9jql8DbVTD0xHrWYBdbNmTaHZArCrVcQuq35R9N_N7RsVIl4wSdx2uKAol
Proposals

DAO R&D Portal Workflow from Proposal to Completion

TZnZb5nNWJh-H4OI3fIeP8MnCd6weNV0jsCMV9d97dudh1FNHBlakXFaSFGlx_Y690v0f7W1zDyEPmI3-gyFLeGs6a
DAO R&D Portal Workflow from Proposal to Completion

Diagram 1.0 

 

  1. The flow starts when one of the verified contributor submits a proposal. In this example, let us name the proposer Sarah. 

  2. She then submits a proposal with some basic details like the title, deadline, budget, tasks and project details (text, graphs, videos) and relevant link.

  3. Her proposal will be displayed on “Proposal Drafts” and will be viewable by the other verified contributors AND the public/  community contributors

  4. Other verified contributors approves the proposals that comes in the “Drafts”. The proposal needs to get 33% of vote to pass as a live task/approved proposal

  5.  An approved proposal goes to the “Live R&D page”. Anyone can take the approved proposals as a job. This includes, the proposer, VC, or the public

  6. If VC proposal is approved, it also is a signal for the Parent DAO treasury to move selected assets from ParentDAO to Temporary Holding Escrow. The main Deeplink DAO or the parent DAO allocates funds to the child DAOs. The child DAO will then have access to the capital, and they will manage the fund for their tasks and goals. Every specific task has a plan and budget. So, the Deeplink treasury or the main treasury, sends money to the escrow contract or the treasury of the child DAOs. The main Deeplink DAO has $10,000, then people who control or manage Deeplink can allocate capital to each department, e.g., data departments. In the data department, once the funds are received, the participants within that child DAO have full access to that capital. They will manage the capital for their tasks and their goals. Every specific task is well documented with a budget proposed and goes through a way that the community can review and approve it first.

  7. Taking on jobs/ live tasks is on a first come first serve basis among the proposer, verified contributors and public contributors

  8. When the job is completed, it will again be reviewed by the verified contributors and approve it by signing using their wallets. When it gets 33% approval from the verified contributors, the job will be accepted and the money on escrow will go directly to the ERC20 wallet of the one who worked on the job.

 

Expansion and Additional Frameworks

Our further study and implementation involves some new functionalities of the child DAO. We are introducing a voting mechanism to expedite the processes and dispute resolution within departments or child DAOs. Just like a normal company where it has departments that is responsible for their own management, introducing a child DAO that runs independently without interfering with the other departments allowing it to have their own governance, would be able to operate as a small entity without the disruption of other departments. With this, we are expecting an improvement in efficiency, scaled engineering, dispute resolution, and smooth engineering.

 

Another feature of the child DAO is that it can designate a verified contributor to recruit every 6 months. This would encourage VCs to hire for their own department’s requirements. They can serve as their own HR managers that allow them to vote and accept new members of the team without the need for a management or administration. Doing so would also incentivize these VCs. If you are a part of the data department or data child DAO, you can replicate yourself by giving the same privilege, capability, and rights to a new recruit. Essentially, we will be minting for VCs every 6 months.

 

Further expansion of the Research and development DAO portal is done by making the framework open source. By doing so, other projects will be able to adopt the same system implemented by Deeplink and allow developers to take ownership of their work giving future open source projects the ability to distribute engineering and scale for innovation.

Expansion and Additional Frameworks
bottom of page