Author

Topic: Tracking outgoing transactions / malleability attack (Read 389 times)

newbie
Activity: 15
Merit: 0
What is the best way (in terms of security and/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.
Jump to: