Thanks for the clarification.
Holy cow, I ported this code and tests, but forgot entirely the "Filter matching algorithm". (IsRelevantAndUpdate(Tx) method)
I was so sure I knew what the bloom filter was, I did not took time to scroll to the algorithm of the BIP, nor the methods.
Topic: Correct way to track wallet transactions ? (Read 530 times)
You should read BIP37 which is about bloom filtering. Filters can be used to match against inputs and outputs as well as transaction IDs.
I noted that BIP32 talk about setting a filter to peer nodes to get notified if you are interested into a transaction.
I thought using that to track transaction relevant to my wallet. But does such method is weak transaction malleability ?
The only way to resist transaction malleability is to listening for every transaction, in a block or in mem pool, and check their input/output script to know if they are relevant to you.
Does such thing is too difficult to keep up with the flow of transaction ? Why companies like MtGox insists on using the transaction hash to track transactions ?
I thought using that to track transaction relevant to my wallet. But does such method is weak transaction malleability ?
The only way to resist transaction malleability is to listening for every transaction, in a block or in mem pool, and check their input/output script to know if they are relevant to you.
Does such thing is too difficult to keep up with the flow of transaction ? Why companies like MtGox insists on using the transaction hash to track transactions ?
Jump to: