v0.11.0 - Darkcoin Core Release

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Just entertaining the crowd while we in this "forking" limbo. Who can resist almost 15k views ?



Talking of views... How's the network doing?


Ok ok... I'll stop now. Evan is around, so soon enough we're back in business...

.
LOL.........................................................
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
All my Masternodes are currently on 0.11.0.11 and are showing up with "Safe mode Warning The network does not appear to fully agree! Some miners appear to be experiencing issues". Similarly to how others have described. I assume this is to make operator aware that a fork has occurred?

I've tried " getblock" on the Debug console of one of my Masternodes and I'm currently getting block not found (code-5). I've already tried reindexing. Are any other Masternode owners experiencing the same issues? I can't seem to get them onto the correct block.
http://explorer.darkcoin.io/chain/Darkcoin is in sync now, you can check block height against it.
Try to delete peers.dat first before reindexing.
 

jpr

Active Member
May 11, 2014
493
393
133
All my Masternodes are currently on 0.11.0.11 and are showing up with "Safe mode Warning The network does not appear to fully agree! Some miners appear to be experiencing issues". Similarly to how others have described. I assume this is to make operator aware that a fork has occurred?

I've tried " getblock" on the Debug console of one of my Masternodes and I'm currently getting block not found (code-5). I've already tried reindexing. Are any other Masternode owners experiencing the same issues? I can't seem to get them onto the correct block.
Hi
I had this warning this morning and what I did was:
Code:
./darkcoind stop
cd .darkcoin
rm peers.dat
cd ..
./darkcoind start -reindex
After this the problem did not dissapear but now I checked and it's gone. Seems I am on the right fork now.
 
  • Like
Reactions: ANAEDV

italx

Well-known Member
Foundation Member
Jul 31, 2014
65
52
158
California
Hi
I had this warning this morning and what I did was:
Code:
./darkcoind stop
cd .darkcoin
rm peers.dat
cd ..
./darkcoind start -reindex
After this the problem did not dissapear but now I checked and it's gone. Seems I am on the right fork now.

I just did the same for all of mine and they seem to be alive again.
 

Sub-Ether

Well-known Member
Mar 31, 2014
1,516
1,254
183
Schrodinger's Fork,
i.e. it doesn't know whether its eating chicken or is on the desert already, which is pretty silly because the desert is custard.
 

aaxx1503

Active Member
Feb 28, 2014
113
106
93


Jesus christ, if this was pool distribution I'd be quite happy, Masternode versions, Not so much!
 
  • Like
Reactions: buster

aaxx1503

Active Member
Feb 28, 2014
113
106
93
That 10.17.25 is about 25% for a few days now and is not decreasing :(
Someone is being very lazy. Would love if there was a way to diminish payments to older nodes. There has to be an incentive to update.
 
  • Like
Reactions: yidakee

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Agreed, but the limiting factor is not the MN's, but the miners, to achieve consensus. From there, banning old clients is peanuts.
Time to mobilize the Pool Police again? Waiting on Evan for further instructions.

Splawik, get your guns ready just in case ;)
 
  • Like
Reactions: splawik21

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
Well, this fork has become a bit of a clusterfuck for my MN set up. Constantly getting kicked off, updating, reindexing etc. Going to take the opportunity to consolidate my set up and utilise this start-many function I think... Sounds like a good idea as I type this but no doubt I'm about to enter a world of pain...! :tongue:
 

thelonecrouton

Well-known Member
Foundation Member
Apr 15, 2014
1,135
813
283
Well, this fork has become a bit of a clusterfuck for my MN set up. Constantly getting kicked off, updating, reindexing etc. Going to take the opportunity to consolidate my set up and utilise this start-many function I think... Sounds like a good idea as I type this but no doubt I'm about to enter a world of pain...! :tongue:
It's a piece of cake.

Import all your MN collateral address privkeys into one wallet, set up your masternode.conf exactly as described in the /doc/masternode.conf-md file, unlock your wallet and 'masternode start-many' - you'll be glad you've done it when you've done it. :)

My MNs all seem to be still OK, about 12 hrs after this mornings group -reindexing session.
 

jpr

Active Member
May 11, 2014
493
393
133
Absolutely sickening seeing how many Onyx masternodes are still out there. You shitbags don't deserve a single fucking payment you lazy bums.
Lazyness is one thing. They just don't want to miss a payment. So development is slowing down, price will drop, all this because of a few missed $$.
 

rrodent

New Member
Nov 9, 2014
13
5
3
well all righty then... --reindex put me on a different fork which sucks... thought i had hit the lottery with found blocks. So evidently i was on the wrong fork even though i was running 11.0.11. My major bitch here is that I had my 100 drk mixing and even though I was obviously on the wrong fork I was still charged .5 in fees... wtf.
 

splawik21

Moderator
Dash Core Team
Foundation Member
Dash Support Group
Apr 8, 2014
1,938
1,295
1,283
Agreed, but the limiting factor is not the MN's, but the miners, to achieve consensus. From there, banning old clients is peanuts.
Time to mobilize the Pool Police again? Waiting on Evan for further instructions.

Splawik, get your guns ready just in case ;)
No problem for me, if I have the precise info like drk.mn on right version which will point which pools are on different ver I can do it with pleasure. Can start since tomorrow not earlier.
 

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
It's a piece of cake.

Import all your MN collateral address privkeys into one wallet, set up your masternode.conf exactly as described in the /doc/masternode.conf-md file, unlock your wallet and 'masternode start-many' - you'll be glad you've done it when you've done it. :)

My MNs all seem to be still OK, about 12 hrs after this mornings group -reindexing session.
How should my darkcoin.conf file look? I've done my masternode.conf file as described but not sure what I need to put into the darkcoin.conf file. Can't seem to find an example documented anywhere either. It's more the syntax i need guidance on if anything... Any help appreciated! :)
 

splawik21

Moderator
Dash Core Team
Foundation Member
Dash Support Group
Apr 8, 2014
1,938
1,295
1,283
Walter you don`t need your darkcoin.conf anymore ;) your masternode.conf is enough, make sure every line with alias ip masternode privkey and txid index is in one line and after all there are no spaces.
 
  • Like
Reactions: Walter

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
How should my darkcoin.conf file look? I've done my masternode.conf file as described but not sure what I need to put into the darkcoin.conf file. Can't seem to find an example documented anywhere either. It's more the syntax i need guidance on if anything... Any help appreciated! :)
If you have custom settings in your darkcoin.conf like disabling safemode, wallet mining, etc, you can leave them, but the masternode information can get removed if you are using the masternode.conf in junction with start-many/start-alias.
 
  • Like
Reactions: Walter

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
Walter you don`t need your darkcoin.conf anymore ;) your masternode.conf is enough, make sure every line with alias ip masternode privkey and txid index is in one line and after all there are no spaces.
Ah... That makes more sense! Couldn't figure out why i'd need it but this guide is a bit misleading in that respect...

https://github.com/perrywoodin/darkcoin-startmany-guide

"
Create a darkcoin.conf file
Remember... this is local. Make sure your QT is not running.

You should already have a darkcoin.conf file from your exisiting node. I simply copied it into my new wallet."

This bit in particular, makes it sound like a requirement :confused:
 

David

Well-known Member
Jun 21, 2014
618
628
163
I'm so confused right now. Is it any wonder MN operators aren't updating? We have network fragmentation, unstable releases that are causing MNs to crash, and now we have a fork. I'm sitting on 11.0.10 for now, and y'all can gripe at me all you want, but until I figure out what the hell is going on and the network stabilizes, I'm not doing anything.
 

camosoul

Grizzled Member
Sep 19, 2014
2,261
1,130
1,183
Peoe still running v0.10.xx.xx at this point are blackhats deliberately fucking the network. There is absolutely no fucking excuse for this.

"I updated but I don't even computer, bro. So I switched back to make sure DRK would never work." Helping retards run masternodes, I told you it was a bad idea months ago.

Every damn thing I ever got shouted-down for bringing up has come back to bite the short-sighted, entitled, LIV mentality shitstains... Now the project is suffering badly because theze lazy brats refuse to computer.

I hope upon all hope that 0.11.0.12 forces versioning on payments. Tbis fork would not even exist if not for the turds going hut of their way to cause it...

Absolutely no damn excuse for this. Maybe Darkcoin Jesus can forgive you, but I'll kick you in the crotch until you bleed out your ears.
 
  • Like
Reactions: jpr

camosoul

Grizzled Member
Sep 19, 2014
2,261
1,130
1,183
So, this is the question for the entire dev team. What do you need to make testnet and testing more robust? Change of approach, money, more hands on deck?
A realization that testnet is a sterile laboratory environment, and that mainnet is really nothing more than a more realistic test environment might help.

Version zero dot oneone dot zero dot oneone...

Perspective and people with a clue keeping their shit together for masternode operators...

There is only one problem; failure to update. The 0.10.xx.xx are the cause.
 

camosoul

Grizzled Member
Sep 19, 2014
2,261
1,130
1,183
I'm so confused right now. Is it any wonder MN operators aren't updating? We have network fragmentation, unstable releases that are causing MNs to crash, and now we have a fork. I'm sitting on 11.0.10 for now, and y'all can gripe at me all you want, but until I figure out what the hell is going on and the network stabilizes, I'm not doing anything.
The mn operators who aren't updating are the cause. There is nothing confusing about it. Update your shit.
 

Walter

Active Member
Masternode Owner/Operator
Jul 17, 2014
231
201
103
Well two hours later and my transition to start-many was relatively smooth... I've shifted my increased number of MNs onto two VMs now and got the start-many function working. It's going to be a big time saver going forwards. Should be able to update my MNs in a couple of minutes now :):):)

Thanks for the help guys :D
 
  • Like
Reactions: splawik21

Propulsion

The buck stops here.
Feb 26, 2014
1,008
468
183
Dash Address
XerHCGryyfZttUc6mnuRY3FNJzU1Jm9u5L
The entire cause of the fork appears to be network fragmentation, so masternode payments will remain non-enforced until we have a good portion of the network on a recent version.
So this was due to half the mining pools on an old version and half on the new?
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
Absolutely sickening seeing how many Onyx masternodes are still out there. You shitbags don't deserve a single fucking payment you lazy bums.
They like the name you gave the release so they want to hang on to it... It's all your fault! :tongue:
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
The entire cause of the fork appears to be network fragmentation, so masternode payments will remain non-enforced until we have a good portion of the network on a recent version.
Due to masternodes or pools because I thought the pools were already on Core and v10's should have forked off (which appears to be the case).

Looks like over 80% of the pools are paying Core masternodes.