-
Notifications
You must be signed in to change notification settings - Fork 4.6k
Conversation
If we wanted to be extra careful, we could also disable the Commitment::Max until the "cluster confirmed root" queries are actually supported. If not, for that commitment level at least (just b/c of the implications) it feels safer to return a failure rather than a local root, as critical clients that are expecting Local root and cluster confirmed root should only diverge if there's some critical bug/attack that causes a few validators to commit down the wrong path. It hasn't happened to date, but just being extra careful here. Maybe @mvines can illuminate if there are further implications for restart any current partners using this call? |
Turning "max" into "root" for a time will be transparent to downstream users AFAICT. We made the distinction unilaterally to improve the safely of the results that "max" returns, not due to any partner request |
Awesome, thanks! |
Codecov Report
@@ Coverage Diff @@
## master #11188 +/- ##
=======================================
Coverage 82.1% 82.1%
=======================================
Files 318 318
Lines 74002 74007 +5
=======================================
+ Hits 60804 60816 +12
+ Misses 13198 13191 -7 |
Co-authored-by: Tyera Eulberg <[email protected]>
Pull request has been modified.
Problem
The bank at a given CommitmentLevel may not be in BankForks. See #11078
Summary of Changes