You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once an event becomes observed, we can safely raise the last observed nonce for all validators. This could prevent validators from being stuck trying to get old events after being offline for awhile. Also, since the event is already observed, having more validators attesting to it is just wasteful.
The text was updated successfully, but these errors were encountered:
# Related Github tickets
- VolumeFi#2159
# Background
When a claim is set to observed, update all validator nonces if they
have a lower last observed nonce.
NOTE: This only takes effect when a claim is successfully attested to.
The validators currently stuck will remain on their current nonces until
a claim is processed. To get them unstuck, we need
VolumeFi#2160
# Testing completed
- [ ] test coverage exists or has been added/updated
- [x] tested in a private testnet
# Breaking changes
- [x] I have checked my code for breaking changes
- [x] If there are breaking changes, there is a supporting migration.
Once an event becomes observed, we can safely raise the last observed nonce for all validators. This could prevent validators from being stuck trying to get old events after being offline for awhile. Also, since the event is already observed, having more validators attesting to it is just wasteful.
The text was updated successfully, but these errors were encountered: