Igor Artamonov
Igor Artamonov
Oh, that's a silly bug. Fixed now with https://artifacts.emerald.cash/builds/dshackle/2021-12-24/20211225-0710-f2b471c/dshackle-0.12.0-SNAPSHOT.zip
That one is more tricky, needs some design changes. Will take a bit more time. Thank you for reporting it
So, the issue is that Dshackle doesn't currently provide `eth_getLogs` method, but before the recent changes it didn't return error on that method. So I think that was actual reason...
It seems that the upstream is not working and returning `Oops...nothing here!` as a response to any request
I'm not familiar with the Bucket4j but I guess it could work. Dshackle already has a support of Redis for caching, so using Redis should align well with the current...
Thank you! It seems that I need to check why it stuck. This time I'm not ready for setting up another node, so I'm going to try with their public...
Ok, so the Fantom doesn't have conception of "Block Difficulty" which Dshackle uses to determine forks/consensus splits. As a result Dshackle cannot figure out if a new block is a...
Initially it was 11. I don't remember exactly, but there was a reason to upgrade to 13. At this point it makes more sense to upgrade to 17 LTS, but...
In general, it happens when Dshackle received a response from an upstream, but a client connected to Dshackle already disconnected. But it also happens in other situations when a response...
It's not possible now, but could be implemented