Holger Drewes

> are you expecting breaking changes on the trie library interface? I‘m using it quite a bit, also internal structures and it‘d be quite bad if it was broken. Can...

This should not be a dedicated package on its own (or has there been any discussion on this that I missed? Otherwise I am not seeing a reason for this?)....

> @holgerd77 > > I could pivot from the `evm-vm-tests` #2341 and broaden to a general `shared-test` package if you'd like. See my comment on #2341, once we have the...

Oh, we have never tried to get the devp2p library working with Polygon. That's definitely an interesting experiment and we can keep this issue open and see over time if...

Ah, one thing as some starting point though, just occurred to me: the setting of a custom network with these predefined `CustomChain` enum values is just a very much stripped...

> Hi @holgerd77, turns out the problem was I was passing port as string whereas it should be int, I fixed it now its able to connect to bootnodes. I'm...

@buchan123 I've generalized the title of your issue a bit, I hope that's ok, then we can keep this a bit as a general Polygon support analysis issue.

I would have some tendency to close if such a small issue is not taken within close to a year's time. Or do we want to keep? Would this addition...

Ok, then I would say: issue (still) open for a casual side grasp. 🙂 😆 At least one test case would be nice/good as well.

Also pasting here for reference, start command is (as posted by Jochem in the chat): ```shell go run ./hive.go --client ethereumjs --sim ethereum/engine --sim.limit "engine-withdrawals/Withdrawals Fork on Block 1" ```