Bitcoin Forum
June 22, 2024, 04:26:53 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Bitcoin / Bitcoin Technical Support / Re: Transaction stuck for 3 days, can't accelerate with viabtc on: December 09, 2017, 08:01:21 PM
Great job!

Thank you
2  Bitcoin / Bitcoin Technical Support / Transaction stuck for 3 days, can't accelerate with viabtc on: December 09, 2017, 06:44:46 PM

Hi guys,

I'm waiting for 3 days for this  transaction. At the time I made this , fee was recommended for 60 minutes. But then cаme the overload of the network.

https://blockchain.info/tx/fd34d004961d840b5b7572081e4d1ce3349fd29225393e28d48d7b5ff3f1e50e

Tried to accelerate with confirmtx and antpool , but still no result.

I have no luck with VIABTC accelerator. Every time(tried more then 10 times for 2 days) I get  "Submissions are beyond limit. Please try later". No matter how I try(round hour ..etc).


Thanks,
3  Bitcoin / Bitcoin Technical Support / Re: Bitcoin ABC stuck at block 478558 and not syncing on: November 21, 2017, 05:59:17 PM



I was unable to read the forum these days.

I found meanwhile that re-downloading whole blockchain from the beginning(2009) fixed the issue. I started bitcoin-ABC-qt to point empty directory and then replaced newly created wallet.dat with the existing one.
Then restarted the bitcoin-qt and waited all to finish. I have good Internet speed , and the time was comparable to reindex existing files  ~ 6 hours for both.

Finally I was able to withdraw the amount. You don't need to import keys if you use Bitcoin core based wallet , just copy wallet.dat file

Same was with the bitcoin gold. (just download appropriate wallet)

Thanks all for the comments.
4  Bitcoin / Bitcoin Technical Support / Bitcoin ABC stuck at block 478558 and not syncing on: November 18, 2017, 12:16:18 PM
Hi guys,

I started BitcoinABC wallet pointing my old bitcoin core wallet, and after reindex program stuck at block  478558 and not syncing any more.
I see the amount before the fork  , but cant sync any further. My Bitcoin core wallet was up to date ( before I started the bitcoinabc). So this contains blocks that will be not acceptable for bitcoin cash I think.


Details :
Client vertion : v0.16.1.0-19b2c4a
Number of connections : 8
Current number of blocks : 478558
Last block time: Tue Aug 1 16:16:14 2017

On the connected peers I see that they have block : 504710

Maybe the next block which is not accepted from the bitcoin cash is the problem

Tried to invalidate next block : 478559:

invalidateblock 00000000000000000019f112ec0a9982926f1258cdcc558dd7c3b7e5dc7fa148

Command pass OK , but didn't helped.

Any idea what to do?


Thanks,

5  Bitcoin / Bitcoin Technical Support / Re: Two problems with transaction on: November 16, 2017, 05:28:59 PM


Thank you all for comments.

It was good to know what Danny said:

"Your new wallet was probably not online at the time that your old wallet transmitted the transaction, therefore your new wallet will probably not see the transaction until it is confirmed."

"A receiving wallet will not display a transaction until it has heard about it from a peer."

I didn't  know about this. Hope that other people will not have headaches with this.



6  Bitcoin / Bitcoin Technical Support / Re: Two problems with transaction on: November 16, 2017, 05:13:15 PM
@user234

If you are not in a hurry, then you can just wait, and leave your old wallet running.  With such a low fee, it is very difficult to predict how long it will take for the transaction to confirm. You might get lucky and your transaction could be confirmed in the very next block a few minutes from now, or you could get very unlucky and it could take many weeks or months.

If you become impatient, you will have a couple of options:
  • Replace the transaction with a higher fee transaction.
  • Create a CPFP transaction to incentivize miners to confirm the transaction sooner.
  • use a transaction acceleration service with a mining pool to increase the likelihood that the transaction will be confirmed in the next block solved by that mining pool.

Also, if you want the unconfirmed transaction to show up in your receiving wallet, you can broadcast the raw transaction from there.  You would need to acquire the raw transaction (this can be accomplished with getrawtransaction in the "Console" (found in the "Debug Window" under the "Help" menu option) of the sending wallet.  Then in the "Console" of the receiving wallet you would use the sendrawtransaction command.



In fact, you were absolutely right

Just received transaction on my new wallet.( currently with 2 confirmations - but I'm able to see now )So everything OK, now  Smiley

My old wallet was opened as you advised me.

Very accurate and professional opinion.

Thank you Danny!



7  Bitcoin / Bitcoin Technical Support / Re: Two problems with transaction on: November 16, 2017, 02:40:28 PM
From what I understand the new wallet is Bitcoin Core. Is it synced? Because if it's synced I think that it should show the transaction even with 0 confirmations.
Normally is not necessary for the old wallet to stay open.

You should give us the transaction id (tx id) to see more about it - basically at such small fee you should try/ask to accelerate it else the chance it won't go through is quite big - but first make sure that the recipient is indeed an address in your new wallet.


Yes the new wallet is synced ( Bitcoin Core 0.15.1)
I copied the recipient address from new wallet from File–> Receiving addresses. There was only one address. I've send the transaction to this address that i copied from new wallet.
Let's double check the address again, before try to ask to accelerate. Where you recommend?

If there is a problem , with the recipient address (new wallet) is it a better idea to try to get back this transaction to original wallet while still unconfirmed?
8  Bitcoin / Bitcoin Technical Support / Re: Two problems with transaction on: November 16, 2017, 02:08:50 PM
The transaction fee on your transaction is quite low.

As such, it will probably take a very long time for it to confirm.

Your new wallet was probably not online at the time that your old wallet transmitted the transaction, therefore your new wallet will probably not see the transaction until it is confirmed.

Your transaction fee is low enough that many nodes and miners may choose to drop the unconfirmed transaction from their memory pools in a few days.  If you leave your old wallet running (or you start it back up every few days) then it will re-broadcast the transaction to remind the network about it.



Thanks for your answer Danny!


Yes, you are correct,  my new wallet was not online at the time that I made transaction from old wallet. I hope that you are right , and there is not a problem with the new wallet.
But whats in the case if this transaction is confirmed after long time , but I still can't see in the new wallet?

Is there a way to check that the new wallet working properly? There are no error messages and I'm currently connected with 8 peers. Any way to force  the new one to see the unconfirmed transaction,
or the only option in my case is to leave the old wallet running and wait?





9  Bitcoin / Bitcoin Technical Support / Two problems with transaction on: November 16, 2017, 11:05:13 AM
Hi there,

I'm new and sorry if this was discussed before.

I tried to move btc to my new wallet from an old one. ( I own both of them, using Bitcoin Core 0.15.1)

Almost 24 hours after I sent the transaction, the "transactions" tab on the new wallet is still empty. Seems to be new wallet has no information about this transaction.
Balance(available, pending and total) on the new wallet is also empty. From the old wallet I see the transaction to the new address.
Both wallets are synced up to date.

 I know that there will be a some time until confirmed , but is it normal not to see the transaction in the transactions tab and the pending balance (currently empty)on the new wallet, while still waiting to be confirmed. This is my main concern now. I suppose  the "pending balance" should be seen even if they are not yet confirmed?

If this is OK  then the problem is probably small transactions fee.

From the old wallet I see the transaction as unconfirmed.
"Status: 0/unconfirmed, in memory pool"
Also size is 2701 bytes which is huge.

The transaction is still unconfirmed ( checked also on blockchain.info )

Bitcoin Client Software and Version Number: Bitcoin Core 0.15.1

Transaction ID : e
Size :  2701
Weight    10804
Fees    0.0005416 BTC
Fee per byte    20.052 sat/B
Fee per weight unit    5.013 sat/WU

Does it make sense to wait or to do any steps from my side?
What will you advise me to do?


Any help would be greatly appreciated
Thank you very much,
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!