<p>You could import the private keys used into another wallet and spend the funds there.  For instance, on Blockchain.info/wallet you simply do Advanced -> Import and import the private keys (which can be exported from Bitcoin-Qt's debug console).</p>

CC BY-SA 3.0
2013-03-13T11:07:28.307Z
2013-03-13T11:07:28.307Z
Stephen Gornick
<p>I'll take a stab at this, from a very simplistic approach.</p>

<p>The best way to replace it is to pretend it didn't happen. Reset the blockchain in use, and continue as normal. The client (or <code>bitcoind</code>) will be unaware of the transaction, and the mistake transaction will eventually be disregarded by all nodes, invalidated, and discarded.</p>

CC BY-SA 3.0
2013-03-13T02:51:51.997Z
2013-03-13T02:51:51.997Z
Colin Dean
<p>According this this WikiPage, <a href="https://en.bitcoin.it/wiki/Raw_Transactions#Multisignature_transactions" rel="nofollow">a MultiSigTransaction that doesn't include a fee may never get included in a block.</a></p>

<p>Since I've read that replacing Transactions (by version number or any other feature) isn't enabled, how can I expedite the replacement and updating of this?</p>

<transactions><block><transaction-fees><multi-signature>
How can I cancel and replace a Transaction that never gets confirmed?
makerofthings7
# How can I cancel and replace a Transaction that never gets confirmed?

(Asked by: username_0 on 2013-03-13)

According this this WikiPage, [a MultiSigTransaction that doesn't include a fee may never get included in a block.](https://en.bitcoin.it/wiki/Raw_Transactions#Multisignature_transactions)

Since I've read that replacing Transactions (by version number or any other feature) isn't enabled, how can I expedite the replacement and updating of this?

**Tags:** transactions, block, transaction-fees, multi-signature


---

## 2 answers

### Answer by username_1 on 2013-03-13. Score: 3

You could import the private keys used into another wallet and spend the funds there. For instance, on Blockchain.info/wallet you simply do Advanced -> Import and import the private keys (which can be exported from Bitcoin-Qt's debug console).


---

### Answer by username_2 on 2013-03-13. Score: 2

I'll take a stab at this, from a very simplistic approach.

The best way to replace it is to pretend it didn't happen. Reset the blockchain in use, and continue as normal. The client (or `bitcoind`) will be unaware of the transaction, and the mistake transaction will eventually be disregarded by all nodes, invalidated, and discarded.


---

