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

v0.10.11.x RC3 Prelaunch Testing

Status
Not open for further replies.

eduffield

Core Developer
****** PLEASE UPDATE TO 9.11.0 OR 10.11.0 *******

Hello everyone!

We're going to be testing the changes outlined in the this post: https://darkcointalk.org/posts/9557/


As mentioned before 9.11.x and 10.11.x permanently turn on masternode payments in a way that is completely 100% safe for the network. We're also going to be using an innovative strategy utilizing a modified version of Hiro's checkpointing code that gives it the ability to remotely tell the network to activate and deactivate enforcement in the future. This way if enforcement causes any issues the code can retroactively turn it off for the whole blockchain, then I can manually set a checkpoint to bring all clients back on the same chain.

New features included are:
  • Modified checkpointing (able to remotely turn on/off enforcement)
  • Hashing algorithm for including the voting information into the block hash in a tamper proof way
  • Confirmations required fix for masternode inputs (was one off)
  • Masternode pruning (inactive masternodes fall off the lists after a period of time)
  • Min protocol version (clients will now only talk to recent client versions)
Can we get some mining power?:

Mpos + Stratum: http://ec2-54-198-19-83.compute-1.amazonaws.com
-- connection string: sgminer.exe -o stratum+tcp://54.198.19.83:3333 -u eduffield.1 -p x

P2Pool: http://54.213.244.5:18998/static/
-- connection string: sgminer.exe -o stratum+tcp://54.213.244.5:18998 -u mt2ScQSwpsohN8KC9CuFGCuCuvyJkCY8iEn1K5Y5JGe5svtfmrJ6J9McsZPJdWXPvuRq -p 1

NOMP: http://54.183.73.24/ (Thanks Chaeplin!)
-- connection string: sgminer.exe -o stratum+tcp://54.183.73.24:3333 -u
Block Explorer: http://23.23.186.131:1234/chain/DarkCoin

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

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

Thanks everyone,

The Darkcoin Team
 
Last edited by a moderator:
There's a few hours to update before activation of the new code:

#define START_MASTERNODE_PAYMENTS_TESTNET 1403568776 //Tue, 24 Jun 2014 00:12:56 GM

You can tell when it activates with getblocktemplate:

$ ./darkcoind getblocktemplate
{
"version" : 2,
"previousblockhash" : "000000008ed76d7c20fe86a0b0d1ff0b59bf6b6fd1d9463c1f7037b1c9c0e6f8",
"transactions" : [
],
"coinbaseaux" : {
"flags" : "062f503253482f"
},
"coinbasevalue" : 2500000000,
"target" : "000000013d0a0000000000000000000000000000000000000000000000000000",
"mintime" : 1403552570,
"mutable" : [
"time",
"transactions",
"prevblock"
],
"noncerange" : "00000000ffffffff",
"sigoplimit" : 20000,
"sizelimit" : 1000000,
"curtime" : 1403553536,
"bits" : "1d013d0a",
"height" : 24446,
"votes" : [
],
"payee" : "",
"masternode_payments" : false,
"enforce_masternode_payments" : false
}

Here's how you get the next enforcement epoch (currently 2099)
./darkcoind masternode enforce
4085657524
 

Just to be double sure, this is testnet=0 or 1 ?

Will bring in 5x 4mh/s divided by all mining platforms
 
Hmm, I'm getting errors with the qt client. I'll figure it out in a bit.

edit: Starting with -reindex fixed this
 
Last edited by a moderator:
Ok, great, I'm on it.

NOMP and MPOS are working. P2pool is giving me "waiting for work"

EDIT: p2pool not working
 
Last edited by a moderator:
Anyone please send me a boatload of testnet darks? This is not address 0, and I'll send it out to whoever needs it

mpoM9TqSzKjQ8EeFJuYw4nQyN2jrwqitTX

Something like 50 gzillions testDRKs should do :tongue:
 
Anyone please send me a boatload of testnet darks? This is not address 0, and I'll send it out to whoever needs it

mpoM9TqSzKjQ8EeFJuYw4nQyN2jrwqitTX

Something like 50 gzillions testDRKs should do :tongue:

Code:
sendtoaddress mpoM9TqSzKjQ8EeFJuYw4nQyN2jrwqitTX 100000
df9c72009a4e7c47d9b0d8e2f8a8cbc8ea3818718aacc1f07fca6da2df184917

Block 24486 - TX df9c72

Enjoy your tDRK wealth :grin:
 
damn it... one of my remote nodes is getting constantly stuck at 88828... done --reindex and --rescan 3x now... grrr
 
Anyone please send me a boatload of testnet darks? This is not address 0, and I'll send it out to whoever needs it

mpoM9TqSzKjQ8EeFJuYw4nQyN2jrwqitTX

Something like 50 gzillions testDRKs should do :tongue:

Actually address 0 isn't required for a masternode. It's just an input that's 1000 DRK
 
Actually address 0 isn't required for a masternode. It's just an input that's 1000 DRK

Really? Well I missed that change it seems. But now that we're on it, a few versions back, when we did use address 0, when masternode=1 was in the conf file, when we tried to move more than the 1k deposit the daemon would "lock" it, not allowing moving those funds. That was a great failsafe feature to not accidentally deactivate the masternode.
Would be cool to have that.

Now that address 0 is not required, how can be sure not to touch the 1k deposit?
 
Status
Not open for further replies.
Back
Top