Vote: Self-sustainable Decentralized Governance by Blockchain

tungfa

Grizzled Member
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,898
6,744
1,283
we have to start somewhere,
that is my believe in this.
we can discuss this for another 2 weeks, get a new version, another 2 weeks discussion,..... (dam that will be tiering)

lets start with this and see where it takes us,
i think evan changed a lot of points raised by the community and this is a good middle ground to get this started and see where it takes us.
(i can not wait to show this off when implemented to the BTC people, and others who go for lame outside funding ;))
 

Sapereaude

Well-known Member
Foundation Member
Apr 30, 2014
191
235
203
The reason for the paranoia is that there are so many people getting arrested in the Bitcoin space with what seems like insignificant activities. Bitcoin is getting more traceable and the record is permanent. So as time goes by more technologies are used to go back into the blockchain to chase transactions. DASH is similar except when Darksend is used. It isn't now that matters with DASH at $3 as much as in 10 or 20 years when it is $100 or $10,000. The blockchain transactions are permanent and public, which makes tracking back overtime an issue. The confiscation of funds will happen when the wallet hits $100K or $1,000K or something significant. All that needs to happen is for it to be considered an "unlicensed money transmitter business" or "failing to report suspicious activity".

The questions we need to ask with this comingled escrow fund(not just today, but 10 or 20 years from now):
Is this a money transmitter account? (How are projects going to be paid in $? Is a proxy used to convert DASH to $)
Are we paying taxes with the funds? Are we giving out W2s or 1099s and hiring contractors? Is the project owner required to report as income? (This is a lot clearer if DASH is sent to one person directly from the block rewards. When a comingled fund pays for labor, I think this all changes.)

Hosting a node offsite still is not that answer. Your IP that you access your server is recorded. Further action could be taken with a proxy server to hide your access, but you get the point. It isn't as easy as just changing providers. I agree that I can be paranoid, but this proposal will cause problems over time. We are trying to find a solution that will last, not something that exposes all the masternode owners.

I am not saying 1.25% is the right number. The chart above says 1.25% and the text says 2.5%. I just picked one. 2.5% would be about $72,575/year at $3/DASH, not insignificant by my standards. Maybe we put in 10% for 1 month.

The last issue is that this 10% has no end. Let's vote in each project with a specific donation and timeframe. There is no mechanism stated above to return the funds if there are no projects, so inevitably this will get wasted on bad projects or abused as time goes on. (I don't think this is the intent of this proposal, but a forced donation like this will not end well even with the best intentions.)
I would argue that these are irrelevant questions, DASH is not valued at billions of dollars with thousands of eyes looking at it. There are not multiple multi-million dollar companies looking exploiting the tech, not law enforcement seminars on DASH, no legislative bodies wondering how to legislate DASH and hell even dark markets don't use DASH yet.

The point is that this is a prototype program we have no idea what the landscape will look like in 5,10,20 years time or how this part of the DASH project will evolve. You are attaching snow chains to the car's tires before it even starts raining, wasting time and leaving it stuck in the driveway. There are relevant questions to be asked, but not these.

Perfection is the enemy of progress.
 
  • Like
Reactions: Dunedoo and aleix

Solarminer

Well-known Member
Apr 4, 2015
762
922
163
I would argue that these are irrelevant questions, DASH is not valued at billions of dollars with thousands of eyes looking at it. There are not multiple multi-million dollar companies looking exploiting the tech, not law enforcement seminars on DASH, no legislative bodies wondering how to legislate DASH and hell even dark markets don't use DASH yet.

The point is that this is a prototype program we have no idea what the landscape will look like in 5,10,20 years time or how this part of the DASH project will evolve. You are attaching snow chains to the car's tires before it even starts raining, leaving it stuck in the driveway. There are relevant questions to be asked, but not these.

Perfection is the enemy of progress.
I think we can all hope/believe that DASH will be worth much more in the future. If we play our cards right, it will be an easy road ahead when that day arrives. Just trying to help us all get there a little easier by putting in a little more effort now.
 
  • Like
Reactions: Dunedoo

darkchild

Member
Sep 20, 2014
76
193
73
Proxima Centauri
www.dashnodes.com
Can some one explain to me why several people are so paranoid about goverments, in the sense that why in the current state of affairs would anyone care in the slightest about DASH? Maybe when we reach the 100+ million marketcap, until then I can not see any logic in worrying about governments or resonantly be able to predict the reaction, Even then if you are so petrified in your belief that this is a problem then there is a simple solution, host your node somewhere that don't require personal details. Hell if there is a problem you can always activate the node somewhere else. I feel this paranoia it has very little to do with the proposal and that your turning a feature of DASH(decentralized cold nodes) into a negative for no good reason.
Winners pre-empt. Losers react...
Failing to prepare is preparing to fail.

Sooner than later the U.S. government is either going to coming knocking or will require all cryptos including DASH to introduce key changes that will lead to total regulatory capture as we see from the article below. No one has all the answers, but so long as we have these open discussions, some members of the DASH community will no doubt step up and provide some insights and solutions to these legal/tax aspects.

I learned a long time ago to read up on government policies especially those that directly or indirectly affect my field of work, and this saved me a lot of headache down the line whereas those who didn't bother ended up making lawyers and tax consultants very rich. I may not agree with the government policies, but the government's still hold the big sticks. If DASH is going to change the crypto landscape and potentially the world of digital cash, then we have to recognize that DASH won't be operating in the fringes especially when widespread adoption kicks in. The foundations we lay down now will affect how the government perceives DASH and reacts accordingly.

Let's not be naive to think for a moment that the decisions we are making with these new DGB innovations and voting mechanisms won't send ripples and eventually financial shockwaves out into the world and affect governments that are largely controlled or influenced by the legacy financial cartels.

I also won't be surprised if Bitcoin and other cryptos start to follow the footsteps of DASH.

Article below:

-----------------

How could the government seek to force changes to an open-source software platform that’s supposed to be free from any party’s centralized control? Could it feasibly apply to other digital currencies – including bitcoin, whose governance structure has no go-to management actor like Ripple Labs? How will users react to the notion that Ripple is snooping on them even if the company is not itself a counterparty to their trades?

It also seems impossible that FinCEN could wield similar influence over the management or monitoring of bitcoin’s decentralized protocol — there is, after all, no core company leading the development and adoption of bitcoin’s technology in the way that Ripple Labs leads the ripple network. But that didn’t stop bitcoiners from worrying about whether the government might try.

Prominent bitcoin developer Peter Todd, for one, took to Twitter put this question to Gavin Andresen, who leads a team of five core developers charged with updating and maintaining bitcoin’s core code:

So @gavinandresen, thoughts on FinCEN forcing Ripple to change their core protocol to add AML? How do we protect Bitcoin from that pressure?

— Peter Todd (@petertoddbtc) May 6, 2015

And Jerry Brito, executive director of Washington-based think tank the Coin Center said, “It makes me nervous that FinCEN is asking protocol level changes from a company. Ripple is a special case and I hope that FinCEN understands that.”

Others, including New York Law School Professor Houman Shadab, made the case that FinCEN had proven that the comprehensive state-by-state regulation of bitcoin companies as money transmitters was redundant.

FinCEN’s fine of Ripple suggests that federal enforcement of AML laws is robust and that state-level regulation is unnecessary. #Bitcoin

— Houman Shadab (@HoumanShadab) May 6, 2015

One thing’s for sure, however, this action comes as as reminder that digital currencies are on enforcement agencies’ radars.

“Rock solid anti-money laundering compliance should be at the forefront of every digital currency company’s agenda,” said Perianne Boring, President of the Washington-based Digital Chamber of Commerce. (Michael Casey)

http://blogs.wsj.com/moneybeat/2015...cen-bombshell-ripple-labs-addresses-concerns/
 
Last edited by a moderator:

qwizzie

Well-known Member
Aug 6, 2014
1,780
918
183
i think we need a command that we can run in the debug console which will show the following :

% voted for YES
% voted for NO
% voted for ABSTAIN (those will actually be the people that havent voted yet)

Lets for example call it ''masternode list results'', after the command has been given it will show the correct % that voted for YES, NO, ABSTAIN
so we as community know where we stand with regards to certain voting topics.
 

Solarminer

Well-known Member
Apr 4, 2015
762
922
163
i think we need a command that we can run in the debug console which will show the following :

% voted for YES
% voted for NO
% voted for ABSTAIN (those will actually be the people that havent voted yet)

Lets for example call it ''masternode list results'', after the command has been given it will show the correct % that voted for YES, NO, ABSTAIN
so we as community know where we stand with regards to certain voting topics.
Good idea. For now try this.(linux only)
./dashd masternode list votes | grep -c YEA

And here are the latest results.
135 yes
11 no
2391 abstain
 
  • Like
Reactions: Dunedoo

darkchild

Member
Sep 20, 2014
76
193
73
Proxima Centauri
www.dashnodes.com
Good idea. For now try this.(linux only)
./dashd masternode list votes | grep -c YEA

And here are the latest results.
135 yes
11 no
2391 abstain
What if more than 51% of mastenode owners ABSTAIN from the vote after the voting window closes presumably due to lack of being aware of the vote or maybe because they were too technically challenged to run a basic command line entry.
Is there a way to send out a network alert/broadcast to masternode operators only? This way they can click on the tooltip/alert message which takes them to a page on dashtalk or dash pay with full instructions about the project and the vote.

Lots of people have friends helping them out with their masternodes as they don't keep up with all the dashtalk discussions and updates as some of us do. They are investors in masternodes but terrified of the command line.

I'm worried that without such a broadcast system, we might initially get a lot of people ABSTAINing unintentionally and affect project funding.

It might also be worth having the voting mechanism as a dummy-proof GUI feature before the end of 2015. Click on the shiny green, red or grey buttons for Yea, Nay, Abstain and then a dialogue box/modal window pops up and asks you to enter your password to confirm.

Once you vote, you can then see the results in real-time rather than getting your hands dirty in the commandline with pipes and greps to parse out specific results.
 

drkhouse

Member
Nov 22, 2014
79
19
48


For the next version, can we use yes and no like normal human beings?
nay sounds like just yawn. If you are bored press nay!

More seriously, they both work .

Also, if some dum countries try to taxe crypto, crypto users should start to find another one? As their country is probably not gonna let you or your kids be free of a real currency.
 
  • Like
Reactions: raganius

alex-ru

Grizzled Member
Jul 14, 2014
2,374
3,243
1,183
One proposal for future: it's be good to have "voting ID in command", like "masternode A-vote yes", "masternode B-vote no".
It will unlock us from "only one voting's term per definite period of time". And will make possible to organize several voting simultaneously (or 1 voting with many parameters).
 

raganius

cryptoPag.com
Foundation Member
Masternode Owner/Operator
I am also not absolutely happy about this voting and think some things may be done better way, but...
1. There are so many opinions and contradictory ideas - we could keep debating them for months... So more constructive is - to start with something, get first practical results and then correct system, than doing endless theoretical discussions.
2. For every decision - there are some logical-technical limitations, and many of them only developers are competent to estimate...
3. I realize proposed model as "release candidate (similar to initial early_2014_darksend)" that will be changed in future...

My general opinion on vote: it has to include announce - the exact way (and time?) MN ops may correct the proposed "model" in 2015... It will allow MN ops to feel more confident and stop being afraid of making "fatal mistake" by voting "yes".
i see this totally being part of it
when suddenly all MN's keep voting 'nay' (and concerns are raised in the community)
no project will get approved and the Dev team will and has to listen to the community
and we will go into the next round of discussions and eventually changes of the original idea
Fair enough. We have already taken the good path: the voted decision. Now, let's work wisely.
 
  • Like
Reactions: Dunedoo and tungfa

crowning

Well-known Member
May 29, 2014
1,414
1,997
183
Alpha Centauri Bc
  • Like
Reactions: alex-ru

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283


For the next version, can we use yes and no like normal human beings?
I dont agree with this at all, and here's why.

"yea" and "nay" is an exquisite cultural/historical reference. Its the oral version of "I vote yes/no" .. so people can say Yes and No all the time in an argument at will without ambiguity, and when it comes the time to take a voting stance, "yea or nay" causes no conflict or confusion.

Though MN's can't speak, it's a fabulous touch of class and indeed yet another sign that Evan is not only a great coder, but also well read and educated man.

.
 
Last edited by a moderator:

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
If I manage a bunch of MNs via a single masternode.conf, is there a vote-alias command so owners of particular MNs can instruct me how to place their vote?
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
If I manage a bunch of MNs via a single masternode.conf, is there a vote-alias command so owners of particular MNs can instruct me how to place their vote?
It's in the OP

"How To Vote

To vote, simply copy your masternode.conf into your dash directory, open the software then execute the command “masternode vote-many yea” or “masternode vote-many nay”.

To vote with a single masternode you can use the command “masternode vote yea” or “masternode vote nay”.
"
 
  • Like
Reactions: Sub-Ether

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
masternode vote-alias **** yea/nay
Yeah I tried that, having unlocked the wallet for 60 secs, and it just spits out the help thing

masternode "command"... ( "passphrase" )
Set of commands to execute masternode related actions...
...blah blah...
 

deusstultus

New Member
Dec 5, 2014
29
33
13
Yeah I tried that, having unlocked the wallet for 60 secs, and it just spits out the help thing

masternode "command"... ( "passphrase" )
Set of commands to execute masternode related actions...
...blah blah...
That method doesn't exist, not sure what TaoOfSatoshi meant to indicate. All you have for voting within the client right now are vote and vote-many. Also, voting does not require a wallet unlock.
 
  • Like
Reactions: TaoOfSatoshi

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
That method doesn't exist, not sure what TaoOfSatoshi meant to indicate. All you have for voting within the client right now are vote and vote-many. Also, voting does not require a wallet unlock.
That's what I suspected. It's going to be a PITA for guys who manage a lot of other peoples MNs.

I suppose they will have to importprivkey each MN to a fresh yea or nay wallet for each proposal voted on, and use a yay- masternode.conf and a nay- masternode.conf unless someone can post a simpler way, or vote-alias in implemented?
 

splawik21

Yeah, it's me....
Dash Core Group
Foundation Member
Dash Support Group
Apr 8, 2014
1,950
1,312
1,283
That's what I suspected. It's going to be a PITA for guys who manage a lot of other peoples MNs.

I suppose they will have to importprivkey each MN to a fresh yea or nay wallet for each proposal voted on, and use a yay- masternode.conf and a nay- masternode.conf unless someone can post a simpler way, or vote-alias in implemented?
This will be probably solved in next version.... I suppose as it would be integral option in dash voting system. Give our guys a bit of time and you``ll see ;) I just love them :D

edit: v12 will bring the vote-alias..... confirmed ;)
 
Last edited by a moderator:
  • Like
Reactions: TaoOfSatoshi

Sub-Ether

Well-known Member
Mar 31, 2014
1,516
1,256
183
I like how you have brought back an increase of masternode commission of an extra 5%, this will bring incentive to open more masternodes and strengthen the network after the growth has presumably leveled off later on next year.
 
  • Like
Reactions: moli

Sub-Ether

Well-known Member
Mar 31, 2014
1,516
1,256
183
I dont agree with this at all, and here's why.

"yea" and "nay" is an exquisite cultural/historical reference. Its the oral version of "I vote yes/no" .. so people can say Yes and No all the time in an argument at will without ambiguity, and when it comes the time to take a voting stance, "yea or nay" causes no conflict or confusion.

Though MN's can't speak, it a fabulous touch of class and indeed yet another sign that Evan is not only a great coder, but also well read and educated man.

.
Another excellent little flourish, subtlety and class in every area :cool:
 

David

Well-known Member
Jun 21, 2014
618
628
163
Just to clarify...do I need to load my cold wallet to vote, or can I vote on any wallet as long as the proper masternode.conf is loaded? I hate fooling with my cold wallet plus security issues...
 

deusstultus

New Member
Dec 5, 2014
29
33
13
Just to clarify...do I need to load my cold wallet to vote, or can I vote on any wallet as long as the proper masternode.conf is loaded? I hate fooling with my cold wallet plus security issues...
Just need the masternode.conf. Nothing is pulled from wallets here so you don't need to load or unlock cold wallets.
 
  • Like
Reactions: Sub-Ether

Solarminer

Well-known Member
Apr 4, 2015
762
922
163
That's what I suspected. It's going to be a PITA for guys who manage a lot of other peoples MNs.

I suppose they will have to importprivkey each MN to a fresh yea or nay wallet for each proposal voted on, and use a yay- masternode.conf and a nay- masternode.conf unless someone can post a simpler way, or vote-alias in implemented?
Or maybe you can vote from the remote servers. You only need to do either the nay or yea votes on the remote servers. Then in the masternode wallet do a vote-many and get the rest, since the votes can't be changed once voted.
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Or maybe you can vote from the remote servers. You only need to do either the nay or yea votes on the remote servers. Then in the masternode wallet do a vote-many and get the rest, since the votes can't be changed once voted.
I'll try commenting out the nays in my masternode.conf, doing a vote-many yea, then reverse the comments and do a vote-many nay.
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Just need the masternode.conf. Nothing is pulled from wallets here so you don't need to load or unlock cold wallets.
It's not working for me (this morning) I have yet to vote :( But I hope to get my vote in before we hit 51%, Though it'd be cool to be the vote that pushes it over the edge ;) LOL