v0.10.15 - Onyx Release

[admin]

This thread has derailed into many different topics. Now it is even becoming uncivil.
Thread is locked. I'll be moving multiple posts to separate threads with their respective links and reopen this one after it is completed.

Mining Pool dynamics discussion has been moved here.
https://darkcointalk.org/threads/onyx-release-mining-pools.2726/

This thread is for the new software release. Any problems you find or questions should be posted here. This is not the thread for proposing new distribution models or changes to the protocol.

Thread has been reopened. Once again, keep it civil.

 

[oaxaca]

In other words, you got 2 payments to an address which once WAS a Masternode.

Interesting....I'll open another JIRA issue for that...

Edit: Done, see http://jira.darkcoin.qa/browse/DRK-107

OK, back on track.

This address: XonoU99cPNkWkc3UuEvVN4btUrgWeCCcEc was never operating as a masternode. It "earned" 2 MN payments: 4668c8064f29035a943a0864a895ae2ed8f7ed72f256a2ae252809a9b8ad4a3a
and: 0b26601ccc7275ca994aa0dd703ec1c3f150dd0cfed9a744dd82b3e9a62706e9

Any ideas?

 

[eduffield]

v0.10.15.15 - Onyx Masternode Stability Update (RE: Crowning/Jimbit)

There have been some masternode stability problems (masternodes not staying active on the network) for some users, this was caused by the masternode operators changing the masternodeprivkey and then starting the masternode again. This lead to some of the networking have one pinging key and parts of the network having another. This update fixes that issue and will allow masternodes to change that key. Because of this issue clients were flagging peers as misbehaving, eventually leading to them being banned, causing network fragmentation, which lead to other issues on the network.

An alternative solution is to move the 1000DRK input to a brand new address that the network has not seen. Then start the masternode normally. Once the network updates to v15.15, we won't have these issues anymore.

Enforcement:

At block 158,000 masternode rewards will jump to 25%, if more than 80% of the network is updating and paying the correct rewards enforcement will be activated then. From the looks of it, we're very close to those numbers already. Once enforcement is active, payments will be completely 100% fair and equal between all masternodes.

10.15.15 Onyx Binaries: All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.15-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.15-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.15-linux.tar.gz

 

[jimbit]

all my MN updated... looking good so far!

thank you Evan

edit: after about an hour... this is the best I have seen my MN's since the latest launch..

 

[scratchy]

https://mupool.com/ fully updated

 

[UdjinM6]

updated too

somebody wake chaeplin up please

 

[oblox]

Masternodes updated.

 

[DrkMiner]

v0.10.15.15 - Onyx Masternode Stability Update (RE: Crowning/Jimbit)

There have been some masternode stability problems (masternodes not staying active on the network) for some users, this was caused by the masternode operators changing the masternodeprivkey and then starting the masternode again. This lead to some of the networking have one pinging key and parts of the network having another. This update fixes that issue and will allow masternodes to change that key. Because of this issue clients were flagging peers as misbehaving, eventually leading to them being banned, causing network fragmentation, which lead to other issues on the network.

An alternative solution is to move the 1000DRK input to a brand new address that the network has not seen. Then start the masternode normally. Once the network updates to v15.15, we won't have these issues anymore.

Enforcement:

At block 158,000 masternode rewards will jump to 25%, if more than 80% of the network is updating and paying the correct rewards enforcement will be activated then. From the looks of it, we're very close to those numbers already. Once enforcement is active, payments will be completely 100% fair and equal between all masternodes.

10.15.15 Onyx Binaries: All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.15-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.15-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.15-linux.tar.gz

Linux link doesn't work.

darkcoin.io has v 15.16

What is the diff with 15.15?

We should have a thread ONLY for version announcements.

 

[eduffield]

v0.10.15.16 - Onyx Masternode Stability Update

After some more inspection I found there were multiple Masternode announcement messages propagating around the network. This update filters out all but the newest one to ensure the list is correct and up-to-date. It's not manditory to update, but please do if you can. Last update till InstantX

10.16.16 Onyx Binaries: All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.16-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.16-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.16-linux.tar.gz

 

[DrkMiner]

v0.10.15.16 - Onyx Masternode Stability Update

After some more inspection I found there were multiple Masternode announcement messages propagating around the network. This update filters out all but the newest one to ensure the list is correct and up-to-date. It's not manditory to update, but please do if you can. Last update till InstantX

10.16.16 Onyx Binaries: All Users

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.16-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.16-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.15.16-linux.tar.gz

10.16.16 should be 15.16

 

[GermanRed+]

Evan, we are still seeing MN's showing up multiple times on the 0.10.15.15 masternode list command:

% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1'
3 "37.46.114.158:9999" : 1,
2 "37.46.114.175:9999" : 1,
3 "37.46.114.244:9999" : 1,
3 "37.46.114.245:9999" : 1,
2 "37.46.114.58:9999" : 1,
2 "37.46.114.66:9999" : 1,
2 "37.46.114.76:9999" : 1,
2 "37.46.114.94:9999" : 1,

Please notice that 37.46.114.24{4,5} were listed twice before 0.10.15.15. They are listed thrice now. Is anyone else seeing the same thing on their darkcoind? Will that be addressed by the enforcement or is it another exploit? If this is another exploit, will simply checking the number of occurrences and rejecting these nodes get rid of this problem, at lease temporarily?

And, thanks for the update. Let's hope the enforcement will soon get rid of the nodes getting paid without acting as a masternode.

 

[DrkMiner]

Evan, we are still seeing MN's showing up multiple times on the 0.10.15.15 masternode list command:

% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1'
3 "37.46.114.158:9999" : 1,
2 "37.46.114.175:9999" : 1,
3 "37.46.114.244:9999" : 1,
3 "37.46.114.245:9999" : 1,
2 "37.46.114.58:9999" : 1,
2 "37.46.114.66:9999" : 1,
2 "37.46.114.76:9999" : 1,
2 "37.46.114.94:9999" : 1,

Please notice that 37.46.114.24{4,5} were listed twice before 0.10.15.15. They are listed thrice now. Is anyone else seeing the same thing on their darkcoind? Will that be addressed by the enforcement or is it another exploit? If this is another exploit, will simply checking the number of occurrences and rejecting these nodes get rid of this problem, at lease temporarily?

And, thanks for the update. Let's hope the enforcement will soon get rid of the nodes getting paid without acting as a masternode.

V10.15.16
./darkcoind masternode list | grep 37.46.114.158

Shows 3 times

 

[GermanRed+]

V10.15.16
./darkcoind masternode list | grep 37.46.114.158

Shows 3 times

Good to know before I update my MN to 0.10.15.16 which sounds like addressing this problem according Evan's comment. That may be still the case if it takes time for the excessive Masternode announcement messages to quiet down. Could you check the version by getinfo? I got the wrong version with a typo in the git command in one of the updates. If there is nothing wrong, please ignore me.

 

[DrkMiner]

Good to know before I update my MN to 0.10.15.16 which sounds like addressing this problem according Evan's comment. That may be still the case if it takes time for the excessive Masternode announcement messages to quiet down. Could you check the version by getinfo? I got the wrong version with a typo in the git command in one of the updates. If there is nothing wrong, please ignore me.

Version 15.16 Latest download link works

 

[djcrypto]

So is 15.15 already obsolete? Do I need to update to 15.16 now?

 

[AjM]

So is 15.15 already obsolete? Do I need to update to 15.16 now?

Yes, it is recommended.

 

[DrkMiner]

So is 15.15 already obsolete? Do I need to update to 15.16 now?

Yes.... Even said: "It's not mandatory to update, but please do if you can"

 

[GermanRed+]

% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1'
3 "37.46.114.158:9999" : 1,
2 "37.46.114.244:9999" : 1,
2 "37.46.114.245:9999" : 1,
2 "37.46.114.58:9999" : 1,
2 "37.46.114.66:9999" : 1,
2 "37.46.114.76:9999" : 1,
2 "37.46.114.94:9999" : 1,

After update to v0.10.15.16, 37.46.114.24{4,5} are back to listed twice now. Not sure if 0.10.15.16 has anything to do with this. But, hope that more people updating to 0.10.15.6 will help in reducing these duplicated MN entries on the list.

 

[bertlebbert]

So is 15.15 already obsolete? Do I need to update to 15.16 now?

Not to worry, Evan said Last update till InstantX

 

[eduffield]

Evan, we are still seeing MN's showing up multiple times on the 0.10.15.15 masternode list command:

% darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1'
3 "37.46.114.158:9999" : 1,
2 "37.46.114.175:9999" : 1,
3 "37.46.114.244:9999" : 1,
3 "37.46.114.245:9999" : 1,
2 "37.46.114.58:9999" : 1,
2 "37.46.114.66:9999" : 1,
2 "37.46.114.76:9999" : 1,
2 "37.46.114.94:9999" : 1,

Please notice that 37.46.114.24{4,5} were listed twice before 0.10.15.15. They are listed thrice now. Is anyone else seeing the same thing on their darkcoind? Will that be addressed by the enforcement or is it another exploit? If this is another exploit, will simply checking the number of occurrences and rejecting these nodes get rid of this problem, at lease temporarily?

And, thanks for the update. Let's hope the enforcement will soon get rid of the nodes getting paid without acting as a masternode.

Those masternodes are indeed unique and valid DRK. They're just tied to the same daemon. Addresses are not unique within the system due to the fact that, someone who doesn't actually own it could claim it in the masternode list, then you couldn't register your node. There's a couple proposed solutions to this such as the multi-path routing system, which I've been working on. So, it's a known issue and it needs to be dealt with carefully.

 

[DrkMiner]

eduffield, with the latest updated, could we run 1 wallet with multiple addresses?

masternode start many

 

[crowning]

eduffield, with the latest updated, could we run 1 wallet with multiple addresses?

masternode start many

I'm not Evan nor do I play him in films, but nope, it's not in the source code so most probably also not in the binaries.

 

[darkstrike420]

Those masternodes are indeed unique and valid DRK. They're just tied to the same daemon. Addresses are not unique within the system due to the fact that, someone who doesn't actually own it could claim it in the masternode list, then you couldn't register your node. There's a couple proposed solutions to this such as the multi-path routing system, which I've been working on. So, it's a known issue and it needs to be dealt with carefully.

Regarding the planned IP obfuscation feature, wouldn't it be easier to just run the Darkcoin network under I2P similar to how other coins are doing it?

I2P is being recoded in C++. You can look at it here: https://github.com/PrivacySolutions/i2pd

 

[bertlebbert]

I'm not Evan nor do I play him in films, but nope, it's not in the source code so most probably also not in the binaries.

One wallet, multiples of 1000 DRK - each in a separate address... That doesn't work?

 

[splawik21]

One wallet, multiples of 1000 DRK - each in a separate address... That doesn't work?

You mean having one file wallet.dat and inside of him many getnewaddresss MN# so having 10k coins you have 1 main address with 9 getnewaddresses which contains 1000drk....
well this is still in alpha mode but heard it worked... didn`t try....yet....

 

[bertlebbert]

You mean having one file wallet.dat and inside of him many getnewaddresss MN# so having 10k coins you have 1 main address with 9 getnewaddresses which contains 1000drk....
well this is still in alpha mode but heard it worked... didn`t try....yet....

Yes, one wallet, 10 different 0-addresses... I thought someone said that worked

 

[UdjinM6]

only 3 left for me on 15.16

darkcoind masternode list | sort | uniq -c | grep -v '^[^"]*1'
      2     "37.46.114.158:9999" : 1,
      2     "37.46.114.244:9999" : 1,
      2     "37.46.114.245:9999" : 1,

 

[splawik21]

Yes, one wallet, 10 different 0-addresses... I thought someone said that worked

Flare was using this as i remember.... but he said that it is still alpha and that need to be feeded

 

[crowning]

Yes, one wallet, 10 different 0-addresses... I thought someone said that worked

Not with this version.

flare posted a link to a test-version, but with all the updates since then I wouldn't use that old version any more.

 

[GermanRed+]

Those masternodes are indeed unique and valid DRK. They're just tied to the same daemon.

When a masternode is unique, shouldn't it have a single external IP address? I could imagine something like running the same daemon thrice with some intelligent firewall tagging and forwarding may let some run three darkcoind on the same host. Or, I'm completely off here. Please enlighten me in the dark.

Addresses are not unique within the system due to the fact that, someone who doesn't actually own it could claim it in the masternode list, then you couldn't register your node. There's a couple proposed solutions to this such as the multi-path routing system, which I've been working on. So, it's a known issue and it needs to be dealt with carefully.

I don't really get it. I understand the danger of letting someone who doesn't own the addresses claim it and prevent the true owner from registering the node. It should hurt the owner. But, it seems to me that this guy at 37.46.114.158 is claiming others' addresses and hijack other MN payments? Then, I'm confused because you said these MN's are unique and valid. Sorry, I must misunderstood something since I'm not a network programmer. I don't want to take too much time of your time to explain this to me since it seems that you are very busy implementing a solution. Perhaps, someone else will do this on the forum for you when they have time and the knowledge.