Search results

if we think RC4 is working as expected.. then lets fork the rc3 pools out... I should have just left my MN's running on RC3

Not sure if this is a problem or not.. but I should have gotten a payment ( a few actually) for my MN <jimbit_> this payment from wafflepool did not go to ME.. even tho I was the expected payee. 2014-08-17 14:56:54 120629 wafflepool 4182.75 5 1 Xy7NQQ5q4AqSjJags8eNbSRLWxAP9SeX7g RC4...

I am still seeing some debug in console on mainnet. successfully started masternode ubuntu@ip-10-251-84-27:~$ conflict with in-memory transaction : COutPoint(846e161d386fdae8c1617aab61b295061d892e0d50969fc7830c12887c39d39b, 5)

A nice boring launch!!! Which is exactly what you want when you do a release, or land an airplane! Great Job Evan, Flare, Chap, and everyone involved

with 21 I was still getting some messages in the console: successfully started masternode ubuntu@ip-10-254-36-45:~$ conflict with in-memory transaction : COutPoint(004d33614861b0c4707c0 82ed50cd62c91f6ef95b27745650cd7da3718e72a18, 2) conflict with in-memory transaction ...

my latest console: 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 ...

got this one: ubuntu@ip-10-254-36-45:~$ maxconnections check 248 ubuntu@ip-10-254-36-45:~$ darkcoind getinfo { "version" : 101220, "protocolversion" : 70030, "walletversion" : 60000, "balance" : 18591.15356589, "anonymized_balance" : 0.00000000, "blocks" : 12893...

getting debug messages in the console with this update edit: Evan, pretty sure this is critical. debug is coming to the standard output.

done: "version" : 101206, "protocolversion" : 70022, "walletversion" : 60000, "balance" : 14330.91276589, "blocks" : 3692,

the string: "My entries are not correct!" is NOT in my debug.log

is it possible that I am the current MN when there are invalid created transactions? I have a node that is not active with all the players, namely p2pool. https://test.drk.mn/masternodes.html node: mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4 if I understand correctly, 2 or more nodes are doing the...

I am wondering why I am the only node that p2pool doesn't consider active. which also cause the mixup in consensus when I am the current node. mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4

I have always been inactive at p2pool since I regenerated my key to get current RC4 running the node:

How hard is it to DDos 700 diff Ip's at once?

wierd. my wallet shows a different balance then the https://test.drk.mn/masternodes.html (7442.657965840) mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4 "version" : 101203, "protocolversion" : 70021, "walletversion" : 60000, "balance" : 6561.45796584, edit: looks like only the 12.1 version is...

MN updated: mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4 "version" : 101202, "protocolversion" : 70021, "walletversion" : 60000, "balance" : 6263.65796584,

my MN updated, but the html page still shows it as old version, active: mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4 https://test.drk.mn/masternodes.html

the question remains, is RC4 compatible with RC3 on mainnet?

flare I set my maxconnections=2 and add these 2 nodes, deleted my data folder and restarted. I get the same behaviour, it gets to block 18 then forks to the old chain.

I am also concerned. I cannot get version v0.10.11.5-unk-beta to sync with new chain.