You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Those two lines are important: Line 274 in BlockchainBridge.cs Line 283 in BlockchainBridge.cs
In Nethermind, the implementation uses timestamp + slotTime. However, as far as I know, in Geth, the logic instead uses timestamp + 1. I believe timestamp + slotTime is better for block estimation.
Sina from the Geth team mentioned there is a known issue with the timestamp in eth_simulate calls, and I suspect this difference in timestamp logic could very likely be the root cause.
So:
Discuss this issue with the Geth team to reach a consensus on the ETH R&D Discord.
Fix the Hive tests for eth_simulate to resolve the errors.
Ideally, define this in the spec and adjust implementation Geth <> Nethermind
The text was updated successfully, but these errors were encountered:
Those two lines are important:
Line 274 in BlockchainBridge.cs
Line 283 in BlockchainBridge.cs
In Nethermind, the implementation uses timestamp + slotTime. However, as far as I know, in Geth, the logic instead uses timestamp + 1. I believe timestamp + slotTime is better for block estimation.
Sina from the Geth team mentioned there is a known issue with the timestamp in eth_simulate calls, and I suspect this difference in timestamp logic could very likely be the root cause.
So:
The text was updated successfully, but these errors were encountered: