What does the StartingBlock property do? Does it determine how long the voting remains open?
Vote: Self-sustainable Decentralized Governance by Blockchain
- Thread starter eduffield
- Start date
What does the StartingBlock property do? Does it determine how long the voting remains open?
eduffield
Core Developer
The JSON object is pretty much ignored by the protocol. It's just used on the website to show more information to the users. If you mess that file up, it wouldn't mess with the network and it will pretty much be ignored.
That's a great idea, that will definitely help
That could be interesting - If the proposal is rejected the collateral could be added to an approved project perhaps? (or returned after some time period, but that defeats the purpose of a fee)
-Second question that may or may not be valid- How would we prevent 'imitation' requests if that's a concern:
(an exact duplicate of an existing vote, or one with a slight change in parameters that may not be immediately noticeable)
The community could police that? May get annoying as utilization shoots up.
eduffield
Core Developer
Using starting block, you can tell the network you would like to start getting paid in 3 months or so. That's also how it calculates when your payments are complete.
JGCMiner
Active member
Evan, correct me if I am wrong, but according to this new proposal the block reward will be reduced 10%. Then based on MN voting a certain number of projects are funded where the total cost of those projects must be X where 0%<= X <= 10% of the original block reward (in your example 5). Next those funds are paid by some superblocks say at the end of every month. Finally, if the total required funds are less than 10% of the original block reward then the remaining Dash is never generated (in your example the $20 or 6.667 DASH). Is that correct?
Last edited by a moderator:
Each proposal would obviously have it's own topic on this forum. Enough comments like "Project 12 is just a ripoff of project 7. Don't vote for it!" should be sufficient.
deusstultus
Member
Should rebuff user response on the voting system with this aspect. There is no response on success from client side on delivering a vote or write to debug.log. Additionally, the client side should be able to check pmn->lastVote equivalent from masternodeman as well and respond with a message indicating votes cannot be changed within the specified interval rather than just returning.
Masternode handling is obviously more important to govern this system, but if clients don't have an easy way of acknowledging the status of each vote call it complicates the process.
I don't think it would be 'earmarked' (and thus the block reward modified) in the first place. Not so much a case of never generated as never needed, never taken?
At least that's how I read it - Evan was just demonstrating a within-max-budget scenario.
Sorry to bug you all, but Crowning said I could vote via my remote masternodes. I haven't been able to vote via my local (using vote-many shows failed 1) When I vote on my remote, using dashd masternode vote yea I get no feedback, and checking here: http://178.254.18.153/~pub/Dash/masternode_payments_stats.html, the vote count didn't go up. I checked my debug log, and I can't find anything definitive searching for yea or vote or anything. The remotes and the locals were updated to v23. Thanks for any help.
Maybe I just have to load my actual wallet and put it online? I didn't want to do that
Maybe I just have to load my actual wallet and put it online? I didn't want to do that
Sorry to bug you all, but Crowning said I could vote via my remote masternodes. I haven't been able to vote via my local (using vote-many shows failed 1) When I vote on my remote, using dashd masternode vote yea I get no feedback, and checking here: http://178.254.18.153/~pub/Dash/masternode_payments_stats.html, the vote count didn't go up. I checked my debug log, and I can't find anything definitive searching for yea or vote or anything. The remotes and the locals were updated to v23. Thanks for any help.
Maybe I just have to load my actual wallet and put it online? I didn't want to do that
I voted from my MNs as well. No feedback, but if you do ./dashd masternode list vote | GREP <YOURIP> you will see your vote.
Solarminer
Well-known member
I agree. An easy way to do this would be to have the website that records the proposal take this fee. It could be used to manage and host the website.
Same here..
All vote done on hot daemon, because my cold wallet are... really cold
Checking the "masternode list votes" and was moving accordingly what I was voting.. (David "S" on votes)
when i do “masternode list votes”
all i see are "ABSTAIN" listings, no nay or yea
incl my own votes ?!
Hummm, I'm unable to get dashd masternode list vote | GREP ip to work, I get an error
Solarminer
Well-known member
This revised proposal is fantastic. Thanks Evan for making the changes.
Solarminer
Well-known member
Maybe your node doesn't show up as enabled. Try to start it from the local wallet.
Last edited by a moderator:
Lebubar
Active member
You must be on .23 version. And the daemon had to be running since the beginning of the votes.
Mine are OK :
lebubar@108:~$ ./MyMNVote.sh
MN1: YEA
MN2: YEA
MN3: YEA
MN4: YEA
MN5: YEA
MN6: YEA
MN7: YEA
MN8: YEA
MN9: YEA
MN10: YEA
MN11: YEA
MN12: YEA
MN13: YEA
cat MyMNVote.sh
echo "MN1: " `./dashd masternode list votes | grep x.y.w.z | awk -F\" '{print $4}' `
echo "MN2: " `./dashd masternode list votes | grep a.b.c.d | awk -F\" '{ print $4}' `
...
...
(yes I voted yea
)
Last edited by a moderator:
Lebubar
Active member
Ok, so to check my daemon, I had to do dashd masternodelist votes | grep IP
For any other old people out there, or prematurely senile people like myself, LOL.
Also, my vote on remote isn't taking, the one on my local (without actual wallet - only my config files loaded - worked.
For any other old people out there, or prematurely senile people like myself, LOL.
Also, my vote on remote isn't taking, the one on my local (without actual wallet - only my config files loaded - worked.