The nu client remembers which motion to vote even after the client is restarted. Where is this voting info stored? Is it in walletS.dat?
A related question, How do I put the setvote command in nu.conf for a daemon?
The nu client remembers which motion to vote even after the client is restarted. Where is this voting info stored? Is it in walletS.dat?
A related question, How do I put the setvote command in nu.conf for a daemon?
@sigmike would have to answer the first question.
To run the command for the daemon you just run setvote as an RPC command with the vote JSON string as a parameter value. Remember to wrap the whole string in single quotes ’ '.
Like this:
./nud setvote '{
"custodians" : [
{
"address" : "bPwdoprYd3SRHqUCG5vCcEY68g8UfGC1d9",
"amount" : 100.00000000
},
{
"address" : "bxmgMJVaniUDbtiMVC7g5RuSy46LTVCLBT",
"amount" : 5.50000000
}
],
"parkrates" : [
],
"motions" : ["0000000000000000000000000000000000000000"]
}'
of course you wouldn’t have all those carriage returns. You would just use one one long string like this:
./nud setvote '{ "custodians" : [ { "address" : "bPwdoprYd3SRHqUCG5vCcEY68g8UfGC1d9", "amount" : 100.00000000 }, { "address" : "bxmgMJVaniUDbtiMVC7g5RuSy46LTVCLBT", "amount" : 5.50000000 } ], "parkrates" : [ ], "motions" : ["0000000000000000000000000000000000000000"] }'
Thanks. Seems that my 0.5.1 client has "motions":["..."]
instead of "motionhash" :"..."
so a command would be
./nud setvote '{"motions":["0000000000000000...00"]}'
Ah sorry. I’ve updated the post. Thanks.
I think “motions” needs an array.
Yup. forgot that changed in 0.5.0.
Yes.