<p>I personally would look for newly spent outputs as opposed to TXIDs.  The outputs get spent the exact same way in a malleability attack.</p>

<p>So create a hash based off of the inputs into the transaction, and when a TX comes in calculate that internal hash and check off of that.</p>

CC BY-SA 3.0
2014-06-02T14:46:53.163Z
2014-06-02T14:46:53.163Z
shemnon
<p>What is the best way (in terms of security or resources) to track my outgoing transactions through the RPC API? </p>

<p>I would like to be able to track them down using their tx id and also to have a fallback mechanism for when my outgoing transaction's id changes as a result of a malleability attack.</p>

<raw-transaction><transaction-malleability>
Tracking outgoing transactions & malleability attack
Doug Peters
# Tracking outgoing transactions & malleability attack

(Asked by: username_0 on 2014-06-02)

What is the best way (in terms of security or resources) to track my outgoing transactions through the RPC API?

I would like to be able to track them down using their tx id and also to have a fallback mechanism for when my outgoing transaction's id changes as a result of a malleability attack.

**Tags:** raw-transaction, transaction-malleability


---

## 1 answers

### Answer by username_1 on 2014-06-02. Score: 2

I personally would look for newly spent outputs as opposed to TXIDs. The outputs get spent the exact same way in a malleability attack.

So create a hash based off of the inputs into the transaction, and when a TX comes in calculate that internal hash and check off of that.


---

