mirror of
https://github.com/Instadapp/chains.git
synced 2024-07-29 22:37:19 +00:00
Improve collision management (#2181)
This commit is contained in:
parent
5064e29da3
commit
96a0976af3
|
@ -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)
|
||||
|
|
Loading…
Reference in New Issue
Block a user