Keep3rb: First Keeper Network on Binance Smart Chain

The Developer role is a highly specialized one, and often, finding the right fit for your project can be difficult. Keep3rb solves this problem of connecting projects to developers using a freelance platform on the Binance Smart Chain Network.

About Keep3rb

Keep3rb Network is a decentralized Keeper network built on the blockchain for projects that need external DevOps and external teams to find Keeper jobs.

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.”  – Wikipedia 

It will be the platform where project teams can connect easily with Devops and external DevOps teams. DevOps(Keepers) can easily connect with the project team(Jobs) needing the service by simply setting up their profile on the network while getting fairly rewarded.

Key Features

Development and IT operations (DevOps)



Project Component

The roles/positions on the Keep3rb network are well defined for the participating individuals and teams needing DevOps. The functions are well spelled out, including the steps to each action:

KeepersKeepers are the term used to refer to the external person/team used to execute a job; they can be bots, scripts, other contracts, or simply EOA accounts that trigger events. This can be as simple as calling a function or as complex as requiring extensive off-chain logic. Whatever the expected action of a job will be listed as the work required. Users can then register jobs as Keepers and Keepers to register themselves as available for the job.

How to become a Keeper

To join as a Keeper, you need to call bond(uint) on the Keep3rb contract. You do not need to have KPR tokens to participate as a Keeper; you can join with bond(0). There is a 3-day bonding delay before you can activate as a Keeper. Once the three days have passed, you can call activate(). Once activated, your lastJob timestamp will be set to the current block timestamp.

Jobs: Jobs is the term used to refer to a smart contract that requires external DevOps or a team to work on it. The action needs to be performed in goodwill and not as a malicious act to harm the project. For these reasons, they are registered as jobs, and Keepers can take on the action.

How To Register A Job

Keep in mind that the Keep3rb network does not get in the way of the job. They don’t define or restrict the action taken, hence its decentralized nature. There are incentive mechanisms for all parties involved to ensure tasks are carried out efficiently. There are two core ways to create a job;

Registering a job via Governance 

Registering a job via Contract Interface

Governance: Projects can register a job via Governance if they prefer by simply submitting a proposal via Governance to include the contract as a job. If Governance approves, no further steps are required.

Contract Interface: Registering a job via contract interface requires projects to go through a few steps. For example, You can register as a job by calling addLiquidityToJob(address,uint) on the Keep3rb contract. You must not have any current active jobs associated with this account. Calling addLiquidityToJob(address,uint) will create a pending Governance vote for the job specified by the address in the function arguments. You are limited to submit a new job request via this address every 14 days.

Job Interface

Some contracts require external event execution; an example is the harvest() function in the yearn ecosystem or the update(address, address) function in the uniquote ecosystem. These usually require a restricted access control list. However, these can be difficult for fully decentralized projects to manage, as they lack DevOps infrastructure.

These interfaces can be broken down into two types, no risk delta and harvest. The first is similar to an update(address, address) in uniquote, which has no risk to execution.  Harvest(), seen in yearn, can be exploited by malicious actors by front-running deposits. Complete details of how these codes are executed are mentioned in this Medium post.

Job Credits

A job has a set amount of credit they can award Keepers. You do not need to purchase KP3RB tokens to receive credits. Instead, you are required to provide KP3RB-BNB liquidity on PancakeSwap. For specific jobs, users can also provide liquidity using CheeSwap. This will give you credits equal to the number of KPR tokens in the liquidity you provided.

You can remove your liquidity at any time, so you do not have to keep buying new credits. Your liquidity provided is never reduced, and as such, you can remove it whenever you no longer would like a job to be executed.

To add credits, you simply need to have KP3RB-BNB LP tokens; you then call addLiquidityToJob(address,uint), specifying the job in the address and the amount in the uint. This will then transfer your LP tokens to the contract and keep them in escrow. You can remove your liquidity at any time by calling unbondLiquidityFromJob(); this will allow you to remove the liquidity after 14 days by calling removeLiquidityFromJob().

Source :

Leave a Reply

Your email address will not be published. Required fields are marked *