support Geth chainspec format

[kristofgazso]

Describe the solution you'd like Nethermind currently uses the Parity chainspec format while virtually all other clients use the Geth chainspec format. It would be great for composability if Nethermind also supported the Geth chainspec format

[kamilchodola]

Do we still want to do that? Any pros of doing than rather than quicker integration into some Geth-based chains? @MarekM25 @LukaszRozmej - imo not worth spending time but up to you.

[LukaszRozmej]

No idea I think @smartprogrammer93 was looking into it (or someone else)

[smartprogrammer93]

Not me, i remeber @flcl42 mentioned this

[flcl42]

I like the current spec for ability to set exactly eips you need. There is also a script to map it into geth format. We need to look for users for such low priority issues - make a permanent poll in discord or so. And close em after a year of no demand

[kamilchodola]

I mean these days we have scripts as mentioned to convert easily.

I even converted Geth to Neth and other way around with GPT in a matter of minutes so I don't think we need to invest tons of time to support Geth styled chainspec which is quite low level change imo.

I'd recommend closing the issue for now and in case we will receive a huge demand for that - reopen.

[stdevMac]

Closing in post of the previouos comment.

[LukaszRozmej]

I think we are consider supporting it directly so I will re-open for now.

[kristofgazso]

Woah I remember opening this issue so many years ago, good times 🫡

[kamilchodola]

This NEEDS to be done. Nothing optional here, we already agreed on unifying the format or creating a new one for all clients.

[smartprogrammer93]

Let's not do anything blindly for now. We will do it. But clients need to agree on the spec.