Igor Artamonov
Igor Artamonov
If that's the case, it's a bug. I didn't do extensive testing with fallback, but even without it the Dshackle shouldn't use a SYNCING node. I'll take a look
Not sure. I found a similar issue with `eth_call` when it refers a specific height but routed to an upstream that didn't catch it yet. Fixed in [90c39768913c] But I'm...
Oh, I see. That's interesting, didn't see this EIP, thank you. I'll do some debugging and hope to fix it asap
Hi Chase! Thank you, working on it right now, I can reproduce it and going to fix, and make a release (in in a couple of days at max).
@MysticRyuujin please try version 0.9.2
yeah, I actually fixed the issue with block height/hash in eth_call, and it was the main cause of that issue. I made an integration test with exactly your code, and...
what if you try without blockHash, or with referencing it just by height?
ok, thank you. that's different from what I get with my test env, but I'll try to reproduce. will keep you posted
@MysticRyuujin i'm still trying to reproduce and now i'm thinking that it's something else causing the error. Is it possible that all of the upstreams are syncing, or something like...
@MysticRyuujin can you try with v0.9.3?