RPC: Scanforunspent

[iFoggz]

Another RPC tool mainly aimed at multisig. I recently added a consolidation tool for multisig addresses however I felt this tool is also needed for managing multisig utxos. This tool is designed for scanning of a specified address for unspent utxos. This can also be used on non-multisig addresses as well. This tool also offers exporting of data into txt or xml

This uses some of the code works of consolidation of multisig utxos.

Added:

• Scan block range for any utxos linked to an address that are not spent.
• Option to export to xml or txt file in -backupdir
• Display results in rpc for ease of use.
• I've tested this on both mainnet/testnet.
• Use stringstream for faster building for exporting data.

here is a rpc output from test

scanforunspent 2N3tWtXU4azezQjXushYbkicq11xnkEufEw 1030000 1040000 true txt

[
[
{
"txid": "d5f7a9bd915e35f8d56189628f2a78764c8bb5dcb088fdca70d3f880699300b4",
"vout": 1,
"value": 71011.77755834
},
{
"txid": "54e35e53294678fee4c008c9bcda364b4609adedf64cc589eaf8fa14f953bdaf",
"vout": 0,
"value": 4136.15581166
}

@jamescowens @cyrossignol review and mention any changes or ask any questions
],
{
"Block Start": 1030000,
"Block End": 1040000,
"Total UTXO Count": 2,
"Total Value": 75147.93337000
}
]

Output of a xml file:

<?xml version="1.0" encoding="UTF-8"?>
<id>
  <tx1>
    <txid>d5f7a9bd915e35f8d56189628f2a78764c8bb5dcb088fdca70d3f880699300b4</txi$
    <vout>1</vout>
    <value>71011.77755834</value>
  </tx1>
  <tx2>
    <txid>54e35e53294678fee4c008c9bcda364b4609adedf64cc589eaf8fa14f953bdaf</txi$
    <vout>0</vout>
    <value>4136.15581166</value>
  </tx2>
</id>

Output of a txt file:

TXID / VOUT / Value
d5f7a9bd915e35f8d56189628f2a78764c8bb5dcb088fdca70d3f880699300b4 / 1 / 71011.77755834
54e35e53294678fee4c008c9bcda364b4609adedf64cc589eaf8fa14f953bdaf / 0 / 4136.15581166

This will make the ease of use for foundation easier as we will be able to keep track and maintain foundation utxos more efficiently and effectively.

[jamescowens]

@cyrossignol Let's get this reviewed and merged today. I want to get this one done and also all of the stuff in the integrated_scraper_2 tracking PR, and then we are going to do an interim release.

[jamescowens]

Looks good. Should we create a subdirectory under the walletbackups directory to store this stuff, or maybe a new directory under the data directory, since people may have automated sweep scripts that would get confused by files other than wallet/conf file backups?

[iFoggz]

that is possible to do. i'll honour the -backupdir and just make a subdirectory within that. what should we call it? walletbackups/rpc ?

[jamescowens]

Perfect.

[jamescowens]

utACK

[cyrossignol]

Since we're already building up the UTXO list in txres, we can support JSON export without much additional effort:

exportoutput << txres.write(2); // 2 = indent spacing

[cyrossignol]

Can we move the LOCK into the nested scope?

[iFoggz]

yes i'll move in inward when i get back home

[cyrossignol]

If we want to use XML for a machine-readable format, we may want to move nCount into a child element:

<tx>
  <num>1</num>
  ...
</tx>

...or an attribute:

<tx num="1">...</tx>

...or remove it altogether instead of appending it to the tag name. This prevents some XML parsers from logically grouping the <tx> items into a list structure.

[iFoggz]

originally i wanted by but can't have numbers in main part of tag. i'll play around with this idea

[iFoggz]

num="1" doesnt do anything really but cleaner then <tx#> and probably better supported for xml parsers