Skip to content

Read consensus parameters version from every gql response #3746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nedsalk opened this issue Mar 3, 2025 · 3 comments
Closed

Read consensus parameters version from every gql response #3746

nedsalk opened this issue Mar 3, 2025 · 3 comments
Assignees
Labels
feat Issue is a feature

Comments

@nedsalk
Copy link
Contributor

nedsalk commented Mar 3, 2025

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.

@nedsalk nedsalk changed the title Read consensus parameters version from every node response Read consensus parameters version from every gql response Mar 3, 2025
@nedsalk nedsalk added chore Issue is a chore feat Issue is a feature labels Mar 19, 2025 — with Linear
@nedsalk nedsalk removed the chore Issue is a chore label Mar 19, 2025
@petertonysmith94 petertonysmith94 self-assigned this Mar 20, 2025
@arboleya
Copy link
Member

@arboleya
Copy link
Member

arboleya commented May 2, 2025

Note to self.

onEvent: (event) => {
Provider.setCurrentBlockHeight(
this.urlWithoutAuth,
event.extensions?.current_fuel_block_height as number
);
},

@arboleya
Copy link
Member

arboleya commented May 7, 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:

@arboleya arboleya closed this as completed May 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feat Issue is a feature
Projects
None yet
Development

No branches or pull requests

3 participants