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

[Solarminer]

Or just run my new restart script, instead of investing in testing.    It figures out if any node is over 1 block behind the average of 7 nodes.  If it finds a slow node or gets a bad block number, it will will log the last 30 lines, shut it down nice, then kill it, and then restart it.  Cycles every 16 minutes.  You need to rename each dashd/dash-cli, do some port forwarding, and port changes in the configs to get all the nodes to run at the same time.  Delete the nodes as needed.  This should work with just two nodes.  See my previous post for the single node version.

Bring on V13, I am ready!

Code:

#!/bin/bash
#screen -dm /bcheck7.sh
#screen -X -S 11111 kill (screen -ls for 11111)
while true
do
b1=$(/home/dash/dash1-cli -datadir=/home/dash/.dash1/ getblockcount)
b2=$(/home/dash/dash2-cli -datadir=/home/dash/.dash2/ getblockcount)
b3=$(/home/dash/dash3-cli -datadir=/home/dash/.dash3/ getblockcount)
b4=$(/home/dash/dash4-cli -datadir=/home/dash/.dash4/ getblockcount)
b5=$(/home/dash/dash5-cli -datadir=/home/dash/.dash5/ getblockcount)
b6=$(/home/dash/dash6-cli -datadir=/home/dash/.dash6/ getblockcount)
b7=$(/home/dash/dash7-cli -datadir=/home/dash/.dash7/ getblockcount)
ba=$[($b1+$b2+$b3+$b4+$b5+$b6)/6]
if [ $[$b1+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash1/debug.log >> crash1.log
/home/dash/dash1-cli stop
sleep 30
pkill -9 dashd1 dash_shutoff
sleep 10
/home/dash/d1.sh
exit
fi
if [ $[$b2+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash2/debug.log >> crash2.log
/home/dash/dash2-cli stop
sleep 30
pkill -9 dashd2 dash_shutoff
sleep 10
/home/dash/d2.sh
exit
fi
if [ $[$b3+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash3/debug.log >> crash3.log
/home/dash/dash3-cli stop
sleep 30
pkill -9 dashd3 dash_shutoff
sleep 10
/home/dash/d3.sh
exit
fi
if [ $[$b4+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash4/debug.log >> crash4.log
/home/dash/dash4-cli stop
sleep 30
pkill -9 dashd4 dash_shutoff
sleep 10
/home/dash/d4.sh
exit
fi
if [ $[$b5+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash5/debug.log >> crash5.log
/home/dash/dash5-cli stop
sleep 30
pkill -9 dashd5 dash_shutoff
sleep 10
/home/dash/d5.sh
exit
fi
if [ $[$b6+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash6/debug.log >> crash6.log
/home/dash/dash6-cli stop
sleep 30
pkill -9 dashd6 dash_shutoff
sleep 10
/home/dash/d6.sh
exit
fi
if [ $[$b7+1] -lt $ba ]; then
tail -n 30 /home/dash/.dash7/debug.log >> crash7.log
/home/dash/dash7-cli stop
sleep 30
pkill -9 dashd7 dash_shutoff
sleep 10
/home/dash/d7.sh
exit
fi
sleep 1000
done

[stealth923]

I'm just going to throw one more idea out there and then I'm off.

How about some trusted member of the testing team lodge a proposal to fund a masternode or two to reward the testers! Sure the rewards won't be anything like last month's proposal but, it may provide some small incentive and also may be worth quite a lot more in the future.

One way of providing more incentive perhaps would be to have a lottery among testers, so that instead of lots of tiny payouts, all testers are in with a chance of one large payout, or a few payouts.

Then there would always be at least some funds to incentivise testing and the masternode network would be supported at the same time.

I like the idea to support testing.  Why are we tying up 1000 coins forever?  Why not just set a 20 coins/month budget?  Or some reasonable number that makes sense.  Just payout the participants with a lottery like you suggest or split it up.

We really need something much more extensive for testing. I want to make a cluster on AWS, that all core team members have access to. We can run a few hundred masternodes using this cluster, do scripted updates and test various network issues, etc. Then at the end of testing, we could even scale the cluster to 3000 masternodes to make sure it works at the levels we're using for mainnet. We could even setup the cluster to have a centralized logging system so the developers could search the logs for error messages and see what was happening without logging into a million servers.

Infrastructure is the most expensive part of testing and it would be nice to have that covered by the budget. Besides that we could have bug bounties, like 10-50 DASH per bug found for the testers. There's no hurry though, we'd rather utilize the budget to make the public aware of the project and build a nice onboarding system.

The budget system turned out to be a pretty powerful tool for us. There's so many ideas that are being tossed around that would have never worked otherwise.

Totally agree with you, use the budget money for marketing and awareness to get more users & merchants, increase volume on exchanges and hopefully price as well.

This will then have a knock on effect where the monthly budget will be worth even more and go further. You can then use it to get as many test clusters as you want

[tungfa]

Hello Fintech Finance
http://www.fintech.finance/news/dash-a-superior-digital-money-alternative-to-bitcoin/
 

[TanteStefana2]

Can we run a testing node on the same server as a standard masternode?  It should use a different port right?

Maybe we can do a piggyback deal that automatically runs the testing node with a standard masternode.

You can, but it's a really bad idea.  The server can crash, things could get corrupted, it's just not safe, and you'll lose your income if the server goes down.  This can happen easily during a memory leak, where your resources are stretched to the limit, crashing the system, or causing your service provider to turn off your server.

Happens all the time in testing.

[TaoOfSaatoshi]

Hello Fintech Finance
http://www.fintech.finance/news/dash-a-superior-digital-money-alternative-to-bitcoin/
 

Very nice! Word is getting out...

[Solarminer]

Can we run a testing node on the same server as a standard masternode?  It should use a different port right?

Maybe we can do a piggyback deal that automatically runs the testing node with a standard masternode.

You can, but it's a really bad idea.  The server can crash, things could get corrupted, it's just not safe, and you'll lose your income if the server goes down.  This can happen easily during a memory leak, where your resources are stretched to the limit, crashing the system, or causing your service provider to turn off your server.

Happens all the time in testing.

Thanks TS.  I can run some test nodes in separate virtual machines to help out.  Just need some help on getting started and getting test coins.

[oblox]

Can we run a testing node on the same server as a standard masternode?  It should use a different port right?

Maybe we can do a piggyback deal that automatically runs the testing node with a standard masternode.

You can, but it's a really bad idea.  The server can crash, things could get corrupted, it's just not safe, and you'll lose your income if the server goes down.  This can happen easily during a memory leak, where your resources are stretched to the limit, crashing the system, or causing your service provider to turn off your server.

Happens all the time in testing.

Over-the-top, worst case scenario assuming you don't already run autoreboot/autostart scripts (would get you back up and running before you are out of queue so no loss of income) and quite frankly, have a shitty service provider. With separate profiles, I have yet to see the base case for file corruption and the not safe comment is just bullshit.

[TaoOfSaatoshi]

I just watched the promo vid again.

When the voice-over guy says "Dash is Digital Cash.", and the D flips to a C, that is absolutely amazing.

Such a great job done by all on that video!

[tungfa]

I just watched the promo vid again.

When the voice-over guy says "Dash is Digital Cash.", and the D flips to a C, that is absolutely amazing.

Such a great job done by all on that video!

So did 5,562 others
in the last 2 days
 

[TaoOfSaatoshi]

I just watched the promo vid again.

When the voice-over guy says "Dash is Digital Cash.", and the D flips to a C, that is absolutely amazing.

Such a great job done by all on that video!

So did 5,562 others
in the last 2 days
 

Wow. That's huge! And like it says in the video, it's only the beginning...

[tungfa]

I just watched the promo vid again.

When the voice-over guy says "Dash is Digital Cash.", and the D flips to a C, that is absolutely amazing.

Such a great job done by all on that video!

So did 5,562 others
in the last 2 days
 

Wow. That's huge! And like it says in the video, it's only the beginning...

So true
china video just went live (i share that later)
russian nearly done
we have a bunch of subtitles (different languages which have to go onto YT)
......

[TanteStefana2]

Can we run a testing node on the same server as a standard masternode?  It should use a different port right?

Maybe we can do a piggyback deal that automatically runs the testing node with a standard masternode.

You can, but it's a really bad idea.  The server can crash, things could get corrupted, it's just not safe, and you'll lose your income if the server goes down.  This can happen easily during a memory leak, where your resources are stretched to the limit, crashing the system, or causing your service provider to turn off your server.

Happens all the time in testing.

Over-the-top, worst case scenario assuming you don't already run autoreboot/autostart scripts (would get you back up and running before you are out of queue so no loss of income) and quite frankly, have a shitty service provider. With separate profiles, I have yet to see the base case for file corruption and the not safe comment is just bullshit.

Well, I'm not trying to BS, but my service provider shut my server down when I hogged resources once, and I got no notification and didn't realize it was down for days.  It was a cpu issue.  So if it doesn't start up again, my auto restart setup won't do anything for me.  This may not happen with other service providers, but I just want you all to know there is a risk.  Hopefully you can mitigate it, that'd be great!

[Laxdude7691]

Is almost 12 hours unusual for a confirmation time on bitcoin deposits at Cryptsy? This is crazy!

[splawik21]

Is almost 12 hours unusual for a confirmation time on bitcoin deposits at Cryptsy? This is crazy!

I use poloniex and dashcurex.com - they need 1-3 confirmations and your BTC are there!
Haven`t had any problems with them.
In the past I couldn`t stand it too as had to wait ~5h to get the coins (btc) there.

[stealth923]

Seems as though price is starting to move on up - if you were waiting to get some coins, id get them now!

[LiteMine]

Can we run a testing node on the same server as a standard masternode?  It should use a different port right?

Maybe we can do a piggyback deal that automatically runs the testing node with a standard masternode.

You can, but it's a really bad idea.  The server can crash, things could get corrupted, it's just not safe, and you'll lose your income if the server goes down.  This can happen easily during a memory leak, where your resources are stretched to the limit, crashing the system, or causing your service provider to turn off your server.

Happens all the time in testing.

Over-the-top, worst case scenario assuming you don't already run autoreboot/autostart scripts (would get you back up and running before you are out of queue so no loss of income) and quite frankly, have a shitty service provider. With separate profiles, I have yet to see the base case for file corruption and the not safe comment is just bullshit.

The larger point made by eduffield is that we need a testing environment that more closely resembles mainnet. V12 didn't have more than a few hundred nodes and a few more people piggybacking aren't going to get us to 3000 testnet nodes.

[mastertrader777]

I bought more Dash!!!!

[LiteMine]

Test-DASH is free but servers cost money - even on t-net


TESTER's need to be paid also - no different from the DEVs

Absolutely, and we'll probably see a proposal to address both points. No disrespect intended towards testers, it's a tough job. I tried to run several testnet MN's, but quickly got overwhelmed with all the updates.

[Solarminer]

Can we run a testing node on the same server as a standard masternode?  It should use a different port right?

Maybe we can do a piggyback deal that automatically runs the testing node with a standard masternode.

You can, but it's a really bad idea.  The server can crash, things could get corrupted, it's just not safe, and you'll lose your income if the server goes down.  This can happen easily during a memory leak, where your resources are stretched to the limit, crashing the system, or causing your service provider to turn off your server.

Happens all the time in testing.

Over-the-top, worst case scenario assuming you don't already run autoreboot/autostart scripts (would get you back up and running before you are out of queue so no loss of income) and quite frankly, have a shitty service provider. With separate profiles, I have yet to see the base case for file corruption and the not safe comment is just bullshit.

The larger point made by eduffield is that we need a testing environment that more closely resembles mainnet. V12 didn't have more than a few hundred nodes and a few more people piggybacking aren't going to get us to 3000 testnet nodes.

Test-DASH is free but servers cost money - even on t-net

TESTER's need to be paid also - no different from the DEVs

My point I was trying to make originally, is that maybe a testing daemon could be built into the normal masternode dashd.  Effectively, using the same servers as the main net without any extra server expenses while simulating the same network environment.  I realize this isn't as secure or could cause problems, but it would sure be innovative if it could be pulled off.

[toknormal]

Stockmarkets appear to be learning something from cryptomarkets...


"Dumping into the close"