Keeper that lifts the hat and streamlines executive actions
Its purpose is to lift the
hatin DSChief as well as streamline executive actions.
lifta spell, that spell must have more approvals than the current
hat. The approvals of this spell can fluctuate and be surpassed by other spells, some of which could be malicious. This keeper "guards" the
hatby ensuring the spell with the most approval is always the
chief-keeperdoes this in order to maximize the barrier of entry (approval) to
lifta spell to the hat, thus acting as a "guard" against malicious governance actions.
While in operation, the
- Monitors each new block for a change in the state of executive votes
lifts the hat for the spell (
yay) most favored (
- Schedules spells in the GSM by calling
- Executes spells after their
etahas elapsed in the GSM by calling
chief-keeperinteracts directly with the
This keeper is run continuously, and saves a local database of
yays(spell addresses) and an
yay:etadictionary to reduce chain state reads. If you'd like to create your own database from scratch, first delete
bin/chief-keeper; the initial query could take up to 15 minutes.
- This project requires virtualenv to be installed if you want to use Maker's python tools. This helps with making sure that you are running the right version of python and checks that all of the pip packages that are installed in the install.sh are in the right place and have the right versions.
In order to clone the project and install required third-party packages please execute:
git clone https://github.com/makerdao/chief-keeper.git
git submodule update --init --recursive
tinydbisn't visible/installed through
./install.sh, simply run
pip3 install tinydbafter the commands above.
Make a run-chief-keeper.sh to easily spin up the chief-keeper.
--rpc-host 'sample.ParityNode.com' \
--network 'kovan' \
--eth-from '0xABCAddress' \
--eth-key 'key_file=/full/path/to/keystoreFile.json,pass_file=/full/path/to/passphrase/file.txt' \
In order to be able to run tests, please install development dependencies first by executing:
pip3 install -r requirements-dev.txt
You can then run all tests with: