|
Title: minconf=nnn don't works in CLI? Post by: bitcoinex on August 05, 2010, 10:22:50 PM Code: bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel minconf=10 or I did not understand the format of command? Title: Re: minconf=nnn don't works in CLI? Post by: theymos on August 05, 2010, 10:32:47 PM It's a bug with Bitcoin's JSON-RPC client, I think. I get that for all commands with more than one parameter. Try using some other client (JSON-RPC PHP, for example) to do it.
Title: Re: minconf=nnn don't works in CLI? Post by: knightmb on August 05, 2010, 10:57:28 PM Code: bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel minconf=10 or I did not understand the format of command? bitcoin getreceivedbylabel "Your Address" 0 Your label must be in "" if it has a space in it and the next sytax is the minimum number of confirmations to count towards the total. So if that command spits back 10.00.... for example and you changed the last number to 4000 (meaning, only count transactions that have 4000 confirmations or more) then you might get back a 0.000... for example if you have no transactions with that many confirmations. Title: Re: minconf=nnn don't works in CLI? Post by: bitcoinex on August 06, 2010, 12:36:48 AM Code: bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel minconf=10 or I did not understand the format of command? bitcoin getreceivedbylabel "Your Address" 0 Your label must be in "" if it has a space in it and the next sytax is the minimum number of confirmations to count towards the total. So if that command spits back 10.00.... for example and you changed the last number to 4000 (meaning, only count transactions that have 4000 confirmations or more) then you might get back a 0.000... for example if you have no transactions with that many confirmations. :) execve do not let me spoil label with a spaces Title: Re: minconf=nnn don't works in CLI? Post by: bitcoinex on August 06, 2010, 12:41:43 AM It's a bug with Bitcoin's JSON-RPC client, I think. I get that for all commands with more than one parameter. Try using some other client (JSON-RPC PHP, for example) to do it. No, console client is better now: http://bitcointalk.org/index.php?topic=703.msg7709#msg7709 I don't think it would be difficult to fix this problem. Title: Re: minconf=nnn don't works in CLI? Post by: LZ on February 15, 2011, 05:38:25 PM Will it be fixed for CLI sometime? I tested with 0.3.20 and got the same result.
Title: Re: minconf=nnn don't works in CLI? Post by: Gavin Andresen on February 15, 2011, 07:07:14 PM The help text is misleading; never pass the "foo=" part.
Somebody could teach bitcoin to accept either getreceivedbyaccount foo 10 or getreceivedbyaccount address=foo minconf=10 ... but maybe we should just change how the help text shows default arguments or improve the documentation. Title: Re: minconf=nnn don't works in CLI? Post by: bitcoinex on February 16, 2011, 01:09:02 PM The help text is misleading; never pass the "foo=" part. Somebody could teach bitcoin to accept either getreceivedbyaccount foo 10 or getreceivedbyaccount address=foo minconf=10 First option is better if you do not intend to use GNU options format '--xxx'. (And it is easier to implement on C.) But for the convenience of future users make better use a GNU options. Then can be written a good autocomplete for shell. Quote ... but maybe we should just change how the help text shows default arguments or improve the documentation. Title: Re: minconf=nnn don't works in CLI? Post by: LZ on February 17, 2011, 12:08:24 PM I think it should be [confirmations] instead of [minconf=1]. Thanks.
|