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
After the merge of FuelLabs/fuel-core#2715, we are able to read the current_consensus_parameters_version field in every response the same way we're doing for
This can enable us to re-evaluate our auto refetching strategy.
The text was updated successfully, but these errors were encountered:
nedsalk
changed the title
Read consensus parameters version from every node response
Read consensus parameters version from every gql response
Mar 3, 2025
This proved to be impractical and not worth pursuing. There's no guarantee any transaction will occur in long-lived applications, and our automatic 1m interval still needs to be in place, which is sufficient.
The Provider auto-refetch strategy per se was fixed via:
After the merge of FuelLabs/fuel-core#2715, we are able to read the
current_consensus_parameters_version
field in every response the same way we're doing forThis can enable us to re-evaluate our auto refetching strategy.
The text was updated successfully, but these errors were encountered: