Bitcoin Forum
November 09, 2024, 04:07:52 AM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Wallet to GDAX transaction did not execute - should I try again ?  (Read 147 times)
MCLXS411 (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
December 17, 2017, 01:24:03 PM
 #1

Yesterday I tried to send some BTC to GDAX from my wallet.
At first it seemed fine, my balance was reduced and I waited and waited.
Than after a while my balance was restored and it seemed like nothing ever happened.

What can be causing this ?

P.S.

I use Jaxx wallet.
btcton
Legendary
*
Offline Offline

Activity: 1302
Merit: 1007


View Profile
December 17, 2017, 01:59:39 PM
 #2

Yesterday I tried to send some BTC to GDAX from my wallet.
At first it seemed fine, my balance was reduced and I waited and waited.
Than after a while my balance was restored and it seemed like nothing ever happened.

What can be causing this ?

P.S.

I use Jaxx wallet.

It was most likely caused by too low of a fee that made the transaction not get confirmed on the network. If the fee was low enough, the behavior of your transaction fits that of a transaction with a fee so low that it got dropped within the day from your own mempool. I am not familiar with how Jaxx manages transactions, as I have never used it myself, but it might not have been able to calculate the fee automatically. Do you have the transaction hash? This would be a sure way to confirm these suspicions. If you look up your transaction on block explorers such as Blockchain.info and do not get a result, the only possibilities are that it got dropped as I mentioned before or that for some reason the transaction was never broadcast in the first place.

If my suggestion is correct, then yes, feel free to try again with a higher fee and it should succeed next time.

The signature campaign posters adding useless redundant fluff to their posts to reach their minimum word count are lowering my IQ.
MCLXS411 (OP)
Newbie
*
Offline Offline

Activity: 19
Merit: 0


View Profile
December 17, 2017, 03:09:46 PM
 #3

No, I don't have the transaction hash.
btcton
Legendary
*
Offline Offline

Activity: 1302
Merit: 1007


View Profile
December 17, 2017, 10:35:40 PM
 #4

No, I don't have the transaction hash.

Well, my original suggestion still stands. If this ever happens to you again, make sure to have written down the transaction ID so that we can have a closer look at what is happening. Part of me is starting to think that something must have happened client-side if you do not even have a transaction hash, but it is still possible that it was still completely ignored by the network because of the fee. Did you put in the fee manually or did your wallet do that for you? I can't think of any other possibility, really.

The signature campaign posters adding useless redundant fluff to their posts to reach their minimum word count are lowering my IQ.
bob123
Legendary
*
Offline Offline

Activity: 1624
Merit: 2481



View Profile WWW
December 19, 2017, 08:22:10 AM
 #5

I use Jaxx wallet.

This might also be the issue. A lot of user are complaining about jaxx recently.
Most of them seem to be unable to send any funds (mostly connection issues).
This could be your problem too, it would explain why your balance got deducted first (jaxx trying to send funds) and
afterwards it appeared again (jaxx failed to connect to push tx(?)).

You can try to send your funds again (but make sure to include a high enough fee: https://bitcoinfees.earn.com/).
If you furthermore won't be able to send anything out from jaxx you can [1] export your private keys and [2] import them into another wallet (e.g. electrum).

[1] https://decentral.zendesk.com/hc/en-us/articles/218375657-How-can-I-view-my-private-keys-
[2] http://docs.electrum.org/en/latest/faq.html#can-i-import-private-keys-from-other-bitcoin-clients

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!