Awesome additions! Especially like the consensus check, I still have a half finished product so I'm glad yours is working right now!
I think we need a way to easily discuss these transactions and explain why we parse them a certain way. Although right now it seems Masterchest has a lot of other values compared to the other implementations. Could you see if there is something obvious that can be done to fix those differences?
Could also you perhaps add a filter to hide addresses that match on all implementations?
Those addresses where only Mymastercoins had values were a bug (just squashed) - I query all implementations for their list of addresses, it just so happens that Bitoy's is first on the list. There is whitespace in his JSON output so it was throwing off my address matching. A couple of handy trim functions and it's working again.
Re filter, I haven't built in parameters into that page for filters (though I do intend to), in the mean time will this do?
https://masterchest.info/consensus_tachikoma.aspxNice consensus check.
Starting at address
1RavenHqiZ7euZ1ETKkKP74h5SPLovdF6
Only Mymastercoins column has value on the consensus, but when I checked at the website masterchest and master-explorer have values also for this address.
Yeah see above that was a bug - if it helps I noticed you have some whitespace in your output (eg {"address": "1rdyat8oxM33EUHBaGPvEUBiBgAvXHe5M ", "balance": "0.003"}) and a couple of format issues (eg {"address": "139Dx25QXHBJD1tfLQMwASAAJrWFiM4BPz", "balance": "1E-08"}).
Thanks guys
EDIT: Looks like the link I was using for Grazcoin's implementation was wrong, corrected.