v2.3.5

New Feature

In an alert config, users can use consecutive_missed_exclude_preactions to include or exclude the cases where a validator submits prevote and precommit, but the proposer does not include it in the block for the consecutive missed blocks alert. This is helpful for chains like Celestia where validators only include 2/3 of the votes (enabled by V6).

What's Changed

• #52 fix the similar issue in Namada provider by @gluckzhang in #54
• fix stake change comparison by @gluckzhang in #55
• #56 exclude precommit and prevote for missing consecutive blocks alert by @gluckzhang in #57

Full Changelog: v2.3.4...v2.3.5

v2.3.4

What's Changed

• #46 fix panic when reward arrays are empty by @gluckzhang in #47
• #43 fix the issues found by gosec by @gluckzhang in #48
• #49 use unique id for alerts and customize some alert messages by @gluckzhang in #50
• #52 trigger governance proposal alert even if some query requests to RPC endpoints fail by @gluckzhang in #53

Full Changelog: v2.3.3...v2.3.4

v2.3.3 Alert Config Improvements and Non-Operational Metrics

Highlights

• Remind unvoted proposals periodically, defined by governance_alerts_reminder_interval in the config
• Governance proposal alert messages contain the deadline information now (Namada is not supported yet)
• Simplified alert configurations that also support overriding, see https://github.com/Firstset/tenderduty/blob/main/example-config.yml#L32 for the details
• Include more information like stake, voting power, unclaimed rewards, projected 30-day rewards in a fiat currency (using CoinMarketCapAPI), see https://github.com/Firstset/tenderduty/blob/main/example-config.yml#L23 for setting up a CoinMarketCapAPI token and conversion rules

Breaking Changes

• Now each chain's alert configuration is very much simplified because the new version contains a mandatory default_alert_config section in the config yaml file. To use this version, please refer to https://github.com/Firstset/tenderduty/blob/main/example-config.yml#L32 to update your config file. Once the default_alert_config is set, you don't need to duplicate lots of alert configs in each chain's alerts section, unless you need to override some alert configs.
• If you would like to enable unclaimed rewards alerting, and the projected 30-day rewards feature in the frontend, you need to have a CoinMarketCap API token (the free tier is sufficient as Tenderduty caches the token prices), and then adjust the config based on the example here and here

What's Changed

• Add chain id to chain name in alerts by @kinrokinro in #18
• #16 fix false-positive proposal alerts by @gluckzhang in #19
• #15 support self-signed certificates for various connections by @gluckzhang in #20
• #9 resend unvoted proposal alerts after a period of time by @gluckzhang in #21
• feat: add deadline information to a governance alert message by @gluckzhang in #23
• #22 feat: configure each alert channel's severity threshold by @gluckzhang in #25
• Readme updates by @bernatfp in #28
• Update README.md by @bernatfp in #29
• add a static file folder for Tenderduty query fallbacks by @gluckzhang in #30
• #27 and #24 feat: price conversions and non-operational metrics by @gluckzhang in #31
• fix: the cache logic in coinmarketcap-api-client by @gluckzhang in #32
• #24 now we support querying rewards and voting power for Namada by @gluckzhang in #33
• improve price conversion query by ignoring invalid slug values by @gluckzhang in #34
• Fix tenderduty caddy port by @dylanschultzie in #35
• #24 feat: support displaying validator APR by @gluckzhang in #36
• Fix header alignment in table by @bernatfp in #39
• Improve readme with latest changes by @bernatfp in #40
• fix early return never being executed and some typos by @gluckzhang in #41
• Support default alert config by @gluckzhang in #42
• #24 calculate each validator's projected 30-day rewards by @gluckzhang in #45

New Contributors

• @kinrokinro made their first contribution in #18
• @dylanschultzie made their first contribution in #35

Full Changelog: v2.3.2...v2.3.3

v2.3.2 Governance Alert Configurable and UI Improvements

What's Changed

• #13 fix: the issue that a chain-stalled alert is not resolved by @gluckzhang in #14
• Dashboard reskin by @bernatfp in #12
• Add governance alerts configuration and handling for unvoted proposals by @ericjohncarlson in #17
  • Now you can enable or disable governance proposal alerts for each chain in the config. See the example config here: https://github.com/Firstset/tenderduty/blob/main/example-config.yml#L120

New Contributors

• @bernatfp made their first contribution in #12
• @ericjohncarlson made their first contribution in #17

Full Changelog: v2.3.1...v2.3.2

v2.3.1 Fix Websocket Connection When Valcons Address Is Used as valoper_address in Config

What's Changed

• #10 fix: websocket does not work if the valcons address is used by @gluckzhang in #11

Full Changelog: v2.3.0...v2.3.1

v2.3.0 Namada Support and Governance Proposal Monitoring

This release contains the followig two key improvements:

Governance proposal monitoring

• Receive alerts when there are proposals in voting period and the validator has not voted on. The alert is resolved once the validator has voted.
• Unvoted proposals are tracked and reported in the dashboard.
• A Prometheus metric is also added to monitor the number of unvoted proposals.

Improved support for Namada.

• Proper reporting of otherwise missing information such as the Moniker, uptime data or slashing threshold.