Separate names with a comma.
Please sign up to discuss the most innovative cryptocurrency!
Discussion in 'Official Announcements' started by eduffield, Feb 10, 2015.
coinmine is updated...
2015-02-12 23:37:29 spork - new ee189614a468ff7f398299d3dfad9d81160511716cd2b4711eaf7be8ad80b64c ID 10005 Time 30 bestHeight 219151
2015-02-12 23:37:29 DisconnectBlocksAndReprocess: Got command to replay 30 blocksUpdateTip: new best=000000000002929468ddc2cfd6917772f8e30f24471637a5b4523b17af55355d height=219150 log2_work=60.976225 tx=861299 date=2015-02-12 23:25:36 progress=0.999859
2015-02-12 23:37:29 UpdateTip: new best=00000000000a8b329ffe6ab63a1ec71ea5ef96aed08fab5c6202c57896d376f2 height=219149 log2_work=60.976214 tx=861287 date=2015-02-12 23:23:22 progress=0.999833
2015-02-12 23:37:29 UpdateTip: new best=00000000000ad487fbeba11d7b5b088e09bfbc66672e06fd3463356772410b38 height=219148 log2_work=60.976203 tx=861286 date=2015-02-12 23:21:55 progress=0.999816
2015-02-12 23:37:29 UpdateTip: new best=000000000007d1636350e8f9f42dbcb978be00dab3fbacc73c28134dacd7544b height=219147 log2_work=60.976192 tx=861285 date=2015-02-12 23:21:48 progress=0.999815
2015-02-12 23:37:29 UpdateTip: new best=00000000000ef947c66a906289bc5d67ed8a552b7553373ba98222eedaa5d54f height=219146 log2_work=60.97618 tx=861282 date=2015-02-12 23:17:51 progress=0.999768
2015-02-12 23:37:29 UpdateTip: new best=00000000000ee161250258d37f186dd69d977ef5f6e0aeb54e64f40be0b22ed9 height=219145 log2_work=60.976169 tx=861281 date=2015-02-12 23:16:54 progress=0.999757
2015-02-12 23:37:29 UpdateTip: new best=00000000000fb9dace8f7b5792593d6b26996e970dfe8cdf68eb8dbfed51f30e height=219144 log2_work=60.976158 tx=861278 date=2015-02-12 23:14:59 progress=0.999734
2015-02-12 23:37:29 UpdateTip: new best=00000000000779438053eb4d893d2fb191ce878756816da51475f39e35b71f1a height=219143 log2_work=60.976147 tx=861277 date=2015-02-12 23:14:41 progress=0.999730
2015-02-12 23:37:29 UpdateTip: new best=000000000001d2e2e9d313aef5db729144b7f6335d2c32a351b7d6203e2f57bc height=219142 log2_work=60.976134 tx=861273 date=2015-02-12 23:07:22 progress=0.999644
2015-02-12 23:37:29 UpdateTip: new best=000000000003a650d8f26147ba046db86b832cf8dc32dbb8235da77cf8f32f66 height=219141 log2_work=60.976122 tx=861270 date=2015-02-12 23:06:26 progress=0.999633
2015-02-12 23:37:29 UpdateTip: new best=00000000000d0d4f49aad4c4a0b468ce57d4c73781784335dbe45eac795afb7a height=219140 log2_work=60.97611 tx=861266 date=2015-02-12 23:05:06 progress=0.999617
2015-02-12 23:37:29 UpdateTip: new best=00000000000b019af595e592ad9bb0261a854305aa212345d772b268b98d443f height=219139 log2_work=60.976098 tx=861263 date=2015-02-12 23:02:19 progress=0.999584
2015-02-12 23:37:29 UpdateTip: new best=00000000000d103a6e1b9e08001116a81623186f252ac8122fc6d8be42847fce height=219138 log2_work=60.976086 tx=861262 date=2015-02-12 23:01:15 progress=0.999572
2015-02-12 23:37:29 UpdateTip: new best=000000000008b9bfbd01c47bd86640044ccae4e6625863cd8b74169bcdacaace height=219137 log2_work=60.976075 tx=861260 date=2015-02-12 23:00:39 progress=0.999564
2015-02-12 23:37:29 UpdateTip: new best=0000000000083116bd2694754d9e7dc3ba857ee257f3ac7333452410ad28c54b height=219136 log2_work=60.976063 tx=861252 date=2015-02-12 22:55:06 progress=0.999499
2015-02-12 23:37:29 UpdateTip: new best=00000000000360c45676ab36ccc9ad99b45c95864647c631cf16be00780dc83b height=219135 log2_work=60.976049 tx=861245 date=2015-02-12 22:49:23 progress=0.999431
2015-02-12 23:37:29 UpdateTip: new best=0000000000004cccb7364c69d3d414b6cb1f6617a0575424ea72b8c49b7d46f2 height=219134 log2_work=60.976035 tx=861233 date=2015-02-12 22:42:20 progress=0.999348
2015-02-12 23:37:29 UpdateTip: new best=00000000000468e0d90019da4cf28cb5325acc87ff4ca71465ad550e7af1de18 height=219133 log2_work=60.97602 tx=861230 date=2015-02-12 22:40:37 progress=0.999328
2015-02-12 23:37:29 UpdateTip: new best=00000000000bb8721f8f54181c06202e2713ab8ebfb1d7dca5210a496a71552a height=219132 log2_work=60.976007 tx=861226 date=2015-02-12 22:38:57 progress=0.999308
2015-02-12 23:37:29 UpdateTip: new best=000000000005b82d64387deea3610204e5f848850a1373bde97fe07a6792b940 height=219131 log2_work=60.975996 tx=861218 date=2015-02-12 22:35:32 progress=0.999268
2015-02-12 23:37:29 UpdateTip: new best=0000000000083ff86c6875fde187adbecfbf284246a1a0dd0a8d0ebb41c6fa36 height=219130 log2_work=60.97598 tx=861196 date=2015-02-12 22:19:47 progress=0.999081
2015-02-12 23:37:29 UpdateTip: new best=000000000005bc44498601ba4f21629444339937395bcbe0574b901f8051e3e3 height=219129 log2_work=60.975967 tx=861194 date=2015-02-12 22:19:33 progress=0.999079
2015-02-12 23:37:29 UpdateTip: new best=00000000000122b5e40e3ccdd301ac06b6a4479e236c8d70a96d59a06e5f9081 height=219128 log2_work=60.975954 tx=861193 date=2015-02-12 22:19:07 progress=0.999074
2015-02-12 23:37:30 UpdateTip: new best=0000000000073111abf8f5e972595dc97dfa8a018468025e31803404b46e5bb1 height=219127 log2_work=60.975941 tx=861190 date=2015-02-12 22:18:32 progress=0.999067
2015-02-12 23:37:30 UpdateTip: new best=000000000005814144d2ef69259c09e5df4ea94cc3b7f58a74bbca4c7594b37f height=219126 log2_work=60.975929 tx=861156 date=2015-02-12 22:16:45 progress=0.999045
2015-02-12 23:37:30 UpdateTip: new best=000000000009eee6721c9e02e9954f0292752029c3cd289a1985860fb54eb325 height=219125 log2_work=60.975917 tx=861152 date=2015-02-12 22:15:50 progress=0.999035
2015-02-12 23:37:30 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
2015-02-12 23:37:30 *** Failed to read block
Second time in less than 30 minutes, the wallet crashes with the above output in debug.log. Running 11.1.23 and mining locally with my measly 24mh. After force closing the wallet it gives me the corrupted block database detected popup and you have to rebuild the database. Not sure if this is where you report this or not so don't shoot the messenger
I get this, too.
2015-02-13 00:37:50 Using wallet wallet.dat
updated to 23
but still no wallet.dat in sight ?!
(where is that dam thing hiding ??)
I would really like to get some MNs back online but i can not
as i do not ant to drop another wallet.dat into this (as I do not even know where the other ,running one is hiding ?!
I just erased everything , starting from scratch
everything back on track
fresh fresh + clean clean
I just updated 7 nodes to .23 with no problem. But I have one that consistently fails with "Error: Failed to write block." I've deleted peers.dat and have issued a reindex, but no luck. Any other suggestions to bring this sucker back online?
EDIT: I end up getting stuck at "blocks" : 217086 every time.
EDIT2: I decided to wipe out the entire /.darkcoin directory and start fresh on the server. Seems to have done the trick, but I sure would like to know what was going on.
Half of mine had this also....a --reindex fixed it.
Whow ... was that related to these 'fake/changes" download links on BTC (what Tante mentioned) ??
This is Evans Post:
(and i am looking for the Tante one, she said something about wrong liks)
I don't think so--at least not directly. Based on what Evan said above, it sounds like someone hacked the code on their nodes which caused them to keep winning the election for the payout, that elbereth noted.
Elbereth's post shows how many DRKs those cheaters got from how many payments (times) the last 48 hours or so. It has nothing to do with what Tante said at all.
nobs wanna know too
SOYLENT GREEN IS ENFORCEMENT!!!! IT'S ENFORCEMENT!!!!!!!!!!!!!!!!!!!!
I've got a bitchin' Camaro!
Yeah, but look like the majority is not really getting paid as your image... plz check 219276-219278 as examples.
Folks, I know I should be going to bed, but something has been tugging at my memory and it just came clear. I remembered seeing a post on BCT this morning that I just interpreted as one more piece of FUD/trolling. I just went back and found it. And in view of subsequent events it seems pretty ominous in retrospect. :what:
It seems winteriscoming has posted only 4 times with one deleted. (Here they are: https://bitcointalk.org/index.php?action=profile;u=391727;sa=showPosts)
Here is this mornings post (well yesterday morning now):
[quote author=winteriscoming5 link=topic=421615.msg10439150#msg10439150 date=1423760920]
And this from Dec. 1st:
Darkcoin is NOT anonymous. Every transaction can be automatically traced with a Darkcoin de-anonymizer.
Darkcoin is prone to several cost-less DOS attacks that can destroy the whole network.
Darkcoin code was written by amateurs who do not properly understand cryptography.
please do not get confused by the fact, that I am a fresh user. In fact, I am very actively involed in crypto currencies but remaining anonymous requires certain countermeasures.
It does not require many words to describe the problem. Darkcoin's code base remembers me of my childhood where I started coding on my AMIGA. Functions that easily can be implemented in O(1) are in fact implemented in polynomial complexity (like O(n5) or something). But this is not the problem.
The biggest problem is, that while indeed being savvy the developers have not much background knowledge about crypto and (in general) the very exact details about the bitcoin/darkcoin/whatever protocol.
After excessively revieweing the code and verifying everything on an offline testbox very scary facts popped up:
Darkcoin is prone to DOS attacks, there are at least 3 (confirmed) ways you can DOS the complete network at no cost at all. You do not even lose your collateral tx.
More critical: Darkcoin has no anonymity. There is a very easy and reliable way to link inputs to outputs in every single Darksend (as well as automatic denonimating) transaction.
As I know the open source community, I will not get anything from publishing my ideas and helping to fix them. So I want to inform you, that I will shortly setup a "Darkcoin Deanonymizer" which will for every single darksend transaction be able to link incoming and outcoing transactions.
ALRIGHT, DUE TO EXCESSIVE TROLLING ACCUSATIONS I DISCLOSE ONE OF THREE DOS ATTACKS ON DARKCOIN HERE --- just for a start
Alright, I will disclose one of three DOS attacks right now.
Attack: You can destroy all darksend processes by not signing and not losing any of your collaterals ... sabotage for free basically.
Reason: When you push your collateral to the masternode it is incorrectly checked for validity.
Check: IsCollateralValid() in darksend.cpp - line 874ff
It basically checks:
are all inputs correct
are all outputs correct
however, transaction with a nLockTime in the future are also passing "IsAcceptable". So push a collateral with a locktime 10000 blocks ahead, and you will never lose it because it will not make it into any block thus easily can be replaced by another one with a higher nSequence number.
This is SERIOUS and can destroy the whole network.
3 other DOS points are there as well.
I remember this joker from back then, and if I remember correctly, everyone pretty much dismissed him as a crank. I wonder if we have seen the last of him?
PS It was about this time that child_harold started his distractions (dare I say psychological warfare), as well. It was annoying enough that even Evan felt compelled to respond. Could be just a coincidence but...
Yes, I know I may be paranoid... but that doesn't mean they aren't out to get us.
Edit: I was inclined to start a new thread, but I'm not sure if this should be wide-spread or not. I am thinking that here we have a more dedicated readership.
I wouldn't worry too much about it. It seems like someone who knows enough to muddle around in the code for defects, but just wants to take down other coins (except the ones they invested in) rather than help the cryptocurrency community as a whole.
I sure hope that is not true, because if it is, its not working!:
1 minute ago219301XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA3527.454.64286037.5%/0.0%Unpaid blockUnknown
Enforcement is disabled:
"SPORK_1_MASTERNODE_PAYMENTS_ENFORCEMENT" : 1443754538, # Fri, 02 Oct 2015 02:55:38
"Unknown" : 1444217600,
"SPORK_6_REPLAY_BLOCKS" : -1
Masternodes are ready. 88% on version .23.
Almost 50% of all MN payouts currently go to a) miners not paying out masternodes (enforcement off) b) the guy who manipulates MN payout messages to increase probability for his own MNs to get nominated
Just add more details : 219007 - 219350
a) 8.66% of Mining power : XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA
b.1) 29.24% of Mining power : miningpoolhub
b.2) 11.91% of Mining power : XwfiFDTgpVdMBiHKtLZ5Q8KzghZ8qgCfxb
b.3) 1.62% of Mining power : darkcoinoboxru
b.4) 1.08% of Mining power : ghashio
b.5) 0.54% of Mining power : xhash.net
So, at least 53.05% of Mining power is not correctly payouts to MN.
I think there are possibility that b) guys may use same special version for mining which is not the latest release of darkcoin.
Yep, http://explorer.darkcoin.io/address/Xit9gEJiUphYGggS2NCu5UaqoR4YWxmFaZ gets a _little_ bit too much payments...almost 50% :-/
And it gets them from Xemt2zeYELCkddJHvsW4x9ytqTEnkiviaH (miningpoolhub). I already removed my rigs there.
I "politely" asked miningpoolhub for futher explanation on this issue:
All Darkcoin miners who support DRK should stop mining at this pool. Could you make a big red post asking them on BCT? Thanks.
If i should throw out some "Cheating Pool Warnings" (Social Media)
somebody please ping me
(Dev Team - with Links and better suggestions)
Can someone explain me something.
If the majority of masternodes and all exchanges are updated to the latest version and enforcement is turned on what will the "bad" pools do with all the coins they mine?
My understanding is that those coins will not be accepted in the right fork (blocks mined in the "good" pools) in fact those coins do not even exist in the correct blockchain...
Let us be fair and give him some hours to respond and state his opinion. No condemnation without hearing his side of the story.
In case he does not deliver a reasonable explanation, we should remind every miner of miningpoolhub of the possibility to give the user "miningpoolhub" on bitcointalk a negative trust rating. This might be a template how to handle these things in the future. DRK cheating leads to negative PR and the cheaters should better put this into their total equation.
They abuse Darkcoin. It's not honest and I will give a negative trust rating to this guy for that.
Hm, on the one hand it's negative situation, but on the other hand system will be stronger in the future, because Evan can fix this vulnerability now and not in the far future, so I want to say "thank you" to all cheaters, because they help to make the whole system more secure.
The fact that a large pool though is gaming the system means even after this is fixed, that hash should spread to fair pools. Would love to see the DCT pool get that hash.
I hope the 2-3 days worth of payments is enough to cover the backlash from all this.