[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[qwizzie]

i think the results may vary a bit due to masternodes perhaps updating to .23 ?
(active masternodes has dropped to 2497 too, indicating some are indeed most likely updating)

[BrainShutdown]

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

That's it. It is a clean install.

Thanks!

EDIT:

After updating one of the hot nodes to v23 the came as

NAY - 14
YEA - 671
ABSTAIN - 1819

[orangecycle]

I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

My YEA count is at 660 and ABSTAIN is at 1831 at block 264992.

I have also noticed that the YEA count will occasionally decrease. Why would that happen? I've seen it a few times now.

[Lebubar]

Let's compare..

lebubar@118:~$ date ; ./SeeVotes.sh
Thu May  7 17:53:55 UTC 2015
YEA 681
NAY 14
ABSTAIN 1811

Edit:
The two method give different result :

lebubar@148:~$ ./dashd masternode list votes | grep -c YEA
681
lebubar@148:~$ ./dashd masternode list votes YEA | wc -l
683

[Limx Dev]

10 % ?? masternode vote nay
Sorry that I find too much.

Just think of all that funded development you can just port over to your clone.
Sorry I would take your criticisms more seriously if you were contributing to the code not just cloning.

And you won't say it's too much if you come up with something amazing that requires funding and said funding gets approved.

To compete in the global leagues without having to give in to seed funding it's a drop in the ocean.

Is just my opinion. And our code also has differences. e.g. QT Paperwallet, 5 min BlockTime, static reward.

lol, pretty awesome features. What did it take you, a few minutes to change a few variables around? Please.

Please note, this was an update for limecoinx. This is not a new coin. I myself am also dash node operator. I'm on your side!

Regards

[Lebubar]

Vote: Self-sustainable Decentralized Governance by Blockchain

https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825/

BUMP new page.

Don't forget to vote, you have 2 weeks. (Well exactly : 1 week 6 days and 4 hours left )

From a start-many wallet : “masternode vote-many nay”. “masternode vote-many yea”.
From a single MN hot daemon  just : “./dashd masternode vote yea” or “./dashd masternode vote nay”.

Verify your vote with "./dashd masternode list votes | grep  <YourMN_IP>"

EDIT : Current status of the vote :
lebubar@198:~$ date -u ; ./SeeVotes.sh
Thu May  7 18:13:14 UTC 2015
YEA: 683
NAY: 14
ABSTAIN (didn't vote yet): 1816


I will have my Hero status one day???

[Minotaur26]

Dash Video Guides for Newbies

If you are new to Dash or crypto in general, dont forget to visit our Youtube channel https://www.youtube.com/user/DarkcoinTV/videos
There are a lot of great guides on how to get coins, encrypt your wallet, etc. And the video guide team is working hard to add more guides all the time. Make sure to visit the channel.

[Minotaur26]

Please note, this was an update for limecoinx. This is not a new coin. I myself am also dash node operator. I'm on your side!

Regards

Glad to have you on board, consider contributing to the code since you have the ability to do that, the dev team is always in need of help.

[razen489]

Dash Video Guides for Newbies

If you are new to Dash or crypto in general, dont forget to visit our Youtube channel https://www.youtube.com/user/DarkcoinTV/videos
There are a lot of great guides on how to get coins, encrypt your wallet, etc. And the video guide team is working hard to add more guides all the time. Make sure to visit the channel.

very well useful for the new mainstream people

[coins101]

Dash Video Guides for Newbies

If you are new to Dash or crypto in general, dont forget to visit our Youtube channel https://www.youtube.com/user/DarkcoinTV/videos
There are a lot of great guides on how to get coins, encrypt your wallet, etc. And the video guide team is working hard to add more guides all the time. Make sure to visit the channel.

Great work.

Props to all involved!

[splawik21]

btw nice buys of btc! probably to buy more dash, setup nodes and let the votes go ! )

edit: v12 will bring vote-alias option, cool, thnx devs

[Lebubar]

btw nice buys of btc! probably to buy more dash, setup nodes and let the votes go ! )

edit: v12 will bring vote-alias option, cool, thnx devs

How did you make the vote with your sharing MN?
You ask all customer, and if >50% for a MN agree then you vote?
 

[GilAlexander]

How can I obtain right number of votes? Neither restart nor resync doesn't help on my mn daemon ver 23.

[RenegadeMan]

I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

Guys I'm a bit worried about all these varying results we're seeing posted here. It currently has all the accuracy of a vote managed by a random number generator!

Forgetting all those fancy ./dashd commands for a moment, if I simply do a "masternode list votes" in my client (which has been upgraded to .23) and copy/paste the results into a spreadsheet, using the "Find All" function in Excel's "Find and Replace" I get the following:

YEA = 240
NAY = 14
ABSTAIN = 2289

Which totals to 2543

Which is pretty close to the 2546 masternodes currently showing on dashninja.pl

Soooo....someone needs to do a check whether the 680+ YEA's being noted in other postings is even remotely correct or there's a bug in either that calculation or the results I'm getting from a straight "masternode list votes" command inside the console of the .23 client.

[illodin]

Vote: Self-sustainable Decentralized Governance by Blockchain

https://dashtalk.org/threads/vote-self-sustainable-decentralized-governance-by-blockchain.4825/

Great, great and great!!!

I have some vote and I'll vote tonight, ready to begin with the decentralized governance.

 

Carefully read this proposal.  It utilizes a commingled project wallet/blockchain store/escrow.  I don't see this as a true decentralized system.  Other alternatives may work better with less risk.

Yes, on my first post I din't had read all the proposal and the remarks yet...
So patience we'll see what they will  answer to the doubt on dashtalk.

Actually, I see no reason why funding the development of the project needs to be purely decentralized.  We have very decentralized voting (albeit only Masternode owners), why do we have to have a "decentralized wallet" to deposit coins into.  It makes no sense.  It isn't functional any other way, and it is still secured by the same decentralized network that secures everyone's wallet. 

This proposal will force funds into an escrow account exposed to theft/confiscation/loss/tax. The risk is higher with the more account holders, along with additional delays with more signers to get the funds out. Any account holder can be accused of something "illegal" in the eyes of a government entity and it will be traced back to this account.  I believe there are also additional tax consequences with block rewards going into a fund and then separated to project owners.  Plus a lot will need to be implement to even make this work - multisig masternode controls, budget software, budget voting, masternode approval for funds each month.

This proposal also has no mechanism to not fund this account(or return funds), so over time when the best projects are completed and the funds will be spent on poor projects or wasted.  A much bigger deal in a few years when DASH is 10x or 100x it's value and 10% of the block rewards is not the $290k/year like it is today.(although the other post of Evan's suggested a way to return funds, it isn't in this proposal)

This is the decentralized vision that I see.  
Each project owner controls his/her own wallet with the funds.  Each project is directly paid similar to masternodes getting payments over time from block rewards, only the project owner receives and controls the funds.  Quick, simple, no 'central fund' at risk, no fund manager/s.  Each project would get paid their specific % of the block rewards they request so there isn't any funds sitting in a queue waiting accumulate before they can be sent out each month.  The funding mechanism would also be the voting mechanism.  51% yes votes gets a project in the queue, and highest yes% gets priority until the 10% cap is reached.  Projects get voted in every 3 months and each project has a set limit for 3 months of block rewards.

Before voting myself I'd like to see more discussion about this. Pros and cons vs current proposition.

[splawik21]

btw nice buys of btc! probably to buy more dash, setup nodes and let the votes go ! )

edit: v12 will bring vote-alias option, cool, thnx devs

How did you make the vote with your sharing MN?
You ask all customer, and if >50% for a MN agree then you vote?
 

So far doing the survey after all I`ll see how many MNs goes Yea and how many Nay.
After all in masternode.conf will leave only nodes for Yea and vote-many.... the same with Nay....

[Lebubar]

I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

Guys I'm a bit worried about all these varying results we're seeing posted here. It currently has all the accuracy of a vote managed by a random number generator!

Forgetting all those fancy ./dashd commands for a moment, if I simply do a "masternode list votes" in my client (which has been upgraded to .23) and copy/paste the results into a spreadsheet, using the "Find All" function in Excel's "Find and Replace" I get the following:

YEA = 240
NAY = 14
ABSTAIN = 2289

Which totals to 2543

Which is pretty close to the 2546 masternodes currently showing on dashninja.pl

Soooo....someone needs to do a check whether the 680+ YEA's being noted in other postings is even remotely correct or there's a bug in either that calculation or the results I'm getting from a straight "masternode list votes" command inside the console of the .23 client.

Evan explain a bit earlier about this.

Did your daemon was always running (without stop) since the beginning of the vote?

Edit: I made some test, running my script before a MN of mine voting . And after, and always work well.
The result are (+-1 depend on the method of count with two differents commands):
YEA 708
NAY 14
ABSTAIN 1824

[Lebubar]

btw nice buys of btc! probably to buy more dash, setup nodes and let the votes go ! )

edit: v12 will bring vote-alias option, cool, thnx devs

How did you make the vote with your sharing MN?
You ask all customer, and if >50% for a MN agree then you vote?
 

So far doing the survey after all I`ll see how many MNs goes Yea and how many Nay.
After all in masternode.conf will leave only nodes for Yea and vote-many.... the same with Nay....

What prove the customer, that you don't make the vote as "YOU" want..?

You are powerfull man now with all this vote power. 

[RenegadeMan]

I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

Guys I'm a bit worried about all these varying results we're seeing posted here. It currently has all the accuracy of a vote managed by a random number generator!

Forgetting all those fancy ./dashd commands for a moment, if I simply do a "masternode list votes" in my client (which has been upgraded to .23) and copy/paste the results into a spreadsheet, using the "Find All" function in Excel's "Find and Replace" I get the following:

YEA = 240
NAY = 14
ABSTAIN = 2289

Which totals to 2543

Which is pretty close to the 2546 masternodes currently showing on dashninja.pl

Soooo....someone needs to do a check whether the 680+ YEA's being noted in other postings is even remotely correct or there's a bug in either that calculation or the results I'm getting from a straight "masternode list votes" command inside the console of the .23 client.

Evan explain a bit earlier about this.

Did your daemon was always running (without stop) since the beginning of the vote?

Yes, I upgraded to .23 within about 10 minutes of Evan posting the vote announcement and it's been running ever since.

[Lebubar]

I get this from a daemon updated an synced for a couple of hours:

NAY - 1
YEA - 47
ABSTAIN - 2452

I'm on v23 but it's a normal daemon. Does it need to be a masternode (hot/cold) wallet to get the correct results?

I was getting weird results on one of my daemons, then I restarted it and get:

./dashd masternode list votes YEA | wc -l
664

./dashd masternode list votes NAY | wc -l
16

./dashd masternode list votes ABS | wc -l
1834

Maybe there's a bug? Try restarting your client and see if it shows the correct votes

PS. Votes don't sync when you open your client. So to watch the progress of the vote you must have had a client open before the vote started (any v11.2 would work), then update to v11.2.23 to see the correct count.

Guys I'm a bit worried about all these varying results we're seeing posted here. It currently has all the accuracy of a vote managed by a random number generator!

Forgetting all those fancy ./dashd commands for a moment, if I simply do a "masternode list votes" in my client (which has been upgraded to .23) and copy/paste the results into a spreadsheet, using the "Find All" function in Excel's "Find and Replace" I get the following:

YEA = 240
NAY = 14
ABSTAIN = 2289

Which totals to 2543

Which is pretty close to the 2546 masternodes currently showing on dashninja.pl

Soooo....someone needs to do a check whether the 680+ YEA's being noted in other postings is even remotely correct or there's a bug in either that calculation or the results I'm getting from a straight "masternode list votes" command inside the console of the .23 client.

Evan explain a bit earlier about this.

Did your daemon was always running (without stop) since the beginning of the vote?

Yes, I upgraded to .23 within about 10 minutes of Evan posting the vote announcement and it's been running ever since.

Oh!... Well I don't know (I think my MN give a good result), or during those 10 minutes a lot of YEA voting occurred