Algorithm to scan transactions changed in recent hard fork

I had built a transaction scanning library in JavaScript, based upon Luigi1111's code here:

I tried testing my library again this morning and found that it no longer detects owned outputs in a transaction. The linked page from Luigi also has this problem, so not just my lib. Old txns still scan okay, but my newer ones (created today) do not.

I assume this is because something about the tx format or the scanning algorithm changed in the most recent hard fork. Just wondering if anyone can tell me what part of tx scanning changed (save me some time digging through the code, git logs, etc)?

Library is here, currently not working for new transactions:

submitted by /u/fatalglory
[link] [comments]

Leave a Reply

Your email address will not be published. Required fields are marked *