This also includes a little blockchain of 114 blocks (the first 100 just coinbase to reach coin-maturity) with transactions generated by the txVulcano. So lots of outputs. I adjusted the BlackBoxTest to load this data into any hub with ease.
Generically this looks like this; IsUnspent [ { "txid": "0x111111", "output": 1 }, { "txid": "0x111111", "output": 11 } ] IsUnspentReply [ { "blockHeight": 1111, "offsetInBlock": 1111, "unspent": true }, { "unspent": false } ] GetUnspentOutput [ { "txid": "0x111111", "output": 1 }, { "txid": "0x111111", "output": 0 } ] GetUnspentOutputReply [ { "blockHeight": 1111, "offsetInBlock": 1111, "unspent": true, "amount": 1111, "outputscript": "bytearray" }, { "unspent": false } ] note: txids are naturally always sha256s.
The bugreport claimed that sending an existing coinbase would give inconsistent results. This test can't find any unexpected behaviour.
This is a blackbox type testing for specific API calls.
TomZ