Documentation
Documentation
Arcron runs scheduled contract calls that nobody owns. Escrow a fee against a schedule, and any account on the network can earn it by making the call on time.
Start with Integrating if you have a contract you want called on a schedule, or with Running a keeper if you want to be the one making the calls and collecting the fees.
Building on it
- Integrating
One method, and everything else you need to know about it. The hook shape, authorization, the failure modes that quietly stop an upkeep being serviced, and the pull pattern every worked example here is built on.
- How it works
What a keeper actually does, what an execution costs both sides, and what an Arcron-triggered call can and cannot reach.
Running it
- Running a keeper
Anyone can run one and be paid for it. Where to put it, what each option really costs, and what the account needs to start.
- Deploying
From a checkout to a running deployment on any network, plus updating a live contract, giving that up permanently, and holding the key in a multisig.
Reference
- Release stages
alpha, beta, rc and MainNet. What is frozen at each, what is at stake, and the gate that ends it.
- Security
The threat model, the risks accepted on purpose, and how to check a deployment yourself rather than take our word for it.
A warning worth reading first
This is alpha, TestNet only, and unaudited. No third party has reviewed the contracts. Treat TestNet as a demonstration and do not escrow anything you would mind losing. Security says what is known, what is accepted, and how to verify a deployment for yourself.