Bitcoin Forum
December 12, 2017, 04:48:41 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: double spend no longer possible?  (Read 307 times)
seran
Newbie
*
Offline Offline

Activity: 13


View Profile
May 29, 2017, 08:18:13 AM
 #1

I have a stuck transaction, which I would like to replace by a new transaction with a higher fee and a different output (because I paid by credit card in the meantime). I followed this tutorial:

https://steemit.com/bitcoin/@profitgenerator/tutorial-how-to-fix-unconfirmed-transactions

Everything worked fine, until I tried to broadcast the new transaction from the fresh wallet. Then I got the following error:

error: The transaction was rejected by networkrules. (258:txn-mempool-conflict)

and a cryptic error code.

Is double spending no longer possible, or did I do smth wrong? Any help is appreciated!

Regards,
seran
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
ranochigo
Legendary
*
Offline Offline

Activity: 1288


View Profile WWW
May 29, 2017, 10:17:02 AM
 #2

I have a stuck transaction, which I would like to replace by a new transaction with a higher fee and a different output (because I paid by credit card in the meantime). I followed this tutorial:

https://steemit.com/bitcoin/@profitgenerator/tutorial-how-to-fix-unconfirmed-transactions

Everything worked fine, until I tried to broadcast the new transaction from the fresh wallet. Then I got the following error:

error: The transaction was rejected by networkrules. (258:txn-mempool-conflict)

and a cryptic error code.

Is double spending no longer possible, or did I do smth wrong? Any help is appreciated!

Regards,
seran
Double spending has never been possible. It is also not possible for you to replace a transaction that spends the same output as another transaction in the mempool, unless specifically indicated in the first transaction.

Current nodes do not allow replacebyfee unless it has optin enabled in the transaction that is going to be replaced. If not, you will have to wait till the transaction gets dropped (ie. Not being able to search for that transaction on blockexplorers) before you can broadcast it. It can take several days if no one rebroadcasts that transaction.














 

 

█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
BitBlender 

 













 















 












 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
Abdussamad
Legendary
*
Offline Offline

Activity: 1582



View Profile WWW
May 29, 2017, 11:31:17 AM
 #3

Here is something you can do: https://bitcointalk.org/index.php?topic=1916963.msg19015496#msg19015496

seran
Newbie
*
Offline Offline

Activity: 13


View Profile
May 29, 2017, 11:47:06 AM
 #4

Current nodes do not allow replacebyfee unless it has optin enabled in the transaction that is going to be replaced. If not, you will have to wait till the transaction gets dropped (ie. Not being able to search for that transaction on blockexplorers) before you can broadcast it. It can take several days if no one rebroadcasts that transaction.

The thing is, I'm waiting for weeks now for the tx to be dropped. It just isn't. I have the feeling that the mempools keep the unconfirmed tx, to keep the fees high. Since the more tx are in the mempool, the higher fees you've got to pay to be confirmed. The whole bitcoin blockchain is messed up in my opinion Sad
nimbus22
Newbie
*
Offline Offline

Activity: 4


View Profile
May 29, 2017, 02:14:10 PM
 #5

I have the exact same problem.  It gets dropped and then it gets rebroadcast somewhere in the network.  It's been stuck for over two weeks now.

I think at some point I will try to double spend like you did.  When it says "create new wallet", is that the same instance of electrum on the same computer?
Abdussamad
Legendary
*
Offline Offline

Activity: 1582



View Profile WWW
May 29, 2017, 02:27:28 PM
 #6

i have posted the solution to your problems above in post number 3 but you guys ignore it. stuck transactions are responsible for 9/10 of the posts on this forum in the last few months. if you just follow the guide we have created for you you'd be fine.

ranochigo
Legendary
*
Offline Offline

Activity: 1288


View Profile WWW
May 29, 2017, 02:28:06 PM
 #7

Current nodes do not allow replacebyfee unless it has optin enabled in the transaction that is going to be replaced. If not, you will have to wait till the transaction gets dropped (ie. Not being able to search for that transaction on blockexplorers) before you can broadcast it. It can take several days if no one rebroadcasts that transaction.

The thing is, I'm waiting for weeks now for the tx to be dropped. It just isn't. I have the feeling that the mempools keep the unconfirmed tx, to keep the fees high. Since the more tx are in the mempool, the higher fees you've got to pay to be confirmed. The whole bitcoin blockchain is messed up in my opinion Sad
Not really. The mempool isn't managed by a single entity. Every node and miner has the rights to include or exclude any transaction in their mempool. The number of transaction will not affect the fees but rather, the fees paid in the transactions will do. In most cases, node's mempool will take your transactions out after 3 days or so since it takes up precious resources.

The rebroadcast can be done by anyone really. It is possible that the person you are sending the payment to is rebroadcasting it continually.

Anyways, if you really prefer not to wait forever, use Abdussamad's guide. CPFP can work well although it will take significantly more fees but it will get the job done.














 

 

█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
BitBlender 

 













 















 












 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
█ 
nimbus22
Newbie
*
Offline Offline

Activity: 4


View Profile
May 29, 2017, 02:54:22 PM
 #8

i have posted the solution to your problems above in post number 3 but you guys ignore it. stuck transactions are responsible for 9/10 of the posts on this forum in the last few months. if you just follow the guide we have created for you you'd be fine.


I did read this.  I would say this is a pretty good solution in most cases.  However this doesn't help if want to void the original transaction.
Abdussamad
Legendary
*
Offline Offline

Activity: 1582



View Profile WWW
May 29, 2017, 03:00:38 PM
 #9

i have posted the solution to your problems above in post number 3 but you guys ignore it. stuck transactions are responsible for 9/10 of the posts on this forum in the last few months. if you just follow the guide we have created for you you'd be fine.


I did read this.  I would say this is a pretty good solution in most cases.  However this doesn't help if want to void the original transaction.

Bitcoin transactions are irreversible so relying on some mythical ability to void transactions is the wrong approach. My suggestion do a CPFP and get the original transaction confirmed. Then ask for a refund from whoever you sent the money to.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!