Booom! One of my minor altcoin targets has been completed. I have mined a block and also owned the paid masternode. I think I might pretend that I have found an exploit and claim a bounty  Evan...can I have that 1000DRK when that Shojay person who I have on ignore loses the bet please? If you don't pay me I'll tell everybody that the secret to earning DRK is to mine loads and run masternodes. |
|
|
|
Just sent out a Tweet that will make traders very happy.
Holy crap is all I can say. Something huge is about to happen. Evan, or someone, must be up to something HUGE because the chart suddenly just 'clicked' for me as I realized I have seen this pattern in DRK before elsewhere. How high will we go? Hmmm...definitely won't say.
JL
Come on, spill the beans |
|
|
|
Is it possible to correct the spelling of Alan Turing's name? |
|
|
|
I thought Flare put it best We have (at least) three user groups
- normal users
- masternode operators
- miners/pools
For the security update ALL of these are affected
- normal users use the masternode list during Darksend denomination
- masternodes operators are keen on correct masternode list due to MN payouts
- miners/pools refer to the list to randomly choose one entry for MN payout
So if you are in one of these groups it is mandatory to update, the sooner, the better for the Darkcoin network.
Hope that helps, Seriously...our comms are shocking. I regret not having enough time to help. |
|
|
|
Everybody please update to 10.14.1 especially you MN owners.
Do it! Over 50% of the masternode network is vulnerable to the exploit! Well, it is not reasonable to expect 100% compliance this soon after the exploit. I bet you it will take a couple of days before we get close to 99%. I agree but I'd like to keep the message out there thats all |
|
|
|
Everybody please update to 10.14.1 especially you MN owners.
Do it! Over 50% of the masternode network is vulnerable to the exploit! UPDATE YOUR MASTERNODES AND STOP PISSING ABOUT MAKING UP NAMES! |
|
|
|
|
Ladies and gents.
Please note that at this time, until EVERYBODY updates their masternode, we are vulnerable to this exploit.
Lets spend a bit more time talking about this!
PLEASE! EVERYBODY UPDATE!
|
|
|
|
|
To mark our coming of age (our first major exploit) I'm going to celebrate in time honoured (one month old) Stonehedge style...by mining some more. Who knows, maybe our new celebrity will get a few more payments.
|
|
|
|
From Exploit Attack Detection till to the fix in less than 3 hours. That is really good. I bet you just made the Attacker upset. He/she/it sure has hoped to gather more coins.  Well, I'm still getting more coins. All network should be updated, it isn't enough to just commit a fix. Money is not my motivation anyway. Probably will donate this to some open source project. If you felt generous maybe you could spare a few DRK to somebody who has just updated 30 of other people's masternodes while his wife throws a strop at him for spending too much time on his computer Seriously, thanks dude or dudette. You actually rock. Come on Stonehedge, my wife is so cute, she only throw brics at me because of all day in front of the screen, was a bit with her and there was an update LOL btw. thnx again for your help, I owe you a bottle of whisky  I just got a nice 1.8DRK masternode payment which cheered me up a bit |
|
|
|
From Exploit Attack Detection till to the fix in less than 3 hours. That is really good. I bet you just made the Attacker upset. He/she/it sure has hoped to gather more coins. Well, I'm still getting more coins. All network should be updated, it isn't enough to just commit a fix. Money is not my motivation anyway. Probably will donate this to some open source project. If you felt generous maybe you could spare a few DRK to somebody who has just updated 30 of other people's masternodes while his wife throws a strop at him for spending too much time on his computer Seriously, thanks dude or dudette. You actually rock. |
|
|
|
I'm glad my idea of naming releases after eminent members is well received (tied for top and I haven't even voted  ) To celebrate, I propose to have the first release in my name I think is fun to brainstorm about ideas, but naming the releases after individuals would be sectarian and uninviting to newcomers, just my opinion. If you are going down that route a better option would be to auction the release name and use it to fund development, like Android goes, KitKat, etc. I was just about to post something similar. Not a big fan of naming after community members either. Needs something more marketable to appeal to those outside of the "inner circle" of supporters. Actually, you changed my mind. I first thought naming after famous crypto people. Then I thought this should be about the community and encouraging people to join the DRK community. But I think you are right, it would not be seen as encouraging people in, but a little club. So my vote for the top one, should be changed to places that tried to ban bitcoin / crypto. As a Brit, I'd be very proud if one version could be named after Alan Turing. A giant of a man driven to suicide by the ignorance of a government. |
|
|
|
And to be honest, from what I can tell, its hardly heist of the century. Its the principle of the matter which is the concern. A proof that masternode payments can be fooled. Anyway, sounds like a quick fix.
This is what open source is all about.
Patch already compiling. https://github.com/darkcoin/darkcoin/commit/fe9fddb292a8505a8f915708d87ef27a1ddd6060How quickly this was squished & how little panic there was is super bullish for DRK. The hamburgler has so far managed to steal 36DRK. I've mined more than that today. Not supposed to be a boast...more a perspective on the financial impact of this attack. |
|
|
|
I think each person needs to decide whether you/they are investing long term or trading short term. If you are investing long term, then you cant react to every small piece of news, that is probably going to hurt you, don’t react emotionally to what you read in the forums. Assess the situation and then respond, yes we are now open source, and someone found a way to skew the masternode payments in their favor and will probably make 100 or 200 DRK out of that, the problem has a very limited scope and is not worth reacting to, is not threatening to the network at all. Evan will patch it and we move on. Only consequence a few masternodes will miss some payments while the patch is deployed, why is it such a big deal?
There is a new solution for payments already on testnet, this issue is really contained, it looks like someone will get a new PS4 out of it or something. Is that reason to dump your 100K investment? Think more before you act.
Fairly sure BagHolder010 doesn't really have a 100K investment. I am sure you are correct, I was just putting some perspective out there for lurking investors and newcomers. Please buy my order at .02 Mintpal because I am FAIRLY sure you won't. I would be happy to get my BTC's back even thou BTC prices are down. will have to go through my 40 BTC floor first. What's wrong I thought you believe in Dark being $20 then $300, wasn't that you? Dude, everybody here who has Darkcoin is loosing money when price drops BUT most of us have been through so much shit that we manage to stay calm. Once you sunk that much money in crypto, your only option is to be patient. If we still have enemies that means we must be doing something right You will get back many fold of your investment but in the long term and only if you stay calm. And to be honest, from what I can tell, its hardly heist of the century. Its the principle of the matter which is the concern. A proof that masternode payments can be fooled. Anyway, sounds like a quick fix. This is what open source is all about. |
|
|
|
This is one way to harden your code |
|
|
|
I've just poured myself a 35yo single malt and gonna sit back and watch Evan fix the fuck out of this. 48 hours after I make some large buys. Like clockwork. I'm a fucking jinx. |
|
|
|
Lets name them after cloud types.
Nimbus, Cirrus, Stratus... er...grey, fluffy, rainy... |
|
|
|
This release includes: - Spork: True masternode payment enforcement and increasing masternode rewards - Masternode Hardening, I've fixed over 10 vulnerabilities in Darksend that could have possibly caused DOS attacks - Changed the way Masternode pinging works, using a timestamp calculated from the average block timestamp instead of the local time. This should fix some cases where nodes went offline after awhile. - Added a simple list that will provide who gets paid on what blocks. - Turned back on collateral transactions - Added collateral to the queuing process (dsa and dsq protocol commands) - Improved collateral strategy: Collateral is now paid in the form of mining fees. This creates a situation where to double spend the inputs, you would need to pay the miners higher fees then 0.1DRK (the collateral fee). This makes it impossible to double spend attack our collateral system. - New command "masternode winners", shows the next 20 payees - New Darksend branding What we need to test: - If anyone gets hit with a collateral charge, please send your debug.log and wallet.dat to evan@darkcoin.io- "masternode winners" must always be in sync across the whole network. We'll need to figure out a way to test this - Make sure the reward adjustment is working - Make sure darksend is working properly - Update pools and make sure the spork goes smoothly What should we name this release? Lets name them after cloud types. Nimbus, Cirrus, Stratus... |
|
|
|
Looks like another 10 pages of DRK history has been deleted
plus one |
|
|
|
|
Nicehash were contacted several times over and they responded along the lines of "we know, but its not our problem".
You would have thought it was in their customer's best interests to communicate...
|
|
|
|
|
Show Posts
