From 96a0976af3bf04f8059e3a93db8bdf884b0624c9 Mon Sep 17 00:00:00 2001 From: ligi Date: Wed, 25 Jan 2023 17:00:47 +0100 Subject: [PATCH] Improve collision management (#2181) --- README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4b3681dc..445f82ea 100644 --- a/README.md +++ b/README.md @@ -87,8 +87,11 @@ There are also aggregated json files with all chains automatically assembled: ## Collision management - If different chains have the same chainID we list the one with the oldest genesis. - + We cannot allow more than one chain with the same chainID - this would open the door to replay attacks. + The first pull request gets the chainID assigned. When creating a chain we can expect that you read EIP155 which states this repo. + All pull request trying to replace a chainID because they think their chain is better than the other will be closed. + The only way to get a chain reassigned is when the old chain gets deprecated. This can e.g. be used for testnets that are short lived. But then you will get the redFlag "reusedChaiID" that should be displayed in clients to warn them about the dangers here. + ## Usages ### Wallets * [WallETH](https://walleth.org)