chore: update chain-id

[w-woloszyn]

New chain-id

Description

We ditch Kurtosis chain-id for a new one

Motivation and Context

We need a unique chain-id, and this one is about the speed of light ;)

How Has This Been Tested?

canary2 machine

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Style (style only changes)
• Refactor (code that does not add new functionality nor fixes a bug)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I added deployment script (Makefile, docker file etc.)
• I have updated the documentation accordingly - Docusaurus.
• I have added tests to cover my changes.
• All new and existing tests passed.

[evchip]

everyone needs to update the chain ID in their wallet based on this change right? @w-woloszyn

[w-woloszyn]

everyone needs to update the chain ID in their wallet based on this change right? @w-woloszyn

yes, though metamask will suggest the new one by fetching it from rpc

[evchip]

everyone needs to update the chain ID in their wallet based on this change right? @w-woloszyn

yes, though metamask will suggest the new one by fetching it from rpc

Even if the user has already created a network with the old chain ID but the same RPC URL?

[kss-t1]

everyone needs to update the chain ID in their wallet based on this change right? @w-woloszyn

yes, though metamask will suggest the new one by fetching it from rpc

Even if the user has already created a network with the old chain ID but the same RPC URL?

I think we should change Chain ID even if that would require users to remove t1 network and recreate it in Metamask.

[evchip]

everyone needs to update the chain ID in their wallet based on this change right? @w-woloszyn

yes, though metamask will suggest the new one by fetching it from rpc

Even if the user has already created a network with the old chain ID but the same RPC URL?

I think we should change Chain ID even if that would require users to remove t1 network and recreate it in Metamask.

Agreed, but it's worth flagging 🇵🇱

[evchip]

We need to update T1_DEVNET_CHAIN_ID in T1Constants.sol

[evchip]

thanks! please communicate when the canary env will use this chain ID, as we will need to update it on the front end