chore: update internally used chain config

[Dhaiwat10]

• Closes Update internally used Chain Config #3330

Summary

This PR updates our internally used chain config to match the one specified here

Checklist

• All changes are covered by tests (or not applicable)
• All changes are documented (or not applicable)
• I reviewed the entire PR myself (preferably, on GH UI)
• I described all Breaking Changes (or there's none)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fuels-template	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 30, 2024 10:22am
ts-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 30, 2024 10:22am
ts-docs-api	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 30, 2024 10:22am

[petertonysmith94]

@Dhaiwat10 will the differences between the local and ignition chains cause issues here? Consensus parameters version for local is V2 and for ignition (and other configs) it is V1.

[Dhaiwat10]

@petertonysmith94 That's a good point. I'm not really sure which one we are supposed to use. I heard from one of the team members that apparently the local config specified by them hasn't been updated in a long time. I'm not sure why the local is V2 and not mainnet, either.

Gonna try a few things and get back with some more context for our sync.

[Torres-ssf]

It seems our local test chain config uses settings from the Testnet upgrade number 6

Maybe we should go for either the latest Testnet upgrade (upgrade number 9) or even the lastest Mainet Upgrade

Both of them seem to be using the V2 for consensus_parameters already.

This will require changes only on our side if I am not mistaken, and only on TS types related to test helpers.

It seems that even though these versions are being updated on the chain config JSON for main-net and test-net, fuel-core always resolves them to V1 when returning the response for the graphQL queries. I believe this is due to backward compatibility reasons.

[Dhaiwat10]

@Torres-ssf can you check the changes I made and if they make sense?

[codspeed-hq]

CodSpeed Performance Report

Merging #3420 will degrade performances by 54.42%

_{Comparing dp/update-chain-config (d65bcf3) with master (ef94263)}

Summary

❌ 1 regressions
✅ 17 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	master	dp/update-chain-config	Change
❌	should successfully transfer a single asset between wallets (x20 times)	61.5 ms	134.9 ms	-54.42%