The Lock3r Network is a decentralized protocol designed to facilitate efficient and secure management of liquidity in decentralized finance (DeFi) ecosystems. It is closely related to KeeperDAO, as Lock3r Network is essentially the infrastructure that enables KeeperDAO to function.
Who We Are
Here are some key details about the Lock3r Network:
Liquidity Management: The primary function of the Lock3r Network is to manage liquidity across various DeFi protocols and platforms. It achieves this by deploying "keepers," which are automated bots or scripts that perform specific tasks such as providing liquidity, executing trades, or maintaining the stability of DeFi protocols.
Incentive Mechanisms: Lock3r Network provides incentives to keepers for their services. Keepers may earn rewards in the form of tokens or fees for their participation in liquidity provision and other activities that contribute to the health and efficiency of the DeFi ecosystem.
Decentralized Governance: Similar to KeeperDAO, Lock3r Network likely incorporates decentralized governance mechanisms to enable community members to participate in decision-making processes. This allows stakeholders to vote on proposals, upgrades, and changes to the protocol, ensuring its evolution in a decentralized manner.
Interoperability: Lock3r Network may be designed to work seamlessly with multiple DeFi protocols, enabling keepers to interact with various platforms and assets across the decentralized finance landscape.
Class and Culture
Overall, Lock3r Network plays a crucial role in the operation and optimization of DeFi ecosystems by providing infrastructure for efficient liquidity management and incentivizing participation from keepers.
A Locker in our project is the term used to refer to an external person and/or team that executes a job, ordinarily these we're called Keepers. This can be as simplistic as calling a transaction, or as complex as requiring extensive off-chain logic. The scope of Lock3r network is not to manage these jobs themselves, but to allow contracts to register as jobs for lockers, and lockers to register themselves as available to perform jobs. It is up to the individual locker to set up their devops and infrastructure and create their own rules based on what transactions they deem profitable.
Registering a Job
A job can be any system that requires external execution, the scope of Lock3r 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;
Registering a Job via Governance
If you prefer, you can register as a job by simply submitting a proposal via Governance, to include the contract as a job. If governance approves, no further steps are required.
Registering a Job via Contract Interface
You can register as a job by calling addLiquidityToJob(address,uint) on the Lock3r 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 address in the function arguments. You are limited to submit a new job request via this address every 10 days.