****** Please Update To 10.12.20 or 9.12.20 *******
Moved most of the output to the log.
Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind
RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind
It was just a nightmare!This is an awesome team. Kudos to all testers and devs for the great progress. This is true innovation and it's amazing to watch the future being built before my eyes.
Having said that, given the history, please indulge me in a thought experiment:
You wake up after RC4's release to a frantic post-mortem in this thread. Something broke badly on mainnet that didn't affect testnet, and everything had to be reverted.
What probably happened, and what should have been done now to detect the problem in advance?
github is still with the debug on the console.
Edit: Evan if you could push your changes.
Sending D+ still says n/a on the sending address... should it be like this ?
master-rc4 is up to date, on the console I'm just getting this:
init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading
What else are you getting?
got this one:master-rc4 is up to date, on the console I'm just getting this:
init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading
What else are you getting?
ubuntu@ip-10-254-36-45:~$ darkcoind getinfo
{
"version" : 101220,
"protocolversion" : 70030,
"walletversion" : 60000,
"balance" : 18591.15356589,
"anonymized_balance" : 0.00000000,
"blocks" : 12893,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.08658629,
"testnet" : true,
"keypoololdest" : 1405804459,
"keypoolsize" : 1001,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}
ubuntu@ip-10-254-36-45:~$
ubuntu@ip-10-254-36-45:~$ maxconnections check 248
maxconnections check 248
dmcv -done downloading
dmcv -block height ok
dmcv - masternode from vin CTxIn(COutPoint(b24d6ea739601055ae2291e9d8a400e42c1b0fe436ee2a55c51b68383a5a5837, 1), scriptSig=)
dmcv -know masternode
dmcv - found prev masternode vote for block
dmcv -received
dmcv -done downloading
dmcv -block height ok
dmcv - masternode from vin CTxIn(COutPoint(6d4a4432c876081459df5900414f3f06380254dbc33e689c961288d882a0268d, 1), scriptSig=)
for example, it fills the screen.
$ ./bin/darkcoind -?
DarkCoin version v0.9.12.20-beta
$ git pull
Already up-to-date.
$ git status
On branch master-rc4
Your branch is up-to-date with 'origin/master-rc4'.
nothing to commit, working directory clean
Freshly compiled. (Just tried again the very minute)
CreateNewBlock - network could not reach consessus on payee for block 12896
Masternode payment to OP_DUP OP_HASH160 34a8090a974e9aff175e46dc216a188d21822da9 OP_EQUALVERIFY OP_CHECKSIG
dmcv - found prev masternode vote for block
dmcv: rejecting masternode vote
ubuntu@ip-10-254-36-45:~$ maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
maxconnections check 248
conflict with in-memory transaction : COutPoint(4f7d856d0403182297b86c5804d075d6b957b13f6831da661bcea7cc0f798b64, 5)
conflict with in-memory transaction : COutPoint(6295d370a2dd26f7b10ff525c74def9cb4edfc6b00063c94afc3d5f850db6172, 3)
maxconnections check 248
maxconnections check 248
same here +master-rc4 is up to date, on the console I'm just getting this:
init message: Verifying wallet...
init message: Loading block index...
init message: Verifying blocks...
init message: Loading wallet...
init message: Loading addresses...
init message: Done loading
What else are you getting?