v0.10.11.x RC3 Prelaunch Testing

Status
Not open for further replies.

jimbit

Well-known Member
Foundation Member
May 23, 2014
228
103
203
****** PLEASE UPDATE TO 9.11.3 OR 10.11.3 ******

I've added a new masternode payment system for non-enforcement mode and ported over a bunch of changes/improvements from @rebroad on github (thanks!)

Binaries (stable)
http://www.darkcoin.io/downloads/forkfix/darkcoin-qt
http://www.darkcoin.io/downloads/forkfix/darkcoind

RC3 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc3/darkcoin-qt
http://www.darkcoin.io/downloads/rc3/darkcoind
Can we run this on mainnet now?
 

minersday

Member
Apr 9, 2014
77
19
48
Updated my 15 testnet masternodes, 5 of them are bringing in hash power..

****** PLEASE UPDATE TO 9.11.3 OR 10.11.3 ******

I've added a new masternode payment system for non-enforcement mode and ported over a bunch of changes/improvements from @rebroad on github (thanks!)

@rebroad's changes
- Added ability to sync from multiple nodes at once
- Added masternodes to address data (allowing mult-sync from masternodes which is awesome)
- Added a bunch of useful debug info, cleaned up some logging
- Added new proxytoo option
- NodeID's for debug purposes

Thanks for this!!

Binaries (stable)
http://www.darkcoin.io/downloads/forkfix/darkcoin-qt
http://www.darkcoin.io/downloads/forkfix/darkcoind

RC3 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc3/darkcoin-qt
http://www.darkcoin.io/downloads/rc3/darkcoind
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
****** PLEASE UPDATE TO 9.11.3 OR 10.11.3 ******

I've added a new masternode payment system for non-enforcement mode and ported over a bunch of changes/improvements from @rebroad on github (thanks!)

@rebroad's changes
- Added ability to sync from multiple nodes at once
- Added masternodes to address data (allowing mult-sync from masternodes which is awesome)
- Added a bunch of useful debug info, cleaned up some logging
- Added new proxytoo option
- NodeID's for debug purposes

Thanks for this!!

Binaries (stable)
http://www.darkcoin.io/downloads/forkfix/darkcoin-qt
http://www.darkcoin.io/downloads/forkfix/darkcoind

RC3 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc3/darkcoin-qt
http://www.darkcoin.io/downloads/rc3/darkcoind
Tag v0.9.11.3 in git is referencing commit df7734b684, whereas latest commit was bb7fa4f92d - is this correct? Wanted to test my gitian-builds against v0.9.11.3 and need to ensure the tag is correct :)
 
Last edited by a moderator:

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
First, thanks for this guide. If somebody get access to the key that was created with
enter: "masternode genkey" and press enter.
Is he able to steal the coins ?
Question is because of the key is stored onto the online server and there could be security issues
flare could someone using the private key generated by masternode genkey to authenticate with the network as the masternode and abuse that somehow?
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
3 nodes updated.

payout stats

Node A = 45 tDRK (12%)
Node B = 140 tDRK (37%)
Noce C = 195 tDRK (51%)

Seems fair so far, still too early for equal dist. :cool:

eduffield - Any news on a block explorer, or Abe patch? I'm missing being able to check earnings quick
 
Last edited by a moderator:

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
flare could someone using the private key generated by masternode genkey to authenticate with the network as the masternode and abuse that somehow?
As far as i understood eduffield regarding the masternodeprivkey, the key is randomly generated and never used in the wallet.

Masternodes now sign their 1000DRK vin for the first message to the network, then they specific a second pubkey that they will sign all further messages with. This second signing key must be specified for all masternodes in the configuration with the option "masternodeprivkey"

To generate a key, boot up the client and execute the command "masternode genkey" and then take the output and put it in the configuration like this "masternodeprivkey=COMMANDOUTPUT. There is also a new protocol command called "dseep" which is signed with this secondary key. This key will never be used in the wallet and is generated randomly.

This allows the client to encrypt the wallet and still be able to sign new messages to the network.
So even if someone gets access to this key, he will not have access to your 1000DRK vin.

Nevertheless the attacker might use the key to sign messages to the network, so he could presumly register a new pubkey/IP combination to hijack payouts - but i have not thought through all implications of this attack-vector and if it's feasable - or if Evan has already countermeasures in place (he is usually very good at this :) )
 
  • Like
Reactions: yidakee

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
As far as i understood eduffield regarding the masternodeprivkey, the key is randomly generated and never used in the wallet.



So even if someone gets access to this key, he will not have access to your 1000DRK vin.

Nevertheless the attacker might use the key to sign messages to the network, so he could presumly register a new pubkey/IP combination to hijack payouts - but i have not thought through all implications of this attack-vector and if it's feasable - or if Evan has already countermeasures in place (he is usually very good at this :) )
Would you have fun with it if I gave you one of my node's masternodeprivkey?
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
I actually did this by accident, the result is a few pages back..
Dont think its the same thing. I've also managed to do buggy'ish multi-ticket too. We're talking about a third party hijacking the payouts

as flare put it

Nevertheless the attacker might use the key to sign messages to the network, so he could presumly register a new pubkey/IP combination to hijack payouts - but i have not thought through all implications of this attack-vector and if it's feasable - or if Evan has already countermeasures in place (he is usually very good at this :) )
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
3 nodes updated. I just updated daemon and ran debug command, says successfully started node.

payout stats

Node A = 45 tDRK (12%)
Node B = 140 tDRK (37%)
Noce C = 195 tDRK (51%)

Seems fair so far, still too early for equal dist. :cool:

eduffield - Any news on a block explorer, or Abe patch? I'm missing being able to check earnings quick
Abe it working, it was just stuck yesterday.
 
  • Like
Reactions: yidakee

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Abe it working, it was just stuck yesterday.
Nevertheless it fails to parse the masternode votes, as their position in the block moved to the blockheader.

Code:
Masternode Votes


Blockheight    Pubkey    Votes
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Would you have fun with it if I gave you one of my node's masternodeprivkey?
Having fun with cross-compilers currently:

Code:
[email protected]:~/build/distsrc$ ls -l DarkCoin-Qt.app/Contents/MacOS
total 12064
-rwxrwxr-x 1 ubuntu ubuntu 12350516 Jun 25 21:20 DarkCoin-Qt
[email protected]:~/build/distsrc$ file DarkCoin-Qt.app/Contents/MacOS/DarkCoin-Qt
DarkCoin-Qt.app/Contents/MacOS/DarkCoin-Qt: Mach-O 64-bit executable
Looks very promising :)
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
As far as i understood eduffield regarding the masternodeprivkey, the key is randomly generated and never used in the wallet.
So even if someone gets access to this key, he will not have access to your 1000DRK vin.
Nevertheless the attacker might use the key to sign messages to the network, so he could presumly register a new pubkey/IP combination to hijack payouts - but i have not thought through all implications of this attack-vector and if it's feasable - or if Evan has already countermeasures in place (he is usually very good at this :) )
So the only thing that key can do is ping the network is say your node is alive, it can also remove it from the masternode list.
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
I somehow doubt thats worth hacking the masternode :D
I disagree. Same principle as DDoS competing pools? But then again, either a major exploit is found, or the time and trouble might not affect global payouts.
 

HammerHedd

Member
Mar 10, 2014
182
34
88
Might be the problem? BTW, what did Evan mean by new hashing algorithm? He didn't change X11, did he? Is there something else that gets hashed now as well? I missed that part, thanks for any clarification. Gotta get back to this later, so sorry!

Dear HammerHead, I didn't see a newer version posted, how do I check my version number? I mean I'm on version 10.11.02 protocolversion 70019. I don't know where to find the "x.x.x.x:18998 instead of 8998 (or 7903)"

Hard drive died, gotta put new one into the main Ubuntu. I stuck it into another machine because I thought the old drive came back to life well enough, LOL, but now I need to finally replace that drive.
The version i was referring to is the version of p2pool, which is currently commit fac408d. As I type this, tho, I realize that you didn't say you were running a p2pool, only that you were trying to mine on one. In any case, if p2pool is running on testnet, it is using port 18998 instead of port 8998 or port 7903 as on the real network. Because of this, you'd have to point your testnet miner to the the address at port 18998, which is something that I forgot when I was initially setting up a p2pool on testnet.
That said, if you ARE trying to set up a p2pool on an AWS instance, I also wanted to remind you to open port 18998 and 18999 in the security settings as well.

And if you wanted to try to determine if it is a miner config problem or a p2pool config problem, you could try pointing your miner at my testnet p2pool node, which is working at 54.88.172.2:18998. if you can't connect there, it is probably a miner issue, because I can connect from various places to that IP. If you CAN connect to my pool, then your miner is probably not the issue, and you can start working through your p2pool config.

:) because that's what I ended up doing last night :)
 

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
Having fun with cross-compilers currently:

Code:
[email protected]:~/build/distsrc$ ls -l DarkCoin-Qt.app/Contents/MacOS
total 12064
-rwxrwxr-x 1 ubuntu ubuntu 12350516 Jun 25 21:20 DarkCoin-Qt
[email protected]:~/build/distsrc$ file DarkCoin-Qt.app/Contents/MacOS/DarkCoin-Qt
DarkCoin-Qt.app/Contents/MacOS/DarkCoin-Qt: Mach-O 64-bit executable
Looks very promising :)
Awesome!
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Having fun with cross-compilers currently:

Code:
[email protected]:~/build/distsrc$ ls -l DarkCoin-Qt.app/Contents/MacOS
total 12064
-rwxrwxr-x 1 ubuntu ubuntu 12350516 Jun 25 21:20 DarkCoin-Qt
[email protected]:~/build/distsrc$ file DarkCoin-Qt.app/Contents/MacOS/DarkCoin-Qt
DarkCoin-Qt.app/Contents/MacOS/DarkCoin-Qt: Mach-O 64-bit executable
Looks very promising :)
Awesome!
Finally got the gitian-descriptors for OSX build working.

If someone likes to test if the binary distribution is at least starting see link below - i am not able to test it, as i don't even own a mac. The binary is cross compiled on a Ubuntu precise host without any errors, so if i did not f**k up the dmg packaging it should work.

version 0.9.11.5 (Mac OSX)
--> http://bamboo.darkcoin.qa/browse/DOD-DRK-28/artifact/QTL/gitian-osx-darkcoin/DarkCoin-Qt.dmg

version 0.9.11.5 (Win32)
--> http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-23/gitian-win-darkcoin/32/darkcoin-qt.exe
--> http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-23/gitian-win-darkcoin/32/daemon/darkcoind.exe

Next on my wishlist: Linux 32/64 and Windows 64. After that i will create a pull request for Evan, so that the descriptors can be merged into darkcoin master and we can start to distribute signed gitian-builds :)
 
Last edited by a moderator:

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,637
3,536
1,183
Finally got the gitian-descriptors for OSX build working.

If someone likes to test if the binary distribution is at least starting see link below - i am not able to test it, as i don't even own a mac. The binary is cross compiled on a Ubuntu precise host without any errors, so if i did not f**k up the dmg packaging it should work.

version 0.9.11.5 (Mac OSX)
--> http://bamboo.darkcoin.qa/browse/DOD-DRK-28/artifact/QTL/gitian-osx-darkcoin/DarkCoin-Qt.dmg

version 0.9.11.5 (Win32)
--> http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-23/gitian-win-darkcoin/32/darkcoin-qt.exe
--> http://bamboo.darkcoin.qa/artifact/DWD-DRK/QTL/build-23/gitian-win-darkcoin/32/daemon/darkcoind.exe

Next on my wishlist: Linux 32/64 and Windows 64. After that i will create a pull request for Evan, so that the descriptors can be merged into darkcoin master and we can start to distribute signed gitian-builds :)
Nice! I was able to run it on mac but have some strange fonts:
original:

your version:


Didn't tested send/receive though

EDIT: it looks more "strange" live then on screenshot, don't know why...
 

flare

Administrator
Dash Core Team
Moderator
May 18, 2014
2,287
2,406
1,183
Germany
Nice! I was able to run it on mac but have some strange fonts:
original:

your version:


Didn't tested send/receive though

EDIT: it looks more "strange" live then on screenshot, don't know why...
Thanks for the feedback.

Hmm, i ask myself if the different fonts are related to the fact that the official client is built against Qt4, where mine is built against Qt5 :)
 

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Sorry I haven't been around and if this question is part of 10.11.04 issue, but does this mean my node is being rejected?
Code:
2014-06-27 06:38:28 received getdata for: block 000000000006b30a9c2aa4a951607b2e6eda93d96356bcb735f8c9c923d57da1 peer=246
2014-06-27 06:38:35 peer=474 says we are misbehaving 20
2014-06-27 06:38:37 peer=474 says we are misbehaving 20
2014-06-27 06:38:38 peer=474 says we are misbehaving 20
2014-06-27 06:38:55 received getdata for: block 00000000000a0ed3b90352bcb05460b176396c9b950f5fba4afc7d870c0863ca peer=246
2014-06-27 06:39:11 Got bad masternode address signature
2014-06-27 06:39:11 Misbehaving: 192.99.184.49:9999 (60 -> 80)
And will updating to 10.11.05 fix this issue for me?

Answer was yes :)
 
Last edited by a moderator:

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
So anyway, I know you all are dealing with a pool issue right now, but I can't help but wonder if you've noticed any issues yet? Have we had simultaneous block solutions? Is everything running well under the hood?
 
  • Like
Reactions: yidakee

TanteStefana

Grizzled Member
Foundation Member
Mar 9, 2014
2,861
1,854
1,283
Well, I'm going to get another cheap hard drive tomorrow, LOL (i have the worst luck with HDs) and start up another old machine so I can run a masternode and mine on testnet. And if I can get my cpu miner working on my current ubuntu, I'll have that one up and running too. That way I'll be ready to slip in new versions of the wallet and it won't take me forever to catch up with the testing (as usual, LOL)

Hope we can start soon! (need dancing baby pic here) :D
 
  • Like
Reactions: yidakee
Status
Not open for further replies.