Provider re-requesting chain + node config unnecessarily

[petertonysmith94]

Summary

We have logic to re-fetch the chain + node info, given the consensus parameters change (indicating a fuel-core update):

fuels-ts/packages/account/src/providers/provider.ts

Lines 1237 to 1253 in 3af8692

	const {
	consensusParameters: { version: previous },
	} = chainInfo;
	const {
	chain: {
	latestBlock: {
	header: { consensusParametersVersion: current },
	},
	},
	} = await this.operations.getConsensusParametersVersion();
	// old cache? refetch.
	if (previous !== current) {
	// calling with true to skip cache
	await this.fetchChainAndNodeInfo(true);
	}

We are comparing two different version definitions, causing re-fetches of the chain info every 1 minute, irrespective of whether the node has been updated.

From the chain

The version from the chain info returns V1 (on mainnet).

query ConsensusParameter {
  chain {
    consensusParameters {
      version
    }
  }
}

From the getConsensusParametersVersion

The version from the chain info returns 5 (on mainnet).

query GetConsensusParametersVersion {
  chain {
    latestBlock {
      header {
        consensusParametersVersion
      }
    }
  }
}