lidofinance/lido-oracle

TX should stop if report seems to be suspicious (in DAEMON mode). FORCE env to override

Closed this issue · 0 comments

Currently DAEMON mode allows sending anything, no matter is the tx strange or normal. This is risky.
The daemon must log the warning and skip sending TX by default.

To simplify E2E tests (that have very specific numbers and timing), the FORCE option should be introduced to make TX enforceable.

  1. Base: daemon_v2 branch
  2. Cherry-pick proposed implementation from ba99a51
  3. Add FORCE flag
  4. Adapt tests