Metamask warning when adding Wethio network details

[wethioproject]

Metamask warning when adding Wethio network details

[fbaud]

@wethioproject You did not contact us and we are still using this chain.

We pushed the chain id 78 almost 3 years ago. Either you should have checked chain ids before starting your own chain and you must accept that coming late means taking a free chain id. Or you must accept not being accepted by Metamask (which endorsed the forward looking intent of this repo).

@ligi Thx for the ccing

[ligi]

their RPC seems to be active and still produces blocks: https://ethnode.primusmoney.com/mainnet

this is our collision policy: https://github.com/ethereum-lists/chains?tab=readme-ov-file#collision-management

[wethioproject]

Hello Thanks for the update I don’t think their project I still active , we have a big community and the message in metamask affect our reputation we should have a solution for the issue. Best Le lun. 26 fév. 2024 à 14:20, ligi ***@***.***> a écrit :

…

their RPC seems to be active and still produces blocks: https://ethnode.primusmoney.com/mainnet this is our collision policy: https://github.com/ethereum-lists/chains?tab=readme-ov-file#collision-management — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6PMJ4RKSQSCPSNL7H3YVSDYRAVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGEZDSNRWHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ligi]

the RPC is still producing blocks - ask them to stop it or mark their chain deprecated - then you can add yours - currently this is not possible with their chain being active.

[ligi]

you should have red: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-155.md and added your chain here earlier.

[wethioproject]

We contact the project team , but there is no answer from their side Le lun. 26 fév. 2024 à 14:25, ligi ***@***.***> a écrit :

…

you should have red: https://github.com/ethereum/EIPs/blob/master/EIPS/eip-155.md and added your chain here earlier. — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6PZTY6OHLWDNZKAIYTYVSEL7AVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGE2DAMJRGU> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[ligi]

ccing @fbaud who added the chain here: #187

[ligi]

@fbaud thanks for chiming in

[wethioproject]

Hello @fbaud <https://github.com/fbaud>, thanks for your message, we sent you an email on ***@***.***, you can check your spam, and for our chain it s already started from Juin 2020, it means oldest than your chain, we did never have this problem on metamask. @ligi <https://github.com/ligi> so actually what is the solution for this problem, as we have already big community behind the project and we can not accept having such message. Thanks Le lun. 26 févr. 2024 à 16:14, ligi ***@***.***> a écrit :

…

@fbaud <https://github.com/fbaud> thanks for chiming in — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6KMXZHSUV2G5LFYO53YVSRDRAVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRUGM4DCMBTGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ligi]

The only 2 solutions I see are:

• you change your chainId
• you get the other project to give up their chainid

[wethioproject]

We can not change the chain id as our project running since 2020 and we have more than 30k users using our rpc Le mar. 27 fév. 2024 à 09:05, ligi ***@***.***> a écrit :

…

The only 2 solutions I see are: - you change your chainId - you get the other project to give up their chainid — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6JIY7ADNYWBZCYNCWLYVWHUNAVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRVHE4DOOBTHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ligi]

You should have registered the chainId then. Nothing I can do here other than the options I outlined.

[wethioproject]

Our blockchain is older than their blockchain , so minimum you have to change the error message in metamask, or manage the collision with another way , our project started in 2020, you should check community for every project and impact of project in crypto industry to give chain id priority Le mar. 27 fév. 2024 à 09:16, ligi ***@***.***> a écrit :

…

You should have registered the chainId then. Nothing I can do here other than the options I outlined. — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6K67O2DAKUIKHWBGH3YVWI4HAVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWGAYDIMBWGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ligi]

You did not read the documentation (EIP155) and did not register your chainId. So the fault is on your side. We will not run a popularity contest. Our collision policy is clear: the first one registering a chainId gets the chainId.

[wethioproject]

@fbaud <https://github.com/fbaud> you still using your solution? Best Regards, Le mar. 27 févr. 2024 à 09:54, ligi ***@***.***> a écrit :

…

You did not read the documentation (EIP155) and did not register your chainId. So the fault is on your side. We will not run a popularity contest. Our collision policy is clear: the first one registering a chainId gets the chainId. — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6IFIQF7UNKWES7S2XLYVWNK5AVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWGA3DKNBUG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[fbaud]

@wethioproject see my previous response, we are still using this chain and have several workflows relying on it. We do use Metamask in some of them.

[wethioproject]

@fbaud <https://github.com/fbaud> please check your email i v sent you an email on ***@***.*** Le mar. 27 févr. 2024 à 10:55, Frederic Baud ***@***.***> a écrit :

…

@wethioproject <https://github.com/wethioproject> see my previous response, we are still using this chain and have several workflows relying on it. We do use Metamask in some of them. — Reply to this email directly, view it on GitHub <#4423 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALHLZ6N4DOXYZOVD4IFOME3YVWUQTAVCNFSM6AAAAABD2FSCB2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRWGE3TQNZQGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[wethioproject]

@ligi, when we started working on our blockchain in 2020 we checked for other chains with chainId 78 and did not find any. If Primus Money was listed here at that time, then it would have been our fault for using the chain id 78.
But Primus money added their network info here in March 2021. So our fault is only that we did not add our chain info here earlier than Primus Money.
Please check if you can provide any help regarding collisions, or atleast the Metamask team should help us on this issue.