• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.11.0 - Darkcoin Core Release

moli said:
eduffield, DRK withdrawals and deposits are still closed at https://bittrex.com/ and maybe some other exchanges. Someone from Bittrex is asking in IRC if they should reopen.

Could you please address. Thanks.

EDIT: From IRC #darkcoin channel:

[20:22:54] <bittrex-richie> yeah, think i'm on the right chain
[20:23:15] <bittrex-richie> just wanna make sure the rest of the network is there too so we dont have to deal with support tickets
Click to expand...

Yeah, the simply answer is to just make sure you're on the chain with the highest difficulty. That's going to be the one explorer.darkcoin.io, so as long as their last block hash matches the explorer, then they're good.
 
oblox said:
Can't enforcement or some code turn off old builds for masternodes, as in they aren't even recognized by the network. If you are a masternode operator, it is your obligation, much like pool operators, to be on the latest build. When payments stop trickling in, they will get the point.

If the majority of pools can be on the latest, there should be a check to turn off the network even seeing masternodes running old versions. There would be no confliction about masternode winners if the network doesn't see them as eligible.
Click to expand...
Thoughts eduffield ?
 
jimbit said:
As multiple masternode operator, I would be in favor of something like this.. I am sure I would notice within a day or so if my payments were off.
Click to expand...

I agree
i think it is time for some (little bit more) 'radical moves'
if they hold us back (since 5 days) as they do not update
and we will not solve that fo..k without them,
lets pull the plug.

No more payments bellow v11 and done !
lets see how fast they get their move on then !
 
Sounds reasonable to me, but I suspect there is sound reason that Evan has been reluctant to do this.

Evan, could you explain your thinking here? We know you are VERY busy right now, and appreciate all you are doing, but a word or two from you offering to give a fuller explanation when you get a chance, might calm a few frayed nerves.
 
set new p2pool node, download new wallet, sync.
and wrong network.
Code: 
{
    "version" : 110011,
    "protocolversion" : 70054,
    "walletversion" : 61000,
    "balance" : 0.00000000,
    "darksend_balance" : 0.00000000,
    "blocks" : 207640,
    "timeoffset" : 2,
    "connections" : 8,
    "proxy" : "",
    "difficulty" : 1.33652160,
    "testnet" : false,
    "keypoololdest" : 1421989075,
    "keypoolsize" : 1001,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
 
10.17.25 was 25% yesterday and it's 30% now!

Edit: MN count dropped to 1450, maybe that is why. Have we lost 500 nodes or people updating?
 
Last edited by a moderator:
jpr said:
10.17.25 was 25% yesterday and it's 30% now!

Edit: MN count dropped to 1450, maybe that is why. Have we lost 500 nodes or people updating?
Click to expand...
People updating more than likely. Masternode count showing 1880.
 
  • Like
Reactions: jpr
coingun said:
You can't just dangle stuff like this in front of us and not provide details!!!!!
Click to expand...
Sorry. This is crude and ugly but so am I and it works: http://pastebin.com/d67w9BZ1
example output:
Code: 
stu@stu-laptop:~/Desktop$ python mnchecker.py

Fri Jan 23 01:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 01:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 02:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 02:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 03:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 03:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 04:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 04:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 05:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 05:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 06:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 06:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 07:08:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Fri Jan 23 07:38:28 2015
MN 176.126.244.114 is OK!
MN 176.126.246.174 is OK!
MN 176.126.247.190 is OK!
MN 176.126.247.191 is OK!

Remember to unplug your headphones and turn your amp to 11 if you want to be woken up in the middle of the night. You can run it on your MNs too, but obviously replace the play sound bit with a send email or something.
 
Windows 64-Bit App crashed overnight:

Problem signature:
Problem Event Name: APPCRASH
Application Name: darkcoin-qt.exe
Application Version: 0.11.0.11
Application Timestamp: 52cf3800
Fault Module Name: darkcoin-qt.exe
Fault Module Version: 0.11.0.11
Fault Module Timestamp: 52cf3800
Exception Code: c0000005
Exception Offset: 0000000000168350
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0cf9
Additional Information 2: 0cf9cc51e69ff5dd98a6e1bd8c107346
Additional Information 3: e86c
Additional Information 4: e86c4be7a92bcae37d31e5ccf7530ea7
 
Walter said:
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:
Click to expand...
Hey Walter. Sorry for the confusion. My document started circulating before it was ready for a wider audience. I'll be updating it over the next couple of days.
 
oblox said:
Can't enforcement or some code turn off old builds for masternodes, as in they aren't even recognized by the network. If you are a masternode operator, it is your obligation, much like pool operators, to be on the latest build. When payments stop trickling in, they will get the point.

If the majority of pools can be on the latest, there should be a check to turn off the network even seeing masternodes running old versions. There would be no confliction about masternode winners if the network doesn't see them as eligible.
Click to expand...

That's completely supported by the reference node, but first we need a stable version with no crashes (should be v11.0.12) and enforcement turned on successfully.
 
v0.11.0.12

- Fixed 2 segfault causes, 1 due to a null reference in the Bitcoin code (https://github.com/bitcoin/bitcoin/issues/5698) upon a fork and the later due to the Bitcoin core code modifying the coins view without a lock on mempool.cs. The client should be much more stable now.
- Fixed issue with running "masternode start" on a remote masternode. This would corrupt the running status, resulting is the masternode failing to ping and falling off the list.
- fix mn payment comment - blocknumbers / new dates according to stats from last 50k blocks (UdjinM6)
- add missing DS/MN/IX options descriptions in help output (UdjinM6)
- allow masternode commands execution while client is in safe mode (UdjinM6)
- fix dseg messaging / banning issue (UdjinM6)

11.0.12 Core - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.12-win.zip
Mac OSX: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.11.0.12-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.12-linux.tar.gz
 
eduffield said:
v0.11.0.12

- Fixed 2 segfault causes, 1 due to a null reference in the Bitcoin code (https://github.com/bitcoin/bitcoin/issues/5698) upon a fork and the later due to the Bitcoin core code modifying the coins view without a lock on mempool.cs. The client should be much more stable now.
- Fixed issue with running "masternode start" on a remote masternode. This would corrupt the running status, resulting is the masternode failing to ping and falling off the list.
- fix mn payment comment - blocknumbers / new dates according to stats from last 50k blocks (UdjinM6)
- add missing DS/MN/IX options descriptions in help output (UdjinM6)
- allow masternode commands execution while client is in safe mode (UdjinM6)
- fix dseg messaging / banning issue (UdjinM6)

11.0.12 Core - All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.12-win.zip
Mac OSX: https://raw.githubusercontent.com/d...in-binaries/master/darkcoin-0.11.0.12-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.12-linux.tar.gz
Click to expand...
Tweeted.

Way to go, Evan, congratulations, you Proof of Honor winner, you!
 
getblocktemplate




{
"version" : 2,
"previousblockhash" : "00000000000648d472d106f198fedc3f578a1557194687febc098d4bed085b40",
"transactions" : [
],
"coinbaseaux" : {
"flags" : "062f503253482f"
},
"coinbasevalue" : 500000000,
"target" : "00000000000b6b6d000000000000000000000000000000000000000000000000",
"mintime" : 1422029460,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1422030966,
"bits" : "1b0b6b6d",
"height" : 208021,
"votes" : [
],
"payee" : "XyMXvs3zoVp9fQ91tPYY8CT4szPsjyVh63",
"payee_amount" : 175000000,
"masternode_payments" : true,
"enforce_masternode_payments" : true
}
 
You must log in or register to reply here.
Back
Top