Igor Artamonov
Igor Artamonov
that should work. You try https://api.gastracker.io/web3
As you have the private key, then you already have access to the wallet. Just use it
Hm, from your first message I understood it as you've used ETH address instead of ETC address. If that's the problem, you can get your ETH from that address. But...
Yes, same. It's Private Key for Ethereum address in general, it works for both ETH and ETC chains
Exactly same. Just two different chains of same Ethereum. Even had same block history, till Jul 20th, 2016
Did you try to specify it as `basic-auth` option? https://github.com/emeraldpay/dshackle/blob/master/docs/reference-configuration.adoc#ethereum-connection-options PS I guess it's possible to extract from the URL as well, but at this time I could suggest to...
Does it respond to any other requests? Like proxy endpoint, if it's enabled, or the health checks?
Do you have any errors in the logs? Or anything else that may suggest the source of the problem?
You can run it with debug logging by setting env `DSHACKLE_LOG_LEVEL=DEBUG` but I don't think it could help with this particular problem. Because errors are printed to console by default....
Oh, that's very unexpected. Do you have any numbers/stats/etc to find out how many outdated bitcoin nodes are here? To figure out if that makes sense to fix or better...