Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 1924. (Read 9723748 times)
August 19, 2015, 07:03:09 PM
Can anyone remind me why darksend can't use instantx for confirmations?
August 19, 2015, 06:35:00 PM
Anyone knows how to run the latest version of Dash on Ubuntu 14.04?
I get these files and can't open them. I'm kind of an ubuntu noob...
I get these files and can't open them. I'm kind of an ubuntu noob...
Just go to directory where qt is using terminal and execute it.
For instance, i keep my dash-qt on a desktop.
So open terminal and type
cd /home/Desktop
./dash-qt --reindex
Thanks! That worked fine!
Yes, but they're supposed to be double clickable. I've had this same issue since weeks ago in testnet. Nobody answered me back then and I've been using the terminal to start my QT wallet ever since. I figured something happened to my settings with one of the test daemons. At least one other person asked about it, but nobody ever responded, so I dropped it and made due. But if people are still getting this, it should be fixed IMO.
Bump... this is the first time I had this happen... even with chmod 755 or +x on the files.
August 19, 2015, 05:47:59 PM
So does masternode voting then solve the hard problem of 'Benevolent dictator for life' within an open source blockchain decision making conundrum that bitcoin is struggling with at the moment?
http://www.theatlantic.com/technology/archive/2014/01/on-the-reign-of-benevolent-dictators-for-life-in-software/283139/
http://www.theatlantic.com/technology/archive/2014/01/on-the-reign-of-benevolent-dictators-for-life-in-software/283139/
I know you're not meaning to be talking about Evan Duffield, but yes, I do think that's the plan. This project, Dash, still very much has a leader, thus a "Benevolent Dictator" but I'm quite sure from what he has said, he doesn't want that position for life, LOL. So how do you fill an entrepreneur's shoes? You make the people compete. Why would they compete? Because they're gonna get paid! So eventually, Evan should be able to step away knowing his project will survive
And with masternode voting + community input, direction should be a clear indication of which direction to go.Even better, Evan could one day compete for funds for a new project, just like everyone else, and start something new. He doesn't have to maintain the main program the rest of his life, but go off on his own once again, yet still be benefiting his baby, Dash. As long as we can keep his interest, we can keep Evan! You know I'm all for that! LOL
So yes, I think so
August 19, 2015, 05:44:11 PM
weird stuff! my MN got 3 payments today! In 3hour-ish intervals. 
10.5 dash in a timespan of around 9 hours. what are the ods huh!
10.5 dash in a timespan of around 9 hours. what are the ods huh!
Which version and protocol do u have on your node now?
5 nodes here and nothing since 9 days LOL
I suggest version 0.12.0.46 because it really reduces the CPU usage and is working perfectly. But yah, I think enforcement was just turned on, so people are getting payments now. I think fuzzyduck got his through luck, but now luck should be gone.
That is, if eduffield was saying that we're fully enforced when he made this comment:
https://bitcointalksearch.org/topic/m.12187571
Kind of hazy?
August 19, 2015, 05:16:26 PM
weird stuff! my MN got 3 payments today! In 3hour-ish intervals.
10.5 dash in a timespan of around 9 hours. what are the ods huh!
10.5 dash in a timespan of around 9 hours. what are the ods huh!
Which version and protocol do u have on your node now?
5 nodes here and nothing since 9 days LOL
August 19, 2015, 03:27:46 PM
@ddink7 Thanks for explanation. As is see it now "only" 50% of the 350 Dash are stolen, the remaining are regular rewarded due many owned MNs (otoh? 
). I hope one day enforcement will be truly decentralized too.
). I hope one day enforcement will be truly decentralized too. August 19, 2015, 03:23:41 PM
weird stuff! my MN got 3 payments today! In 3hour-ish intervals.
10.5 dash in a timespan of around 9 hours. what are the ods huh!
10.5 dash in a timespan of around 9 hours. what are the ods huh!
August 19, 2015, 03:20:49 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
1.) How about now?
2.) When we stop changing the masternode protocol between versions this will stop. 2 to 3 days per 3-6 months doesn't seem like much of a sacrifice in order to have the type of flexibility to development such different protocols between versions. We're able to explore different ideas and really figure out the best option for the network because of it.
Can someone explain how this hijacking works? Maybe if everyone is able to try this it would not be that unfair with all all blocks going to one person...
PS: for me ~350 Dash/day is a sacrifice. I would be happy if you can donate this amount to me every 6 month.
Miners are supposed to send 50% of the block reward to masternodes. Normally this in "enforced" (blocks without the appropriate payment to the appropriate masternode are rejected by the network). When a new version is released, consensus is not achieved instantaneously. If enforcement was left on, the network would fork. In our recent case, miners on V11 would have their blocks rejected by clients running V12, and vice versa. Evan has to wait for a consensus to emerge (usually 85%) before turning on enforcement in order to prevent forks.
P.S. If you truly have the 700 masternodes needed to generate 350 Dash/day, then it's not too great of a sacrifice. I'm not going to be crying any tears of depriving you of $1,000 a day for six days out of the year when you have $2,100,000 in assets. Sorry for the lack of sympathy.
August 19, 2015, 03:11:06 PM
So does masternode voting then solve the hard problem of 'Benevolent dictator for life' within an open source blockchain decision making conundrum that bitcoin is struggling with at the moment?
http://www.theatlantic.com/technology/archive/2014/01/on-the-reign-of-benevolent-dictators-for-life-in-software/283139/
http://www.theatlantic.com/technology/archive/2014/01/on-the-reign-of-benevolent-dictators-for-life-in-software/283139/
August 19, 2015, 03:10:24 PM
2) Is it possible to prevent this from happening during future upgrades?
2.) When we stop changing the masternode protocol between versions this will stop. 2 to 3 days per 3-6 months doesn't seem like much of a sacrifice in order to have the type of flexibility to development such different protocols between versions. We're able to explore different ideas and really figure out the best option for the network because of it.It's not a huge sacrifice, but I was wondering if it could be reduced or possibly eliminated altogether.
Perhaps, only disable enforcement if there is not a 75%+ consensus between masternodes?
Or somehow restrict consensus to only the masternodes running the newest protocol, and ignore the older protocol once 50% have upgraded?
August 19, 2015, 02:59:42 PM
Help needed after i upgraded to Windows 64x 0.12.0.46 version i keep getting the below error everytime i try launching DASH.
Make sure you are actually running v12 and not the old (v11) link or file.
If for whatever reason you want to run v11 after you installed (and run) v12 go to %appData%/Dash folder and remove (rename) masternode.conf
August 19, 2015, 02:59:09 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
1.) How about now?
2.) When we stop changing the masternode protocol between versions this will stop. 2 to 3 days per 3-6 months doesn't seem like much of a sacrifice in order to have the type of flexibility to development such different protocols between versions. We're able to explore different ideas and really figure out the best option for the network because of it.
Can someone explain how this hijacking works? Maybe if everyone is able to try this it would not be that unfair with all all blocks going to one person...
PS: for me ~350 Dash/day is a sacrifice. I would be happy if you can donate this amount to me every 6 month.
August 19, 2015, 02:58:26 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
1.) How about now?
2.) When we stop changing the masternode protocol between versions this will stop. 2 to 3 days per 3-6 months doesn't seem like much of a sacrifice in order to have the type of flexibility to development such different protocols between versions. We're able to explore different ideas and really figure out the best option for the network because of it.
The thinking of a genius..
August 19, 2015, 02:57:58 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
1.) How about now?
And here I was predicting some time tonight...you beat my expectations, as always!
August 19, 2015, 02:54:54 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
1.) How about now?
2.) When we stop changing the masternode protocol between versions this will stop. 2 to 3 days per 3-6 months doesn't seem like much of a sacrifice in order to have the type of flexibility to development such different protocols between versions. We're able to explore different ideas and really figure out the best option for the network because of it.
August 19, 2015, 02:31:01 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
As soon as enforcement is turned on...
Kinda figured that much... When does that happen?
I'm not sure it's accurate, but dashninja is reporting 99.2% of users on newest protocol (36.3% .45, 62.9% .46)
Generally it's a percentage of the system but I think I did see where it was going to be Sept 5th....
Somebody else will chime in if I'm wrong of course
i think enforcement will be turned on when at least 85% of masternodes is running .46 (could be lower, but i think that number was mentioned before)
and the planned fork starts 5th of september which is more for pools to comply with and for users to be on the correct chain by then (with their wallets).
August 19, 2015, 02:16:09 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
As soon as enforcement is turned on...
Kinda figured that much... When does that happen?
I'm not sure it's accurate, but dashninja is reporting 99.2% of users on newest protocol (36.3% .45, 62.9% .46)
August 19, 2015, 02:12:48 PM
1) How long until XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA stops hijacking 10%+ of the masternode payments?
2) Is it possible to prevent this from happening during future upgrades?
2) Is it possible to prevent this from happening during future upgrades?
August 19, 2015, 01:57:19 PM
Help needed after i upgraded to Windows 64x 0.12.0.46 version i keep getting the below error everytime i try launching DASH.
Sounds like there is a typo in your %appData%/Dash/dash.conf
August 19, 2015, 01:54:10 PM
Help needed after i upgraded to Windows 64x 0.12.0.46 version i keep getting the below error everytime i try launching DASH.
Jump to: