Skip is an ecosystem aligned MEV solution for Tendermint. This repository contains a number of playbooks that can be used to apply Skip's software to an existing Tendermint node!
Playbooks here are meant to be compatible with the excellent set of Tendermint Playbooks provided by Polkachu, and should work out of the box.
These playbooks will enter the remote machine, clone the node software, patch Skip into the codebase, restart the daemon and then cleanup after itself. Almost everything is set up to work right out of the box.
The only assumption this playbook makes is that Tendermint node is run as a systemd daemon.
- Get an API Key from Skip here
- Setup
inventory.ini
To start, copy inventory.sample.ini to inventory.ini, and customize the IP addresses for the networks you wish to deploy on. Modify any config settings to suit the specifics of how SSH access to the remote machine is configured.
- Modify Variables
In the .yml file corresponding to the network you wish to join (ex. juno.yml) there are two variables you may need to change:
daemon- Leave this as is if you do not use Cosmosvisor, or change tocosmosvisorif you do.personal_peer_ids- Set this up if the node you are installing on is a sentry node, according to Skip's documentation
Additionally, you may want to glance over the other variables. For most systems, including one's deployed with Polkachu's playbooks, the default values should be up to date. If you happen to not anything out place (ex. wrong node or Skip version), feel free to send a PR!
- Deploy
You can deploy by running the playbook for the target network and specifying your API key:
$ ansible-playbook juno.yml --extra-vars skip_api_key=<your API key>This will install Skip on every host in inventory.ini that starts with the network name (ex. juno.yml would run on juno-sentry-1, juno-sentry-2 and juno-validator).
Tessellated contributes to projects across the proof of stake landscape.
If you find this project helpful, consider delegating to us in the future!