M
MangledBlue
Guest
Voted
no biggy after MN restart - ugh
crashed
no biggy after MN restart - ugh
crashed
Budget Proposal : Promotion / Reimbursement / Core Team
- Thread starter eduffield
- Start date
Then you should use "vote-many" or "vote-alias" and not "vote"
Naruto
Active member
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)
Oh, ****......
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
all went well until:
11:31:05
mnbudget vote cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
11:31:05
Error voting : Proposal not found!
Edit:
ok sorted
(Mac)
multiple MN's work fine (voting) others show me error from above
- everytime i use wallet/MN with "mnsync reset"
voting works fine
- every time i use a Wallet/MN without "mnsync reset"
I get error above
so if error I erase peers.dat and resync / resync will fail + "mnsync reset"
and all fine
Except 1 MN (it is on, listed and all green)
I do not manage to vote !
Error Message:
Failure to find masternode in list : CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )
11:31:05
mnbudget vote cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
11:31:05
Error voting : Proposal not found!
Edit:
ok sorted
(Mac)
multiple MN's work fine (voting) others show me error from above
- everytime i use wallet/MN with "mnsync reset"
voting works fine
- every time i use a Wallet/MN without "mnsync reset"
I get error above
so if error I erase peers.dat and resync / resync will fail + "mnsync reset"
and all fine
Except 1 MN (it is on, listed and all green)
I do not manage to vote !
Error Message:
Failure to find masternode in list : CTxIn(COutPoint(0000000000000000000000000000000000000000000000000000000000000000, 4294967295), coinbase )
Last edited by a moderator:
Naruto
Active member
Thanks for the help . Vote success nowOh, ****......
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
Sub-Ether
Well-known member
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.
wsmithston
New member
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.
Sub-Ether
Well-known member
Probably just a safe value. payments can be voted down in mid payment by the masternodes anyway, its not permanent as I understand it.
wsmithston
New member
Is this true?
qwizzie
Well-known member
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....
crowning
Well-known member
Defacto
Member
just...
# ./dmnvote.sh eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes
Voted successfully
# ./dmnvote.sh cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
Voted successfully
# ./dmnvote.sh 428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109 yes
Voted successfully
Good job devs! :-D
# ./dmnvote.sh eac6392cd0d63e4b2ebd3c60da2d3e13137c892cd4cd1a8f3885077ac86b7487 yes
Voted successfully
# ./dmnvote.sh cbafad18687045bb72fae611078fac09c3ec09c8379e357c36901ce84891f189 yes
Voted successfully
# ./dmnvote.sh 428438998eeb3234b232a3609d2e0f1122049241e5ecad972554ad163772a109 yes
Voted successfully
Good job devs! :-D
eduffield
Core Developer
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.
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?
Yes, so really, we're in more danger of having someone like otoh vote a proposal down and shut down a project than to get a project going. (otoh wouldn't do that, LOL) I do worry a bit about the "contractor" who's budget was approved, and he works faithfully on the project, but then his budget is voted away or superseded. I think eventually, after a proposal is approved, there is going to have to be some kind of lock in device so that the proposer knows he will get paid, at least for that month. And if he doesn't do his part, it should require something like active down votes to stop it (rather than a more popular project superseding it after he starts his proposal and thinks he is going to get paid). Or something has to be worked out. It will be complex because we're trying to make all this happen automatically within a voting system.
I know I'm not a programmer. But my career was contract administration in construction with complex specifications and standards, so I do see a lot of issues in that area that are going to need work. Very creative work, actually. If we don't figure this out, in the future, nobody will want to do business with us because they - or others will have been burned.
But that's why we're doing it this way. We're paying people whom we could never really pay as they've already done so much, and it's based on trust ATM. But we all know where Dash is going, As a world currency, it is going to be so big with so many projects, it will have to be automated.
I know I'm not a programmer. But my career was contract administration in construction with complex specifications and standards, so I do see a lot of issues in that area that are going to need work. Very creative work, actually. If we don't figure this out, in the future, nobody will want to do business with us because they - or others will have been burned.
But that's why we're doing it this way. We're paying people whom we could never really pay as they've already done so much, and it's based on trust ATM. But we all know where Dash is going,
As a world currency, it is going to be so big with so many projects, it will have to be automated.
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
Last edited by a moderator:
B
buster
Guest
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.
Can masternode owners vote on new initiatives if they already have yea/nay votes out on other initiatives? Or are we limited to a certain amount of yea/nays?
*edit I forgot to give props to the developers, community and everyone else for the effort here and the amazing results. It's great to be a part of something so special.