@ethereum-alarm-clock/contracts
v1.0.0-rc.2
Published
Service to schedule Ethereum transactions that will be executed in the future.
Downloads
12
Readme
Ethereum Alarm Clock
Source code for the Ethereum Alarm Clock service
What is the EAC (Ethereum Alarm Clock)
The Ethereum Alarm Clock is a smart contract protocol for scheduling Ethereum transactions to be executed in the future. It allows any address to set the parameters of a transaction and allow clients to call these transactions during the desired window. The EAC is agnostic to callers so can be used by both human users and other smart contracts. Since all of the scheduling logic is contained in smart contracts, transactions can be scheduled from solidity.
Additionally the EAC faciliates the execution of this pool of scheduled transactions through a client. The EAC client continuously runs and searches for transactions which are scheduled to be executed soon then claims and executes them. For the EAC to be successful it depends on users who run execution clients. There are a few ways incentives for running these execution clients are baked in to the protocol itself, notably the claiming mechanism and the reward payment.
Running the tests
Tests have been ported to Javascript and can now be run using the Truffle Suite
Originally the test suite was written in Python using the Populus framework, these still exist for reference under the populus-tests/ directory. However, we have ported over the suite to use the Truffle framework since this may be more familiar to developers who know the Ethereum tooling in Javascript. These tests can be found in the test/ directory.
If you would like to run the test please set up your environment to use node v8 (lts/carbon), truffle v4.1.5 and the latest ganache-cli.
nvm use lts/carbon
npm i
npm i -g [email protected]
npm i -g ganache-cli
Start ganache-cli in a terminal screen by running ganache-cli
.
In another terminal screen run npm test
at the root of the directory. This will run the npm test script that
splits up the tests into different runtimes. The tests are split because the EAC is a moderately sized project and
running all the tests with one command has a tendency to break down the ganache tester chain.
Each time you run the tests it is advised to rebuild your build/ folder, as this may lead to bugs if not done. You
can do this by running the command rm -rf build/
.
Documentation
Documentation can be found on Read the Docs.
We are in progress of migrating the documentation to the Wiki.
Using the CLI
Please see the cli
repository for the commandline client.
Deployment
As we approach mainnet the EAC contracts are deployed on Ropsten, Rinkeby and Kovan.
Deployed version is 1.0.0-beta.6
You can find the address for each network in the networks folder.