Using Lock3r Network
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.
Disclaimer: Lock3r Network is yet to go under a full audit — We have near identical code to Keep3r on 1400 lines, which was audited by PeckShield. These contracts have been audited and reviewed, that does not mean that bugs can’t/won’t be present. When interacting with these contracts never interact with funds that you are not willing to lose.
Lock3r Network v1 contracts have been released;
A registry of the contracts can be found at;
Joining as a Lock3r
Navigate to lock3r.network click add input your amount LK3R and confirm with add
After the bonding period of 2 days you will be able to select activate.
Performing Jobs
You can view current available jobs, for now our UniswapV2Oracle is available under (Lock3, however more will be added, additional data will also be included on the website.
Lock3r jobs implement a function called work
As a simple locker, you only need to call work and you will receive LK3R.
For details on registering a job or additional information please visit the documentation
