How do you feel about Keep4r today?
Vote to see community results
Launched on 2 November 2020, Keep4r (KP4R) is led by a team based in the U.K. Keep4r Network describes itself as an improved fork of the Keep3rV1 network. The team seeks to improve upon the governance and usability of Keep3rV1, by allowing users to bond and reward jobs directly with ETH and DAI. KP4R holders are rewarded with a share of all network fees.
It had a $5 million trading volume on UniSwap on the first day and $ 6 million on the second day. KP4R received a smart contract audit from Certik. “All issues have been logged and updated on Github. No critical vulnerabilities or major bugs found.” Check audit: https://shield.certik.foundation/projects/keep4r
A Keeper is the term used to refer to an external person and/or team that executes a job. This can be as simplistic as calling a transaction – usually a smart-contract call, or as complex as requiring extensive off-chain logic. The scope of Keep4r allows users to register contracts as jobs for keepers, and keepers to register themselves as available to perform jobs. It is up to the individual keeper to set up their DevOps and infrastructure and create their own rules based on what transactions they deem profitable.
A Job is the term used to refer to a smart contract that wishes an external entity to perform an action. They would like the action to be performed in "good will" and not have a malicious result. For this reason, they register as a job, and keepers can then execute on their contract.
To join as a Keeper you call bond(uint) on the Keep4r contract. users do not need to deposit any DAI or ETH tokens to join as a Keeper, so they can join with bond(0). There is a 1-day bonding delay before you can activate as a Keeper. Once the 7 days have passed, you can call activate(). Once activated, the lastJob timestamp will be set to the current block timestamp.
A job can be any system that requires external execution, the scope of Keep4r is not to define or restrict the action taken, but to create an incentive mechanism for all parties involved. There are two cores ways to create a Job;
Some contracts require external event execution, an example for this is the harvest() function in the yearn ecosystem, or the update(address,address) function in the uniquote ecosystem. These normally requires 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 (something like update(address,address) in uniquote, which needs to be executed, but not risk to execution), and harvest() in yearn, which can be exploited by malicious actors by front-running deposits.
For no, or low risk executions, users can simply call Keep4r.isKeeper(msg.sender) which will let users know if the given actor is a keeper in the network. For high, sensitive or critical risk executions, users can specify a minimum bond, minimum jobs completed, and minimum Keeper age required to execute this function. Based on these 3 limits users can define their own trust ratio on these keepers.
KP4R is a governance and staking coin, allowing holders to vote, and propose jobs as well as collect a % of the network fees.
|24h Low / 24h High|
|Market Dominance||Keine Daten|
|Fully Diluted Market Cap||Keine Daten|
|Yesterday's Low / High|
|7d Low / 7d High|
|30d Low / 30d High|
|90d Low / 90d High|
|52 Week Low / 52 Week High|
Nov 03, 2020 (2 months ago)
Dec 26, 2020 (23 days ago)
|ROI (Keep4r)||Keine Daten|
|Maximale Versorgung||Keine Daten|