-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
return of "Deposit failed: Invalid JSON RPC response:" #17
Comments
This lack of care for such a crucial tool makes me sad. I trusted Kraken
but I won’t be putting more genesis Ether into the exchange.
Richard
Sent via Superhuman <https://sprh.mn/?vip=i@rb.cm>
…On Thu, Jun 01, 2017 at 12:09 PM, ***@***.***>wrote:
I see that there have been previous issues with this Kraken deposit error.
Appears issue was fixed but seems to have reemerged recently, please
evaluate
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#17>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAavkFaMcXbMi7tTzZ4-7JFvqfO1WbWyks5r_o3pgaJpZM4NsxKB>
.
|
I am having this issue too. Could you please look into it. |
This is a total joke :( No faith in Kraken any more.RichardSent via SuperhumanOn Mon, Jun 19, 2017 at 11:39 PM, exslammer<notifications@github.com>wrote:I am having this issue too. Could you please look into it.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.
|
Ric, what exchange are you going to try next? |
5 more. Will report back on the one I dislike the least.
…On Jun 20, 2017, 13:56 +0100, exslammer ***@***.***>, wrote:
Ric, what exchange are you going to try next?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I see that there have been previous issues with this Kraken deposit error. Appears issue was fixed but seems to have reemerged recently, please evaluate
The text was updated successfully, but these errors were encountered: