sorry typing errorWhat are you trying to do?
now I got this error when I want to vote
Error: Error parsing JSON:yes
?? what does it means
sorry typing errorWhat are you trying to do?
Its "yea"sorry typing error
now I got this error when I want to vote
Error: Error parsing JSON:yes
?? what does it means
Here's the instruction how to vote:sorry typing error
now I got this error when I want to vote
Error: Error parsing JSON:yes
?? what does it means
now I got thisNaruto - if your wallet has only one masternode, do:
(on the command-line):
./dash-cli mnbudget vote eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes
./dash-cli mnbudget vote cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
./dash-cli mnbudget vote 428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109 yes
(on console):
mnbudget vote eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes
mnbudget vote cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
mnbudget vote 428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109 yes
Hmm.. Is it a masternode wallet? or your masternode is down?now I got this
Error upon calling SetKey
Yes it is a masternode wallet. No my masternode is not down!Hmm.. Is it a masternode wallet? or your masternode is down?
Did you setup your MN by dash.conf or by masternode.conf?Yes it is a masternode wallet. No my masternode is not down!
I have setup in masternode.conf and it is fine.Did seup your MN by dash.conf or by masternode.conf?
"vote" is for single-masternode setup (using dash.conf)
"vote-many" and "vote-alias" are for multi-musternode setup (using masternode.conf)
Then you should use "vote-many" or "vote-alias" and not "vote"I have setup in masternode.conf and it is fine.
I got "Error: Error parsing JSON:yes" when I type (mnbudget vote-alias mn01 eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes)Then you should use "vote-many" or "vote-alias" and not "vote"
Oh, ****......I got "Error: Error parsing JSON:yes" when I type (mnbudget vote-alias mn01 eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes)
And I got "Error upon calling SetKey" when I type (mnbudget vote eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes)
Thanks for the help . Vote success nowOh, ****......we forgot to implement vote-alias....
It's only in help message but there is no actual implementation, so vote-many is the only option for multi-masternode setup for now... sorry![]()
Look at the last block payment at block=2002228, this is exactly 8 years in the future given uniform 2.5 minute block lengths, although it can be changed I suppose.Evan, can you expand on how long this funding is expected to last for the core-team and public-awareness projects?
8 years of job security for the core-devs, sure no problem.Look at the last block payment at block=2002228, this is exactly 8 years in the future given uniform 2.5 minute block lengths, although it can be changed I suppose.
Probably just a safe value. payments can be voted down in mid payment by the masternodes anyway, its not permanent as I understand it.8 years of job security for the core-devs, sure no problem.
But an 8 year commitment to a public-awareness campaign just seems wrong from a marketing strategic point of view. We don't even know how widespread DASH will be a year from today.
Is this true?.[...] payments can be voted down in mid payment by the masternodes anyway, [...]
yep, masternode-owners can always change their vote to "no" and with enough "no" voters that budget will be gone. The budget system is very flexible in that way....Is this true?
./dash-cli mnbudget projection
{
"core-team" : {
"URL" : "goo.gl/V52wZd",
"Hash" : "eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487",
"BlockStart" : 332320,
"BlockEnd" : 2002228,
"TotalPaymentCount" : 100,
"RemainingPaymentCount" : 100,
"PaymentAddress" : "XtspXMnoGt4RF23CZ7MQQ7NFmkAebMUNME",
"Ratio" : 0.99918765,
"Yeas" : 1225,
"Nays" : 1,
"Abstains" : 0,
"TotalPayment" : 117600.00000000,
"MonthlyPayment" : 1176.00000000,
"Alloted" : 1176.00000000,
"TotalBudgetAlloted" : 1176.00000000,
"IsValid" : true,
"IsValidReason" : "",
"fValid" : true
},
"reimbursement" : {
"URL" : "goo.gl/V52wZd",
"Hash" : "428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109",
"BlockStart" : 332320,
"BlockEnd" : 357244,
"TotalPaymentCount" : 1,
"RemainingPaymentCount" : 1,
"PaymentAddress" : "XmxCEosWmtgDLS4BpAS8MnwYSEnsyMLbRF",
"Ratio" : 0.99750416,
"Yeas" : 1194,
"Nays" : 3,
"Abstains" : 0,
"TotalPayment" : 2529.00000000,
"MonthlyPayment" : 2529.00000000,
"Alloted" : 2529.00000000,
"TotalBudgetAlloted" : 3705.00000000,
"IsValid" : true,
"IsValidReason" : "",
"fValid" : true
},
"public-awareness" : {
"URL" : "goo.gl/V52wZd",
"Hash" : "cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189",
"BlockStart" : 332320,
"BlockEnd" : 2002228,
"TotalPaymentCount" : 100,
"RemainingPaymentCount" : 100,
"PaymentAddress" : "XxTqjYd4bpkTA6yP1gmo5maMkPynT6YvbG",
"Ratio" : 0.98680956,
"Yeas" : 1192,
"Nays" : 16,
"Abstains" : 0,
"TotalPayment" : 215600.00000000,
"MonthlyPayment" : 2156.00000000,
"Alloted" : 2156.00000000,
"TotalBudgetAlloted" : 5861.00000000,
"IsValid" : true,
"IsValidReason" : "",
"fValid" : true
}
}
I just picked a number larger than what I thought we would actually need! Granted it was too big, because people seem to think once approved, always approved. However budgets are very temporary things, they can be removed at any time. We're going to kill all of these proposals in 2 or 3 months and resubmit after we've figured out exactly what we want to do.8 years of job security for the core-devs, sure no problem.
But an 8 year commitment to a public-awareness campaign just seems wrong from a marketing strategic point of view. We don't even know how widespread DASH will be a year from today.
So hypothetically, if enough people change their vote between now and the time the superblock with the payment is created, does that mean that the budget proposal is immediately denied and won't get paid, or does changing of votes only affect the next budget cycle?I just picked a number larger than what I thought we would actually need! Granted it was too big, because people seem to think once approved, always approved. However budgets are very temporary things, they can be removed at any time. We're going to kill all of these proposals in 2 or 3 months and resubmit after we've figured out exactly what we want to do.
i do not agreeAll budgets have officially passed! No more voting is needed at this point.
(unless you're voting just because you want to try it... in that case, go for it)
I agree with tungfa and was going to write something similar to this. Voting is never really finished as we masternode owners can change our vote at any time (from my understanding). So the reality is proposals should get as many yea votes as possible so as to negate the current nay votes and any possible nay votes in the future.i do not agree
as i understand it, if the rest of the 'unvoiced' MN's all would vote "No"
the budgets would not go through
(sorry, do NOT wanna question the Masta here)
but keep voting please, as we want this as clear as possible :
PLEASE VOTE