[FR]: Manual Network Config Input

[daGscheid]

Describe your idea

Because the Ethereum architecture is one of the most solid PoS blockchain architecture out there a lot of networks simply use their clients as a basis for their own networks.

To better capture this I suggest to integrate a more generic manual network input feature, that enables the user to use all of the Stereum supported clients on any network, they wish for and know the parameters of.

A more generic UI, should be coupled with this to support this feature.

• [ ] Discuss
• [ ] Design
• [ ] Build

Name / Network ID Input

Considered Alternatives?

Alternative is to integrate a giant list of supported networks. I don't know if this is really what we would like to do. Though the chain ID could be fun to use to automate this.

Additional Context

No response

Acknowledgment

• [X] I looked through the feature requests/enhancements planned for this project before submitting a new idea

[daGscheid]

https://consensys.io/blog/hyperledger-besu-how-to-create-an-ethereum-genesis-file

{

  "config": {

    "chainId": 2018,

    "muirglacierblock": 0,

    "ibft2": {

      "blockperiodseconds": 2,

      "epochlength": 30000,

      "requesttimeoutseconds": 4

    }

  },

  "nonce": "0x0",

  "timestamp": "0x58ee40ba",

  "extraData": "0xf83ea00000000000000000000000000000000000000000000000000000000000000000d5949811ebc35d7b06b3fa8dc5809a1f9c52751e1deb808400000000c0",

  "gasLimit": "0x1fffffffffffff",

  "difficulty": "0x1",

  "mixHash": "0x63746963616c2062797a616e74696e65206661756c7420746f6c6572616e6365",

  "coinbase": "0x0000000000000000000000000000000000000000",

  "alloc": {

    "9811ebc35d7b06b3fa8dc5809a1f9c52751e1deb": {

      "balance": "0xad78ebc5ac6200000"

    }

  }

}