|
Title: Listunspent: is address standard feature? Post by: maxihatop on February 04, 2014, 08:58:10 PM 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? Title: Re: Listunspent: is address standard feature? Post by: Sonny on February 05, 2014, 10:04:57 AM And, official 1st reference is incomplete, and must be updated. Indeed, quite a lot of pages on the wiki are out of date. Sadly, we don't have enough volunteers to update the wiki, partly because people are required to pay 0.001 btc before they are allowed to edit the wiki. https://en.bitcoin.it/wiki/BitcoinPayment Can't help answering your problem though as I have no idea about it. |