V12 Release

elbereth

Active Member
Dash Support Group
Mar 25, 2014
461
484
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
Sorry for the bad stats but my dashd nodes are dying after less than 12h. Not ram related as I have 7GB free atm. No idea what the problem is and no time to investigate for the moment.
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Sorry for the bad stats but my dashd nodes are dying after less than 12h. Not ram related as I have 7GB free atm. No idea what the problem is and no time to investigate for the moment.
I can offer an external dashd if that is of any help...
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Code:
while [ true ] ; do
  if [ -z $(fuser -c ~user1/.dash 2>&-) ] ; then
    dashd 1>&-
  fi
  sleep 300
done
Thank you so very much! I'm sorry I disappeared, had to go. I did have to add the full path to dashd for some reason, but otherwise it worked. This is what I ended up with. If there is a mistake / bad design that you see could cause issue, please let me know :D

Code:
#!/bin/bash
while [ true ] ; do
  if [ -z $(fuser -c ~usr1/.dash/dash.pid 2>&-) ]; then
    /usr/local/bin/dashd 1>&-
  fi
  sleep 300
done
I've learned a lot trying to do this, again, thanks!
 
  • Like
Reactions: Solarminer

ArpFlush

Member
Jan 24, 2015
49
23
48
Hi guys,

On dashninja I have a yellow protocol, I see that some are on v52. Will it be ok if I just update my VPS with dashd and dash-cli (with v52)?
v0.12.0.51protocol: 70103
 
  • Like
Reactions: aleix

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
Hi guys,

On dashninja I have a yellow protocol, I see that some are on v52. Will it be ok if I just update my VPS with dashd and dash-cli (with v52)?
v0.12.0.51protocol: 70103
Dashninja is wrong on this, current protocol version is still 70103. .52 is not released yet, use on your own risk.
 

Solarminer

Well-known Member
Apr 4, 2015
762
922
163
Thank you so very much! I'm sorry I disappeared, had to go. I did have to add the full path to dashd for some reason, but otherwise it worked. This is what I ended up with. If there is a mistake / bad design that you see could cause issue, please let me know :D

Code:
#!/bin/bash
while [ true ] ; do
  if [ -z $(fuser -c ~usr1/.dash/dash.pid 2>&-) ]; then
    /usr/local/bin/dashd 1>&-
  fi
  sleep 300
done
I've learned a lot trying to do this, again, thanks!
We were also talking about a similar program on the bitcointalk thread here:
https://bitcointalk.org/index.php?topic=421615.105600

It you want to use the process id, instead of the dash.pid file. Replace the if statement with this.
if [ -z `pidof dashd` ]; then

I like your idea of the dash.pid. With the process id it would change if it needed to restart, so your way should allow multiple restarts.

I think with your way you would need to leave your terminal window open for this to work. So I suggested using the screen command to run in the background. UdjinM6 suggested using a crontab. Details from bitcointalk:

Copy code below and paste into mn_watch.sh file. Type nano mn_watch.sh, paste with right click, and control x, y, enter to save. Change dashuser to your user name.
Code:
#!/bin/bash
#run with:  screen -dm /mn_watch.sh
#stop with:  screen -ls to find number and screen -X -S 11111 kill
while true; do
if [ -z `pidof dashd` ]; then
echo Dashd is not running trying to start
/home/dashuser/dashd
sleep 600
else
echo Dashd is Running
sleep 600
fi
done
type:
chmod +x mn_watch.sh

You can test it by running:
./mn_watch.sh
It will stop working as soon as you logout though, so we need to install screen to have it run in the background. Run this to install screen. (Assuming you are running Ubuntu.)
apt-get install screen

to start with screen type:
screen -dm /mn_watch.sh

This will run forever, so if you want it to stop type
screen -ls and get the number replace that with the 11111 below.
screen -X -S 11111 kill
 
Last edited by a moderator:
  • Like
Reactions: TanteStefana

elbereth

Active Member
Dash Support Group
Mar 25, 2014
461
484
133
Costa Rica
dashninja.pl
Dash Address
XkfkHqMnhvQovo7kXQjvnNiFnQhRNZYCsz
I can offer an external dashd if that is of any help...
Unfortunately, even if I started Dash Ninja with the goal of having support for multiple hubs, current code will probably break if used that way.
When I get some more time I will try to improve it so I can add off-site monitoring nodes.
 
  • Like
Reactions: flare

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
We were also talking about a similar program on the bitcointalk thread here:
https://bitcointalk.org/index.php?topic=421615.105600

It you want to use the process id, instead of the dash.pid file. Replace the if statement with this.
if [ -z `pidof dashd` ]; then

I like your idea of the dash.pid. With the process id it would change if it needed to restart, so your way should allow multiple restarts.

I think with your way you would need to leave your terminal window open for this to work. So I suggested using the screen command to run in the background. UdjinM6 suggested using a crontab. Details from bitcointalk:

Copy code below and paste into mn_watch.sh file. Type nano mn_watch.sh, paste with right click, and control x, y, enter to save. Change dashuser to your user name.
Code:
#!/bin/bash
#run with:  screen -dm /mn_watch.sh
#stop with:  screen -ls to find number and screen -X -S 11111 kill
while true; do
if [ -z `pidof dashd` ]; then
echo Dashd is not running trying to start
/home/dashuser/dashd
sleep 600
else
echo Dashd is Running
sleep 600
fi
done
type:
chmod +x mn_watch.sh

You can test it by running:
./mn_watch.sh
It will stop working as soon as you logout though, so we need to install screen to have it run in the background. Run this to install screen. (Assuming you are running Ubuntu.)
apt-get install screen

to start with screen type:
screen -dm /mn_watch.sh

This will run forever, so if you want it to stop type
screen -ls and get the number replace that with the 11111 below.
screen -X -S 11111 kill
Exactly! I started with the conversation on bitcointalk, and discovered that my daemons wouldn't start independently, if one should crash or stop, but the other continued. (I have one server, two users, 2 ip addresses, running 2 masternodes) So GR+ showed me how to test for the user's process id for dash (which I think is only possible because our developers made it pop up as a file in the .dash folder? It is checked with a cron job and if not running, it starts the daemon back up.

There is another way to check to see if the daemon stopped cleanly vs dirty, so that if you stopped the daemon (rather than it crashing) it would stay stopped until you started it again. This would be useful for updating, but I wasn't able to get it to work. I don't think it's worth the trouble either as I only usually need a second to restart the daemon after updating the files. I don't even stop it before updating. As long as we still have dashd and dash-cli, the older running version of dashd can shut down fine (it doesn't over write the new version on shutdown) and restarting updates the version. Plus, I check every 10 minutes, which is done by the clock, so if I start after a check (ie: X:00, X:10, X:20...etc...) I have plenty of time, even if I had to stop the daemon to update.

Anyway, I wrote a tutorial on it here: https://dashtalk.org/threads/keep-your-mn-up-and-running-after-crash-ubuntu-w-explainations.6063/

If it sucks too much, anyone is welcome to rewrite it and even better, give other ways and other choices on how to do it :) Thanks for everyone's help!
 

Geert

Member
Aug 26, 2015
259
82
88
ah true.. i didn't think of that... also, i think at the beginning there was talk that it should be capped at 2000.. that was before evan had his "eureka" moment... and InstantX was born.. :)

EDIT: and more masternodes were needed because of InstantX, hence, more reward for mns...
If Dash appreciates till it's worth as much as BTC, and people clue into the fact that they can run several masternodes and live comfortably off the proceeds, masternodes may eat up most of the available Dash. Also, if there are too many masternodes, will that hamper the network's ability to reliably mix coins? I can't help feeling that at some point, there may be a real hard limit placed upon the total number of masternodes put in the code.
 

fible1

Well-known Member
Dash Core Team
Masternode Owner/Operator
May 11, 2014
710
722
163
If Dash appreciates till it's worth as much as BTC, and people clue into the fact that they can run several masternodes and live comfortably off the proceeds, masternodes may eat up most of the available Dash. Also, if there are too many masternodes, will that hamper the network's ability to reliably mix coins? I can't help feeling that at some point, there may be a real hard limit placed upon the total number of masternodes put in the code.
It would be impossible for masternodes to overtake most of the "coinage" in the network as masternode revenue goes up and down proportional to how many nodes are on the network. In other words, the more nodes come online, the less each individual node will get paid, until it becomes unprofitable to run a node, so the market itself will set a balance.

Hope that helps :).

Pablo.
 

crowning

Well-known Member
May 29, 2014
1,414
1,997
183
Alpha Centauri Bc
If Dash appreciates till it's worth as much as BTC, and people clue into the fact that they can run several masternodes and live comfortably off the proceeds, masternodes may eat up most of the available Dash.
Actually that's a good thing, because hold coins stabilize a crypto-currency. That's why Dash even in this early stage is very stable.
Bad for brokers, good for everyone else.

Also, if there are too many masternodes, will that hamper the network's ability to reliably mix coins?
Nope...for almost everything more Masternodes are better.
 
  • Like
Reactions: weirdgod and akhavr

Lebubar

Active Member
Mar 15, 2014
249
213
103
It would be impossible for masternodes to overtake most of the "coinage" in the network as masternode revenue goes up and down proportional to how many nodes are on the network. In other words, the more nodes come online, the less each individual node will get paid, until it becomes unprofitable to run a node, so the market itself will set a balance.

Hope that helps :).

Pablo.
Well for me it will be hard for a MN to become unprofitable. Maybe if the reward is less than 5$ per month (or even less), which is the cost for the rent of a vps per month.

The hard limit of #number of MN is total coin / 1000 (approx... Minus lost/destroy coins, minus people that hold less than 1000 and not in sharing MN, etc etc) this is the maximum maximorum ;)
 
Last edited by a moderator:

fible1

Well-known Member
Dash Core Team
Masternode Owner/Operator
May 11, 2014
710
722
163
Well for me it will be hard for a MN to become unprofitable. Maybe if the reward is less than 5$ per month (or even less), which is the cost for the rent of a vps per month.

The hard limit of #number of MN is total coin / 1000 (approx... Minus lost/destroy coins, minus people that hold less than 1000 and not in sharing MN, etc etc) this is the maximum maximorum ;)
Hey :),
I meant unprofitable in terms of opportunity cost :). Otherwise yes, you are right, it would be hard for masternodes to not be profitable in an accounting sense; although we are also not factoring on the depreciation that has been going on, but I digress.

:D

Pablo.
 

patrolman

Member
Mar 9, 2014
102
67
78
www.dash.pics
If Dash appreciates till it's worth as much as BTC, and people clue into the fact that they can run several masternodes and live comfortably off the proceeds, masternodes may eat up most of the available Dash. Also, if there are too many masternodes, will that hamper the network's ability to reliably mix coins? I can't help feeling that at some point, there may be a real hard limit placed upon the total number of masternodes put in the code.
I think mixing needs to be faster - there needs to be a greater incentive to provide liquidity for mixing. It was suggested in the past that a budget proposal could be put forward to provide mixing liquidity, but as far as I know at the moment it would be a trusted solution, so the suggestion in the past was for trusted community members to offer the service, which I think is a reasonable idea if there has to be trust.

Let's say a masternode currently earns 0.63 DASH per day (according to http://178.254.18.153/~pub/Darkcoin/masternode_payments_stats.html), on average there are about 30.4 days per month, which would be 19.152 DASH earned per month in a masternode. I don't know what would be the best amount for a liquidity provider, but I have had a little trouble mixing 100s at times in the past, so let's say 2 x 500 DASH liquidity nodes. Obviously you would need to offer a greater incentive than that which is offered to run the Masternodes with funds in a cold wallet, so let's say instead of the estimated 19.152 for 1000 DASH for one month, 40 DASH is offered as compensation - 20 DASH for each 500 DASH liquidity provider. It's not an ideal solution, because trust is involved (one entity running both liquidity nodes would not be a good idea in my opinion), but it would be one way of increasing the speed of the mixing process.

Perhaps 20 DASH wouldn't be enough though, for the risk involved. The great thing is, even if it starts out at 50 DASH per node and people agree to it, in the future someone could beat the price, so the funds could be reallocated to the new party with the better offer.
 
Last edited by a moderator:
  • Like
Reactions: weirdgod

weirdgod

Well-known Member
Foundation Member
Jun 4, 2014
91
51
168
Slovenia, EU
Just noticed that all the files in dash-win-32bit zip file, are dated as 1/10/2014 ... which is a bit confusing?

Also a link to Release notes on downloads page, opens a page that says that version 12.0 is not yet released... ?
 
  • Like
Reactions: tungfa

fuzzyduck

Active Member
Feb 19, 2015
137
113
93
To follow up on my own problem. My log contains mainly:


2015-09-01 19:08:21 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:21 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:21 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:21 UpdateTip: new best=00000000003d80fea2d93bde78cba94bfb6a30afee58cf8991e0216bef607822 height=25342 log2_work=52.342203 tx=97753 date=2014-02-28 12:20:23 progress=0.026413 cache=31464
2015-09-01 19:08:21 ProcessNewBlock : ACCEPTED
2015-09-01 19:08:21 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:21 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:21 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:21 UpdateTip: new best=00000000007b32d9a6d51e55474f450f185ceec5f28554af893e7b2d08cc81f0 height=25343 log2_work=52.342364 tx=97754 date=2014-02-28 12:20:27 progress=0.026413 cache=31465
2015-09-01 19:08:21 ProcessNewBlock : ACCEPTED
2015-09-01 19:08:26 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:26 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:26 ProcessNewBlock : ACCEPTED
2015-09-01 19:08:26 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:26 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:26 ProcessNewBlock : ACCEPTED
2015-09-01 19:08:26 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:26 CheckBlock() : skipping transaction locking checks
2015-09-01 19:08:26 ProcessNewBlock : ACCEPTED

-Besides although i removed maxconnections, its stuck at exactly 8 connections always.
-During startup of dashd it reads about 7000 blocks, then it renames it to bootstrap.dat.OLD and starts downloading them.
-Block count creeps up sloooowwwwly.
-I got this also:

Binding RPC on address :: port 9998 (IPv4+IPv6 bind any: 1)
2015-09-01 18:02:15 ERROR: Binding RPC on address :: port 9998 failed: open: Address family not supported by protocol
2015-09-01 18:02:15 Binding RPC on address 0.0.0.0 port 9998 (IPv4+IPv6 bind any: 1)

and

Error: Couldn't open socket for incoming connections (socket returned error Address family not supported by protocol (97))
2015-09-01 18:02:15 Bound to 0.0.0.0:9999


EDIT: am i hijacking the thread? If so sorry... :p
EDIT2: Hold on. its adding blocks like the wind now. Boostrap.dat still live and not renamed.. Im so confused.
EDIT3: Ok stopped...

tail -f debug.log
2015-09-01 19:22:38 keypool reserve 2
2015-09-01 19:22:38 keypool return 2
2015-09-01 19:22:38 keypool reserve 2
2015-09-01 19:22:38 keypool return 2
2015-09-01 19:22:40 keypool reserve 2
2015-09-01 19:22:40 keypool return 2
2015-09-01 19:23:01 keypool reserve 2
2015-09-01 19:23:01 keypool return 2
2015-09-01 19:25:39 keypool reserve 2
2015-09-01 19:25:39 keypool return 2
2015-09-01 19:27:35 Loaded 24810 blocks from external file in 899974ms

renamed to .Old again :(
Back to 'skipping transaction locking checks'

EDIT4: concluded that 'skipping transaction locking checks' is in fact importing blocks from file. When using 'tail -f debug.log' all this stuff flies by on screen.
Alright.... To finish my problem: Where i couldnt get .51 to work, version .52 worked out of the box after compiling & starting it from wallet.

One happy camper once more.
 
  • Like
Reactions: tungfa

tungfa

Grizzled Member
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,902
6,739
1,283
We've just revoked the release of .52
Please stick to .51 until the new version is fixed.

Sorry
"hope no animals were harmed"
;)
 
  • Like
Reactions: akhavr

weirdgod

Well-known Member
Foundation Member
Jun 4, 2014
91
51
168
Slovenia, EU
hmm. I am really curious how the MN winners are selected in current situation.
From what I understood, winners are selected only from MNs running on latest version.
So, assuming the (unlikely) situation that we would not get new .52 replacement for a few days... what would happen?
Would only the .51 MNs be selected for winners, or would the .52, as its the newest version (although it was revoked)...
Is some central node "prescribing" the network which dashd version is the right for MN winning/payment selection?

if I already updated - should i wait on .52 ... or should i downgrade to .51?
what will raise my chances of winning MN payment?
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,286
2,404
1,183
Germany
hmm. I am really curious how the MN winners are selected in current situation.
From what I understood, winners are selected only from MNs running on latest version.
So, assuming the (unlikely) situation that we would not get new .52 replacement for a few days... what would happen?
Would only the .51 MNs be selected for winners, or would the .52, as its the newest version (although it was revoked)...
Is some central node "prescribing" the network which dashd version is the right for MN winning/payment selection?

if I already updated - should i wait on .52 ... or should i downgrade to .51?
what will raise my chances of winning MN payment?
"Latest version" refers to "latest protocol version" - as long as your node is on protocol version 70103 it will get paid - regardless of client version string
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
We've just revoked the release of .52
Please stick to .51
until the new version is fixed.

Sorry
"hope no animals were harmed"
;)
Oh you bad boy! My son's MN fell off the network! (but it's ok, he got paid only about 24 hours ago, so no biggie) You're lucky this time! No spanking, you get off with a warning ;P JK
 
  • Like
Reactions: tungfa

tungfa

Grizzled Member
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,902
6,739
1,283
Oh you bad boy! My son's MN fell off the network! (but it's ok, he got paid only about 24 hours ago, so no biggie) You're lucky this time! No spanking, you get off with a warning ;P JK
Me ?
i did not do ANYTHING (as usual)
i am just 'translating' things
look at that face :) could i really do anything wrong
lol
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,871
1,863
1,283
Oh no no no no, I distinctly remember last night before going to bed, reading a post encouraging us to update! That was YOU! LOL I still haven't loaded up the wallet to restart the node, I'm feeling so lazy! LOL.
 
  • Like
Reactions: tungfa

tungfa

Grizzled Member
Foundation Member
Masternode Owner/Operator
Apr 9, 2014
8,902
6,739
1,283
Oh no no no no, I distinctly remember last night before going to bed, reading a post encouraging us to update! That was YOU! LOL I still haven't loaded up the wallet to restart the node, I'm feeling so lazy! LOL.
Hahaaaaaa
you totally got me now !
Guilty as ...
no worries there
 
  • Like
Reactions: TanteStefana