<blockquote>
  <p>Is there an easy to understand step by step guide</p>
</blockquote>

<p>No. There is no <strong>easy to understand</strong> guide if you do not understand the underlying  processes.</p>

<blockquote>
  <p>I can execute to create a double spend and get the unconfirmed
  transaction reversed back into the original wallet</p>
</blockquote>

<p>The transactions can not be "reversed back" and are not going "to/from the wallet".</p>

<blockquote>
  <p>so I can resend it with a higher fee and get it delivered?</p>
</blockquote>

<p>The doublespending transaction is the transaction which uses the same input set, but has another outputs/fees. You do not need to do two steps (a) reverse original transaction (b) send another transaction with higher fees, because this is one step.</p>

<p>As far as I know, some wallets contain Replace-By-Fee features, but I use my own program. It is not "easy-to-understand", but it works</p>

CC BY-SA 3.0
2017-10-27T05:09:03.150Z
2017-10-27T05:09:03.150Z
amaclin
<p>No, but if your concern only is to make the transaction to go through you can google for transaction priority services.</p>

<p>several miners offer services to pay extra fees to expediate transactions that would otherwise be stuck with too low fee.</p>

CC BY-SA 3.0
2017-10-27T07:37:40.757Z
2017-10-27T07:37:40.757Z
Jonathan Silverblood
<p>you can not reverse sent transaction. It is in mem pool and waiting to be picked up.
you can send double spend transaction with higher fee to another nodes, if your first transaction is not picked by miners yet there is very very low chance your new transaction will be processed first as miners might pick with high fee.</p>

<p>Eventually only one tx will be processed.</p>

CC BY-SA 4.0
2018-09-25T14:18:43.287Z
2018-09-25T14:18:43.287Z
VJV
<p>No. That type of double-spend will produce a conflict and will get your node DoS banned assuming that you've already broadcasted an earlier transaction that spent the UTXOs. </p>

<p>Unfortunately, you will not be able to use RBF to doublespend.</p>

CC BY-SA 3.0
2017-10-27T04:54:19.883Z
downvoted. the answer is wrong
amaclin
CC BY-SA 3.0
2017-10-27T04:57:49.540Z
my answer is based on src/validation.cpp:653 in bitcoin-core, unless I misunderstood something. Double-spending an already spent output will cause a transaction to be included in setConflict, so the DoS score will be incremented for the node that relays the conflict tx.
rny
CC BY-SA 3.0
2017-10-27T04:29:30.890Z
2017-10-27T04:29:30.890Z
rny
<p>Is there an easy to understand step by step guide I can execute to create a double spend and get the unconfirmed transaction reversed back into the original wallet so I can resend it with a higher fee and get it delivered?</p>

CC BY-SA 3.0
2017-10-27T04:25:39.483Z
You can try sending the same amount but this time with a little more free than usual so that this transaction gets confirmed faster than the previous one.
remedcu
CC BY-SA 3.0
2017-10-27T08:25:41.920Z
I dont know how wallets work but he should make sure to reuse previously sent outputs, to invalidate older transaction.
croraf
<blockchain><transaction-fees><unconfirmed-transactions>
How do I reverse an unconfirmed transaction to the original wallet
Iyke Ukaegbu
# How do I reverse an unconfirmed transaction to the original wallet

(Asked by: username_0 on 2017-10-27)

Is there an easy to understand step by step guide I can execute to create a double spend and get the unconfirmed transaction reversed back into the original wallet so I can resend it with a higher fee and get it delivered?

**Tags:** blockchain, transaction-fees, unconfirmed-transactions

> **Comments:**
> **username_1**: You can try sending the same amount but this time with a little more free than usual so that this transaction gets confirmed faster than the previous one.  
> **username_2**: I dont know how wallets work but he should make sure to reuse previously sent outputs, to invalidate older transaction.  

---

## 4 answers

### Answer by username_3 on 2017-10-27. Score: 1

> Is there an easy to understand step by step guide

No. There is no **easy to understand** guide if you do not understand the underlying processes.

> I can execute to create a double spend and get the unconfirmed
> transaction reversed back into the original wallet

The transactions can not be "reversed back" and are not going "to/from the wallet".

> so I can resend it with a higher fee and get it delivered?

The doublespending transaction is the transaction which uses the same input set, but has another outputs/fees. You do not need to do two steps (a) reverse original transaction (b) send another transaction with higher fees, because this is one step.

As far as I know, some wallets contain Replace-By-Fee features, but I use my own program. It is not "easy-to-understand", but it works


---

### Answer by username_4 on 2017-10-27. Score: 0

No, but if your concern only is to make the transaction to go through you can google for transaction priority services.

several miners offer services to pay extra fees to expediate transactions that would otherwise be stuck with too low fee.


---

### Answer by username_5 on 2018-09-25. Score: 0

you can not reverse sent transaction. It is in mem pool and waiting to be picked up.
you can send double spend transaction with higher fee to another nodes, if your first transaction is not picked by miners yet there is very very low chance your new transaction will be processed first as miners might pick with high fee.

Eventually only one tx will be processed.


---

### Answer by username_6 on 2017-10-27. Score: -1

No. That type of double-spend will produce a conflict and will get your node DoS banned assuming that you've already broadcasted an earlier transaction that spent the UTXOs.

Unfortunately, you will not be able to use RBF to doublespend.

> **Comments:**
> **username_3**: downvoted. the answer is wrong  
> **username_6**: my answer is based on src/validation.cpp:653 in bitcoin-core, unless I misunderstood something. Double-spending an already spent output will cause a transaction to be included in setConflict, so the DoS score will be incremented for the node that relays the conflict tx.  

---

