Mario Vega

I can help with translation to Spanish.

Hello, I am hitting this issue while preparing the prysm's [hive](https://github.com/ethereum/hive) client image. Is there a known cause for this or an ETA ? Many thanks.

> @marioevz this is not actively being worked on. What is required for Prysm's hive client image? All clients on hive need to run a configuration shell script before actually...

Hi @Giulio2002, this proposed change fixes the test where we were getting the `already known` for the transaction that was unwound back into the txPool. Let me know if this...

Thanks for the insight @fjl, yes I think this is exactly what's needed for the implementation of the test case. I would like to give it a go to implement...

Hi @zilm13, thanks for the changes, let me clarify: - Yes, if both EL clients have each a different block with the same difficulty, neither of the two will re-org...

From that fragment I understand that the `fcU` should only be sent when the validator is proposing the transition block, but I understand that it is not directly prohibited in...

I'm almost done with the changes, but the verification approach is giving me some trouble. The test now returns `SYNCING` to every `newPayload`/`forkchoiceUpdated` until after we start getting `execution_optimistic==true` blocks...

Branch https://github.com/marioevz/hive/tree/fix-opt-sync-test has this test updated now: ``` hive --client go-ethereum,lighthouse-bn,lighthouse-vc --sim eth2/engine --sim.limit "/syncing-with-chain-having-invalid-transition-block" ```

Teku seems to now be passing the test (yay! :partying_face:), this behavior is only seen in Lighthouse, so I am now more inclined to think this is a client specific...