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

[moocowmoo]

Thanks for your quick response, It was a easy fix, I just had to use my brain a tiny bit. Im loving your script thanks for this awesome tool  

You're welcome.  Glad you like it!

It will poll github and refuse to run if there is a newer version, so your changes will get overwritten (safely, but thats a git lesson) when a new version is pushed (and your run the sync script).

I'm going to have to update it soon to deal with alternate filesystem layouts..

Luckily .49 seems nice and stable. .50 should be a while, so I have time.

[TanteStefana2]

Now the header on the crash dialog reads "INPAG" and the text reads "runtime error 424".

I'm trying to run it on a Win 7 32bits. Same .bat

I'm sorry, but I don't believe there is a miner for a 32 bit system.  You can, however, install a linux 64bit distribution as a duel boot and run a miner if you need to.  Unless your hardware can't run it.  But if it's built the last 5 years or so (maybe longer now) it should work.

[RBCastro]

Now the header on the crash dialog reads "INPAG" and the text reads "runtime error 424".

I'm trying to run it on a Win 7 32bits. Same .bat

I'm sorry, but I don't believe there is a miner for a 32 bit system.  You can, however, install a linux 64bit distribution as a duel boot and run a miner if you need to.  Unless your hardware can't run it.  But if it's built the last 5 years or so (maybe longer now) it should work.

I found out one that is working on win32

https://github.com/tpruvot/cpuminer-multi/releases/download/v1.1-multi/cpuminer-multi-rel1.1.zip

I made a .bat to run with my other altcoins:

Code:

cpuminer-x86.exe -a x11 -b 127.0.0.1:4048 -o STRATUM -u USER.WORKER -p PASS -t 1

[Icebucket]

How to start dashd automatically again after it crashed.

run:

Code:

crontab -e 

add line:

Code:

*/1 * * * * /home/dashuser/mn_watch.sh >/dev/null 2>&1

use any editor you like and save this as "mn_watch.sh" file in user "dashuser" home directory:

Code:

#!/bin/bash
if [ -z `pidof dashd` ]; then
/home/dashuser/dashd
fi

add executable flag:

Code:

chmod u+x mn_watch.sh

PS. Use appropriate username, not "dashuser" from my example
I also assumed that dashd is located in your user home directory, change path if needed.

PPS. not tested but should work  

EDIT: ooops, tested and fixed  

This seems like the perfect solution to my all of my MN problems, But I am 5 and dont understand this, tryed but did not work, Can someone make a video for 5y olds

Putting a 10 dash bounty on this   .. if anyone is interested

(send me a priv message if you want to collect the bounty, I rarely scan every page here)

[r4vani]

We need bulk of gpu miner like this 

From Scrypt Mining migrate to Dash 

[Sub-Ether]

Now the header on the crash dialog reads "INPAG" and the text reads "runtime error 424".

I'm trying to run it on a Win 7 32bits. Same .bat

I'm sorry, but I don't believe there is a miner for a 32 bit system.  You can, however, install a linux 64bit distribution as a duel boot and run a miner if you need to.  Unless your hardware can't run it.  But if it's built the last 5 years or so (maybe longer now) it should work.

I found out one that is working on win32

https://github.com/tpruvot/cpuminer-multi/releases/download/v1.1-multi/cpuminer-multi-rel1.1.zip

I made a .bat to run with my other altcoins:

Code:

cpuminer-x86.exe -a x11 -b 127.0.0.1:4048 -o STRATUM -u USER.WORKER -p PASS -t 1

wrong .bat , you are using a solo mining own address and the port is wrong anyway. I will answer this at dashtalk..

[qwizzie]

Nice to see the numbers match here :


 

and here :




Onward and forward to 3000 active masternodes !

[Sub-Ether]

Nice to see the numbers match here :
masternodes =2524

Onward and forward to 3000 active masternodes !

whats happened to the other 500 masternodes, they can't all be waiting to buy back in, why so slow ?!

[Minotaur26]

Nice to see the numbers match here :
masternodes =2524

Onward and forward to 3000 active masternodes !

whats happened to the other 500 masternodes, they can't all be waiting to buy back in, why so slow ?!

The count is only of nodes on v12 the ones that are still on v11 are not being counted anymore. Some people just like to update after everything is stable or are just not following the forums so they may not even be aware of the updates yet.

[Triptolemoose]

Nice to see the numbers match here :
masternodes =2524

Onward and forward to 3000 active masternodes !

whats happened to the other 500 masternodes, they can't all be waiting to buy back in, why so slow ?!

The count is only of nodes on v12 the ones that are still on v11 are not being counted anymore. Some people just like to update after everything is stable or are just not following the forums so they may not even be aware of the updates yet.

Is there any way to check how many v11 masternodes are still out there?

[Solarminer]

Nice to see the numbers match here :
masternodes =2524

Onward and forward to 3000 active masternodes !

whats happened to the other 500 masternodes, they can't all be waiting to buy back in, why so slow ?!

BUY-BACK IN??

Who said they sold :-P

Thank you to the Bitcoin doubters.  I picked up another node cheap.  I am sure we will be over 3000 in no time once the good news of .49 is shown to all.  Only using 220MB of ram on this release.

[eduffield]

8/5 - Turn off enforcement / network upgrade
8/7-12 - Turn on enforcement
8/24 - Hard fork to allow for super blocks
9/6 - The very first budget block will be 332320, so that's quite a ways off (about 36 days from today)

https://dashtalk.org/threads/v12-testing-thread.5484/page-105#post-61537

Can we get an update on this? How does the "hard fork" indicated in Step 2 differ from the typical "spork" that we are used to? Hopefully it's not going to be a "cross your fingers and pray" thing like RC3's (several) attempted forks? Has it already happened, or was this date pushed back when the release was pushed back? Is the first budget block still planned for 9/6?

Thanks for any information!

Step 1 and 2 are done and were successful. We shouldn't have any failures like RC3 anymore, we have a nice framework for expansion and there's nothing in the plans that could cause issues like that one.
Step 3 isn't going to cause any problems, it's basically 4 lines of code
Step 4 was tested extensively. I'll be pushing out the first budget proposal soon, then we should see the successful payment of those items on September 6th.

[ddink7]

8/5 - Turn off enforcement / network upgrade
8/7-12 - Turn on enforcement
8/24 - Hard fork to allow for super blocks
9/6 - The very first budget block will be 332320, so that's quite a ways off (about 36 days from today)

https://dashtalk.org/threads/v12-testing-thread.5484/page-105#post-61537

Can we get an update on this? How does the "hard fork" indicated in Step 2 differ from the typical "spork" that we are used to? Hopefully it's not going to be a "cross your fingers and pray" thing like RC3's (several) attempted forks? Has it already happened, or was this date pushed back when the release was pushed back? Is the first budget block still planned for 9/6?

Thanks for any information!

Step 1 and 2 are done and were successful. We shouldn't have any failures like RC3 anymore, we have a nice framework for expansion and there's nothing in the plans that could cause issues like that one.
Step 3 isn't going to cause any problems, it's basically 4 lines of code
Step 4 was tested extensively. I'll be pushing out the first budget proposal soon, then we should see the successful payment of those items on September 6th.

Excellent--thanks for the update Evan! It's amazing to think of how much development has occurred in the last year and how far we've come since last summer!

[oblox]

How to start dashd automatically again after it crashed.

run:

Code:

crontab -e 

add line:

Code:

*/1 * * * * /home/dashuser/mn_watch.sh >/dev/null 2>&1

use any editor you like and save this as "mn_watch.sh" file in user "dashuser" home directory:

Code:

#!/bin/bash
if [ -z `pidof dashd` ]; then
/home/dashuser/dashd
fi

add executable flag:

Code:

chmod u+x mn_watch.sh

PS. Use appropriate username, not "dashuser" from my example
I also assumed that dashd is located in your user home directory, change path if needed.

PPS. not tested but should work 

EDIT: ooops, tested and fixed 

This seems like the perfect solution to my all of my MN problems, But I am 5 and dont understand this, tryed but did not work, Can someone make a video for 5y olds

Putting a 10 dash bounty on this  .. if anyone is interested

(send me a priv message if you want to collect the bounty, I rarely scan every page here)

No offense, but that's as easy as it gets. The only substitute is using whatever text editor you have on your instance to actually create the script file (vi, nano, joe, etc).

[fuzzyduck]

Think I found a Pi replacement if DASH gets a little to 'intensive'

:-D

http://www.banana-pi.org/m3.html

.49 is running rocksolid on my PI2. 10% to 20% cpu and 17%ram atm.
Muchos headroom left for more implementations! Keep 'm coming Evan!

[stealth923]

8/5 - Turn off enforcement / network upgrade
8/7-12 - Turn on enforcement
8/24 - Hard fork to allow for super blocks
9/6 - The very first budget block will be 332320, so that's quite a ways off (about 36 days from today)

https://dashtalk.org/threads/v12-testing-thread.5484/page-105#post-61537

Can we get an update on this? How does the "hard fork" indicated in Step 2 differ from the typical "spork" that we are used to? Hopefully it's not going to be a "cross your fingers and pray" thing like RC3's (several) attempted forks? Has it already happened, or was this date pushed back when the release was pushed back? Is the first budget block still planned for 9/6?

Thanks for any information!

Step 1 and 2 are done and were successful. We shouldn't have any failures like RC3 anymore, we have a nice framework for expansion and there's nothing in the plans that could cause issues like that one.
Step 3 isn't going to cause any problems, it's basically 4 lines of code
Step 4 was tested extensively. I'll be pushing out the first budget proposal soon, then we should see the successful payment of those items on September 6th.

Excellent update Evan. Thanks to you and the team!

Also cannot wait to read the upcoming white paper!

[mjsrs]

FUD is what powers Dash. I've gotten a bunch of ideas from it including the one about the masternode network being an active force to deflect attack. Keep it coming people 

Add it to acknowledgement page 

[HinnomTX]

I've upgraded my masternodes to v12.0.49 but I'm still seeing some of them drop off the list after 1-2 hours as EXPIRED. It's strange because the 'expired' masternodes are still active with port open (responding to 'dash-cli getinfo'). Anyone else having this problem?

[Lebubar]

I've upgraded my masternodes to v12.0.49 but I'm still seeing some of them drop off the list after 1-2 hours as EXPIRED. It's strange because the 'expired' masternodes are still active with port open (responding to 'dash-cli getinfo'). Anyone else having this problem?

50% of the time is because you execute the "masternode startt "xxx"" from the cold wallet that is not on the last version.

[eduffield]

I've upgraded my masternodes to v12.0.49 but I'm still seeing some of them drop off the list after 1-2 hours as EXPIRED. It's strange because the 'expired' masternodes are still active with port open (responding to 'dash-cli getinfo'). Anyone else having this problem?

Sounds like your hot node wasn't activated. I would search the log for this "CActiveMasternode::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon."