Skip to content

Latest commit

 

History

History
85 lines (55 loc) · 2.71 KB

CONTRIBUTING.md

File metadata and controls

85 lines (55 loc) · 2.71 KB
Raw

Contributing guide

Welcome to the MEV-Boost project! We just ask you to be nice when you play with us.

Please start by reading our code of conduct.

Set up

Install a few dev dependencies for make lint: https://github.com/flashbots/mev-boost/blob/develop/.github/workflows/lint.yml#L29-L37

Look at the README for instructions to install the dependencies and build mev-boost

Alternatively, run mev-boost without build step:

go run . -h

# Run mev-boost
./mev-boost -goerli -relay-check -relay URL-OF-TRUSTED-RELAY

Note that you'll need to set the correct genesis fork version (either manually with -genesis-fork-version or a helper flag -mainnet/-goerli/-sepolia/-holesky).

Test

make test
make lint
make run-mergemock-integration

Testing with test-cli

test-cli is a utility to run through all the proposer requests against mev-boost+relay. See also the test-cli readme.

Testing with mergemock

Mergemock is fully integrated: https://github.com/protolambda/mergemock

Make sure you've setup and built mergemock first, refer to its README but here's a quick setup guide:

git clone https://github.com/protolambda/mergemock.git
cd mergemock
go build . mergemock
wget https://gist.githubusercontent.com/lightclient/799c727e826483a2804fc5013d0d3e3d/raw/2e8824fa8d9d9b040f351b86b75c66868fb9b115/genesis.json
openssl rand -hex 32 | tr -d "\n" > jwt.hex

Then you can run an integration test with mergemock, spawning both a mergemock relay+execution engine and a mergemock consensus client pointing to mev-boost, which in turn points to the mergemock relay:

cd mev-boost
make run-mergemock-integration

The path to the mergemock repo is assumed to be ../mergemock, you can override like so:

make MERGEMOCK_DIR=/PATH-TO-MERGEMOCK-REPO run-mergemock-integration

to run mergemock in dev mode:

make MERGEMOCK_BIN='go run .' run-mergemock-integration

Code style

Start by making sure that your code is readable, consistent, and pretty. Follow the Clean Code recommendations.

Send a pull request

  • Your proposed changes should be first described and discussed in an issue.
  • Open the branch in a personal fork, not in the team repository.
  • Every pull request should be small and represent a single change. If the problem is complicated, split it in multiple issues and pull requests.
  • Every pull request should be covered by unit tests.

We appreciate you, friend <3.

For the checklist and guide to releasing a new version, see RELEASE.md.