Search results

I actually did this by accident, the result is a few pages back..

Updated my 15 testnet masternodes, 5 of them are bringing in hash power..

// calculate additional masternode vote info to include in hash So the vote info on clients need to be the same? and we cannot have inconsistencies with the votes on different clients? = different hash. ?

So how about announce a "stress test day"? So making testing like an event? We could maybe setup loadbalacer to distribute load to several p2pools by redirecting IPs? So we would have balanced pools, and ofcourse increased change on finding the block at the same time?

now miners spread amongst 5 different masternodes..

somethings up with sv01 http://tdrk.poolhash.org/ ---- EDIT1: and directed some serious hashing power directly to one of my masternodes.. EDIT2: darkcoind getinfo { "version" : 101102, "protocolversion" : 70019, "walletversion" : 60000, "balance" : 1015.00000000, "blocks" ...

Now total 15 masternodes up for me..

NP. I just make 5 more for those extras.. =P

5 more masternodes need 1000 tDRKs each msYutqQEWZffG1Suabe68NSbdeBtq2DFnQ mxXzjr3E1AtMGwauVbZ5NNHsaecnXhXdA8 mhYnT3kUwuZr68ECQMvaVywCwZNVWmmpcT mkwhKitKC8g44QUwb68okX4Ac8m6GqDWQx mjPo4a6zS3L8GvWZCjDNVG3GeYwc9vQYmA

-- from ...45.36 machine... darkcoind listaddressgroupings [ [ [ "mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDF", 15.00000000, "0" ] ], [ [ "mjeLkyqoDXGrAD6JXGtKNkdaZu6T6WsnBp", 1000.00000000 ] ] ]

not a big deal but tdrk,poolhash,org show the ip _._.45.36 listed twice, with two different wallet addresses. mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDF was originally correct, but I added new address alongside that address (mjeLkyqoDXGrAD6JXGtKNkdaZu6T6WsnBp) with 1000 tDRKs. There were the case that...

Im setting up more testnet masternodes, please provide 1000 tDRKs to each. mtNqTbTj8bDXCPWE9ocBMwE9BhVNULi1yz n3kW9Ps15HaVD2KsCd2CuydiLh4uDhcR1a msTHofF9C2UoWk4BEs4X1MJ4ZLTTRS67Mg mjeLkyqoDXGrAD6JXGtKNkdaZu6T6WsnBp

thnx, now just waiting for the confirmations

Setting up masternode, please send 1000 tDRKs to mvTxKB6Akb2rk9jC1JAZLyw2Lu9PwpwUDF

+111

pointed ~36MH/s to Mpos + Stratum pool.. atleast for a while..

Is it just me, but I have a feeling that if there are nodes in that list that are forked, the sync wont happen? I would try to add just one node and try syncing..

Some more.. 2014-06-03 10:52:04 CDarkSendPool::NewBlock 2014-06-03 10:52:04 ProcessBlock: ACCEPTED 2014-06-03 10:52:04 sending: inv (37 bytes) 2014-06-03 10:52:04 received: getblocks (837 bytes) 2014-06-03 10:52:04 getblocks 13046 to...

EDIT: found out why it didn't start syncing blocks, I did not shutdown p2pool which was using the darkoind, stopped darkcoind removed everything but wallet.dat and started darkcoind.. this procedure did not start syncing blocks. when I stopped the p2pool did the same procedure to darkcoind it...

xxxxx --testnet listaddressgroupings [ [ [ "n1gvBwfPGaUt5KAFko2s5pmZfJqc1Spkga", 0.00000000, "0" ] ], [ [ "mtPDe3eMkhsDfFTJznm5kubrSpz1uKRqkz", 896.13249801, "0" ] ] ] xxxx...