I wouldn't suggest it as true, but it makes DRK look like it's devs are up to something... Perception.
People can think that. They would be thinking wrong.
I wouldn't suggest it as true, but it makes DRK look like it's devs are up to something... Perception.
.20 certainly doesn't look like it will be a necessary update so we can sit tight at .19. Appears to be mostly related to debug output.Some of the MN on drk.mn show 0.10.17.20 - Majority show 0.10.17.19 - I don't see another download or udpate posts for .20?
.20 certainly doesn't look like it will be a necessary update so we can sit tight at .19. Appears to be mostly related to debug output.
https://github.com/darkcoin/darkcoin/commit/25a07f105462500f6da93a5344c66b3499b50da5
2014-12-05 15:59:51 Submitted to masternode, waiting in queue .
2014-12-05 15:59:51 AcceptToMemoryPool (tx): 176.126.247.191:9999 /Satoshi:0.10.17.19/ : accepted 9b62cd34d743043073d3f1e1026d8b545f427dfeec4e1c45300eaf3518a564e2 (poolsz 9)
2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(2408f5405306ec5e57853d32c2853ccf72849ef781ebe85bdb7d38e2297278fd, 1), scriptSig=)
2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=)
2014-12-05 15:59:51 dseep - Asking source node for missing entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=)
2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=)
2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Asking source node for missing entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(e1580a60dcaa038cc1fe6b8a8528a146ba7c66e5592ebeb1cdee047caa71aaf7, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Asking source node for missing entry CTxIn(COutPoint(e1580a60dcaa038cc1fe6b8a8528a146ba7c66e5592ebeb1cdee047caa71aaf7, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(e1580a60dcaa038cc1fe6b8a8528a146ba7c66e5592ebeb1cdee047caa71aaf7, 1), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(f87abb479826b9d6b4dd3046e6c4f85983fae510234d6b2d52a23b06880cab50, 0), scriptSig=)
2014-12-05 15:59:52 dseep - Asking source node for missing entry CTxIn(COutPoint(f87abb479826b9d6b4dd3046e6c4f85983fae510234d6b2d52a23b06880cab50, 0), scriptSig=)
2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(f87abb479826b9d6b4dd3046e6c4f85983fae510234d6b2d52a23b06880cab50, 0), scriptSig=)
Trying to denominate on V3 but keep getting dseep msgs.
Is this normal?
Code:2014-12-05 15:59:51 Submitted to masternode, waiting in queue . 2014-12-05 15:59:51 AcceptToMemoryPool (tx): 176.126.247.191:9999 /Satoshi:0.10.17.19/ : accepted 9b62cd34d743043073d3f1e1026d8b545f427dfeec4e1c45300eaf3518a564e2 (poolsz 9) 2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(2408f5405306ec5e57853d32c2853ccf72849ef781ebe85bdb7d38e2297278fd, 1), scriptSig=) 2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=) 2014-12-05 15:59:51 dseep - Asking source node for missing entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=) 2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=) 2014-12-05 15:59:51 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(cf32d891a3b8122e1bafc65bc841594d2e89d65893b8c27456a97bb83d603bb4, 0), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Asking source node for missing entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(e1580a60dcaa038cc1fe6b8a8528a146ba7c66e5592ebeb1cdee047caa71aaf7, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Asking source node for missing entry CTxIn(COutPoint(e1580a60dcaa038cc1fe6b8a8528a146ba7c66e5592ebeb1cdee047caa71aaf7, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(bd8c364673a8d7acbd8320ccc9598c6fd6b4036461b567e6203f1c6827dd5ee8, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(e1580a60dcaa038cc1fe6b8a8528a146ba7c66e5592ebeb1cdee047caa71aaf7, 1), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(f87abb479826b9d6b4dd3046e6c4f85983fae510234d6b2d52a23b06880cab50, 0), scriptSig=) 2014-12-05 15:59:52 dseep - Asking source node for missing entry CTxIn(COutPoint(f87abb479826b9d6b4dd3046e6c4f85983fae510234d6b2d52a23b06880cab50, 0), scriptSig=) 2014-12-05 15:59:52 dseep - Couldn't find masternode entry CTxIn(COutPoint(f87abb479826b9d6b4dd3046e6c4f85983fae510234d6b2d52a23b06880cab50, 0), scriptSig=)
Network is still fragmented between versions. v10.17.20 might fix log spam.
Will Evan compile a windows version, or do i need to compile from git?
Cheers
can't connect with p2pool to the new version? rpc port works fine, but p2p port gives
2014-12-05 14:33:29.636843 Testing bitcoind P2P connection to 'localhost:12102'...
2014-12-05 14:33:34.637752 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...
using 81fc6c5-dirty
from https://bitbucket.org/dstorm/p2pool-drk
SMUT = simple masternode update tool for all of you who think he's a sick fuck.I love the smell of SMUT and protocol bumps early in the morning. 4:46am and all updated.
Nope my testnet p2pool is offline probably cause of the protocol bump waiting for p2pool patch unless you want to manually update version inside networks.py i think.Anyone has their p2pool working with 10.17.19?
I didn't think start-many was being suggested for use on mainnet? I have seen multiple places stating this code isn't production ready and shouldn't be used on mainnet. Am I crazy?Nodes offline until broadcast/announce bug and fragmentation are fixed.
My guess is that the changes related to making MNs more pingable, somehow islanded the announce call from start-many. Start-many does all it's stuff, but calls the announcement and the name of that process has changed. It's untrapped, so no output except telling me that all is well while it does nothing instead.
No idea why I'm seeing shards tho...
Anyone has their p2pool working with 10.17.19?
def connectionMade(self):
self.send_version(
version=70051,
services=1,
def connectionMade(self):
self.send_version(
version=70049,
services=1,
Thanks to moocowmoo for this one:
20:08 <@moocowmoo> p2pool/bitcoin/p2p.py:22
20:08 <@moocowmoo> thats it
Edit that line to read:
Instead of:Code:def connectionMade(self): self.send_version( version=70051, services=1,
Code:def connectionMade(self): self.send_version( version=70049, services=1,
Most people are wrong about pretty much everything. That's why life is so hard for them... When they make the choice not to adopt DRK because they are wrong, they inflict that hurt on themselves and DRK.People can think that. They would be thinking wrong.
It's not idiot-proof, but it's not a complicated bit of code... It works fine if you know it's limitations. It's not rocket surgery and all this hyperbole against using it is baseless. In same-session, it actually does check for in-use VINs already assigned... So far, that's 2 people trying to come out in troll mode who haven't even looked at the code...I didn't think start-many was being suggested for use on mainnet? I have seen multiple places stating this code isn't production ready and shouldn't be used on mainnet. Am I crazy?
github @ darkcoin/darkcoinHow do I get the 10.17.20? don't know where to start to compile...
15.3% are already on the .20
83.4% are on this version .19
Definitely wasn't attempting to trollmode start on you camo. I was pointing out that both Flare and Evan have said this code isn't robust so only use it at your own risk. I can't seem to find Flare's post but he had an experience where all the vin's got muddled up and had to rebuild manually.It's not idiot-proof, but it's not a complicated bit of code... It works fine if you know it's limitations. It's not rocket surgery and all this hyperbole against using it is baseless. In same-session, it actually does check for in-use VINs already assigned... So far, that's 2 people trying to come out in troll mode who haven't even looked at the code...
It's tie-in to announcement was simply neglected. The feature is still there, it just uses a call for announcement that doesn't exist anymore, so it never broadcasts even though it's output suggests everything is fine. It's really a very small detail... I'd fix this little tidbit myself, but it ain't my place. In fact, if I get the time, I may edit the source and compile my own. It's like one freakin' word, not even a whole line of code... There has never been a lower-hanging fruit. It's hanging so low, even my dumb ass can do it...