minconf=nnn don't works in CLI?

[bitcoinex]

Code:

bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel minconf=10
error: type mismatch
bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel 
0.000000000000000

or I did not understand the format of command?

[theymos]

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.

[knightmb]

Code:

bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel minconf=10
error: type mismatch
bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel 
0.000000000000000

or I did not understand the format of command?

Should be

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.

[bitcoinex]

Code:

bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel minconf=10
error: type mismatch
bitcoin@s7:~$ ./bitcoin-0.3.8/bin/64/bitcoin getreceivedbylabel mylabel 
0.000000000000000

or I did not understand the format of command?

Should be

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

[bitcoinex]

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.

[LZ]

Will it be fixed for CLI sometime? I tested with 0.3.20 and got the same result.

[Gavin Andresen]

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.

[bitcoinex]

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.

... but maybe we should just change how the help text shows default arguments or improve the documentation.

[LZ]

I think it should be [confirmations] instead of [minconf=1]. Thanks.