v0.3.0

What's Changed

Compatibility note

I added a compatibility table to the README so that you can easily check which client works with eth-duties.

Breaking Changes

• Flag --validator-file was renamed to --validators-file
• Shortcut flags like -v or -f were removed
• Comma separated validator indices/pubkeys for the flag --validators does not work anymore
  • Please use a space for separation
  • This has some side effects on a used docker compose (see compose example)
    • TL;DR: If you have many validators and rely on a compose it is recommended to use a validators file

New Features and Fixes 🎉

• The restriction to only get sync committee duties for 300 validators got fixed
• At start eth-duties filters out validators which are not labelled as active on chain
• You can now pass validator pubkeys
• You can also pass one or many indices/pubkeys with an alias which will be used for logging instead of the index/pubkey
• The logging behavior is now more customizable:
  • Replace indices with pubkeys in logging messages with --log-pubkeys
  • Customize colorful logging thresholds for warning (--log-time-warning) and critical messages (--log-time-critical)
  • Define the max. number of logged attestation duties with --max-attestation-duty-logs
• Use --mode to define running mode
  • Default will be the correct one for most users
  • The other modes are mostly for professional node operators (see here for a more detailed explanation)

Other Changes

• Update documentation by @TobiWo in #23
• minor typo by @ladidan in #37

Relevant feature and fix related PRs

• #25
• #31
• #33
• #34

New Contributors

• @ladidan made their first contribution in #37

Docker

Docker image can be found here

Full Changelog: v0.2.1...v0.3.0