v0.10.12.x RC4 Testing

Status
Not open for further replies.
eduffield

eduffield

Core Developer
****** PLEASE UPDATE TO 9.12.4 OR 10.12.4 *******

Hello everyone!

We're going to start systematically testing all of the changes for RC4. Changes include:

- Darksend+ (changes outlined here: https://darkcointalk.org/threads/development-updates-july-15th.1788/)
- Masternode consessus voting spork (with enforcability, we'll switch enforcing on and test this)
- Masternode list syncing capabilities - Nodes should be able to ask and get into sync when discrepancies popup

Kristov Atlas is also going to be doing a code review during the test period and we'll fix anything he finds before the RC4 release. For more information about this (and donation address), please see his post here: http://www.reddit.com/r/DRKCoin/comments/2aw4wy/donations_for_darksend_code_review/

Note: The blockchain had to be restarted, so all of you will have to collect your test darkcoin again. Although, it's really easy to collect right now, so have at it :)

Mpos + Stratum: http://ec2-54-91-161-78.compute-1.amazonaws.com/index.php
-- connection string: sgminer.exe -o stratum+tcp://54.91.161.78:3333 -u eduffield.1 -p x

Nomp : http://54.183.73.24/

How can you help?
1.) Point some hashing power at once of the pools!
2.) Run the "masternode-rc4" branch on testnet: https://github.com/darkcoinproject/darkcoin/tree/master-rc4

Thanks everyone,

The Darkcoin Team
 
Last edited by a moderator:
eduffield said:
****** PLEASE UPDATE TO 9.12.0 OR 10.12.0 *******

Hello everyone!

We're going to start systematically testing all of the changes for RC4. Changes include:

- Darksend+ (changes outlined here: https://darkcointalk.org/threads/development-updates-july-15th.1788/)
- Masternode consessus voting spork (with enforcability, we'll switch enforcing on and test this)
- Masternode list syncing capabilities - Nodes should be able to ask and get into sync when discrepancies popup

Kristov Atlas is also going to be doing a code review during the test period and we'll fix anything he finds before the RC4 release. For more information about this (and donation address), please see his post here: http://www.reddit.com/r/DRKCoin/comments/2aw4wy/donations_for_darksend_code_review/

Note: The blockchain had to be restarted, so all of you will have to collect your test darkcoin again. Although, it's really easy to collect right now, so have at it :)

Mpos + Stratum: http://ec2-54-91-161-78.compute-1.amazonaws.com/index.php
-- connection string: sgminer.exe -o stratum+tcp://54.91.161.78:3333 -u eduffield.1 -p x

How can you help?
1.) Point some hashing power at once of the pools!
2.) Run the "masternode-rc4" branch on testnet: https://github.com/darkcoinproject/darkcoin/commits/masternode-rc4

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

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

Thanks everyone,

The Darkcoin Team
Click to expand...
Nice one!

Will start updating the dnsseeder for testnet first :)
 
compile error with msys-mingw64 in main.cpp function GetMasternodeRank
uint isn't a defined type, had to change to unsigned int
 
Sent some hash towards testnet. Assuming someone knew how to run masternodes, what would they need to be doing differently to run testnet-masternodes other than using the different binary? port to 19999 rather than 9999 and have wallet with 1k tDRK, is that about it?
 
flare said:
Will build 0.9.12.0 for Windows asap
Click to expand...
thank you... btw.. I continue to get forked trying to run my current windows .. even when I limit my connections to 1 and connect to a new testnet node

It does OK for about 17 blocks, then this:

Code: 
2014-07-19 21:51:04 ProcessBlock: ACCEPTED
2014-07-19 21:51:04 received block 000000ab6ae22728c701e15a13dfa022c88f17a4e0fd71f073b0a720229de22b peer=1
2014-07-19 21:51:04 SetBestChain: new best=000000ab6ae22728c701e15a13dfa022c88f17a4e0fd71f073b0a720229de22b  height=16  log2_work=24.087482  tx=17
date=2014-04-30 19:38:20 progress=0.000691
2014-07-19 21:51:04 ProcessBlock: ACCEPTED
2014-07-19 21:51:04 received block 00000541dfefddc46d4a7ef3873375db4a6f5b1c06a84b67346fb88e07f024d0 peer=1
2014-07-19 21:51:04 SetBestChain: new best=00000541dfefddc46d4a7ef3873375db4a6f5b1c06a84b67346fb88e07f024d0  height=17  log2_work=24.169944  tx=18
date=2014-07-18 15:32:31 progress=0.000732
2014-07-19 21:51:04 ProcessBlock: ACCEPTED
2014-07-19 21:51:04 received block 000000d275d8dc93e7bf8c358463c97e12be9b2b17d4e64770aca7af8dcb93d8 peer=1
2014-07-19 21:51:04 ERROR: AcceptBlock() : incorrect proof of work
2014-07-19 21:51:04 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-07-19 21:51:04 Misbehaving: 94.23.248.61:19999 (0 -> 100) DISCONNECTING
2014-07-19 21:51:04 disconnecting node 94.23.248.61:19999
2014-07-19 21:51:04 trying connection 158.75.35.103:19999 lastseen=0.2days
2014-07-19 21:51:04 UPnP: ExternalIPAddress = 24.112.251.57
2014-07-19 21:51:04 AddLocal(24.112.251.57:19999,3)
2014-07-19 21:51:04 UPnP Port Mapping successful.
2014-07-19 21:51:09 connection timeout
2014-07-19 21:51:09 GetMyExternalIP() received [24.112.251.57] 24.112.251.57:0
2014-07-19 21:51:09 GetMyExternalIP() returned 24.112.251.57
2014-07-19 21:51:09 AddLocal(24.112.251.57:19999,4)
2014-07-19 21:51:10 trying connection [2001:0:9d38:6ab8:4d1:31bf:e78f:4c6]:19999 lastseen=48.5days
2014-07-19 21:51:15 connection timeout
2014-07-19 21:51:15 trying connection 85.23.17.212:19999 lastseen=17.6days
2014-07-19 21:51:20 connection timeout
2014-07-19 21:51:21 trying connection 54.178.159.204:19999 lastseen=11.8days
2014-07-19 21:51:26 connection timeout
 
g8F98FF3gjafogj4 said:
Sent some hash towards testnet. Assuming someone knew how to run masternodes, what would they need to be doing differently to run testnet-masternodes other than using the different binary? port to 19999 rather than 9999 and have wallet with 1k tDRK, is that about it?
Click to expand...
In general the binary is the same for testnet/mainnet - you are just starting it with "testnet=1" parameter in darkcoin.conf. Port is chosen automagically depending on this parameter.

But for RC4 you need the RC4 binary of course :smile:
 
jimbit said:
thank you... btw.. I continue to get forked trying to run my current windows .. even when I limit my connections to 1 and connect to a new testnet node
Click to expand...
I would guess testnet blockchain 0.9.12.x is incompatible with 0.9.11.x - but eduffield needs to confirm.
 
dnsseed updated, currently only 2 nodes using new protocol version (70019) available

Code: 
# address                                        good  lastSuccess    %(2h)   %(8h)   %(1d)   %(7d)  %(30d)  blocks      svcs  version
184.73.179.187:19999                                1   1405807307   12.97%   3.41%   1.15%   0.17%   0.04%     466  00000003  70019 "/Satoshi:0.10.12/"
50.191.199.127:19999                                1   1405807321   12.97%   3.41%   1.15%   0.17%   0.04%     466  00000003  70019 "/Satoshi:0.9.12/"
 
Status
Not open for further replies.
Back
Top