sambacha commented on issue #51: URL: https://github.com/apache/incubator-tuweni/issues/51#issuecomment-636392706
Parity and Geth clients have different acceptable genesis files, Parity: https://github.com/5chdn/crossclient-chainspec/blob/master/parity.json Geth: https://github.com/5chdn/crossclient-chainspec/blob/master/geth.json yes, the spec. isn't even agreed to as a standard in ethereum foundation, which `chain_id` and `network_id` having different meanings, but let's just ignore that for this argument. I think a good place to start would be with something like this: https://github.com/ethereum-lists/chains where a network's metadata is at least indexed and agreed upon. Defining those terms first then worrying about specific parts such as `alloc` for example would be easier, as the amount of configuration is rather large when you start getting into IBFT2, etc. Another good reference point would be the Parity config generator: https://paritytech.github.io/parity-config-generator/#config=e30= ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
