Hi,

I am trying write some JSON interface to coniserver.

By my design, this must be "currency-independent" subsystem,
so it must to work with most popular cryptocurrencies.

I see, almost all cryptocurrencies are descendants from Bitcoin,
and supports same RPC/JSON interface.

This time, I confused with listunspent request format:

1. About Bitcoin, here is stated
https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_calls_list
is stated:
listunspent    [minconf=1] [maxconf=999999]

2. Also, about Bitcoin, here
http://we.lovebitco.in/bitcoin-qt/command-reference/
is stated another:
listunspent [minconf=1] [maxconf=9999999] ["address",...]

As you see, 2nd example defines 3rd optional parameter, array of addresses.

Also, this 3rd parameter is supported in the Litecoin API:
https://litecoin.info/Litecoin_API

Also, I tested quarkcoin server - it also supports this parameter
(there is no docs, but server handles this param).

So, I make conclusion: 3rd param works everywhere, and
I can use this in the my code.
And, official 1st reference is incomplete, and must be updated.

Is my assumptions correct, or I missed something?
Is this safe and correct to use 3rd parameter?

I have two questions regarding transaction functionality:

1. Is this possible to create transaction, which sends many output onto same wallet (recipient address)?
This is needed, for example, if I want prepare many tokens, and in future send whole token to another
recipient in the transaction "1in->1out".

2. Is this possible to set transaction with zero value output to recipient?
So, this is just "send zero in the input to zero to output".
Or, create send transaction, contains non-zero input and zero output (all funds will go to miner).

I am learning bitcoin protocol, cannot understand mechanism of transaction protection vs MIM attack.

Imagine scenario:

1. Valid user A decided pay 1000BTC to user B. For do this, user A created transaction with N inputs.
Each input he signs with his PrivateKey, and populate fields scriptSig for each input transaction
with his correct digital signature. As I understand from docs, this signature signs transaction input only,
no transaction outputs, or another inputs.

2. User A send this transaction to bitcoin network.

3. Evil MIM intercept this transaction, and block user A to distribute transaction to another peers.

4. Evil MIM generates new transaction, contains all valid signed inputs from intercepted transaction from A,
but alter output(s) to his own wallet. Of course, he generates new transaction hash, etc - and this "v2"
transaction is technically valid.

5. Evim MIM publish his "v2" transaction to the network.

6. Network nodes verify v2-transaction, and found - scriptSig is correct, so transaction is valid.

7. Profit for MIM.

Of course, I understand, system by some way has been protected versus this attack.
But, I did not found in docs about protection mechanism.

Can you explain?

Thanks.