[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[hellyeahent]

Let me interject a common-sense course of action which will be ignored.

Yes, it's going outside confirmation window. But it IS fixing itself.

Reverting will only rob us of the log files needed to find the problem. Let it go for a while, find the problem, then fix it. If we revert we'll never find it...

so u havent learn anything from it ? what a waste. Such talent xd

[thcmakaveli]

This is the biggest plunge of price which I have ever seen in my life ... The problem is that I am watching how I am loosing thousand of dollars just in a minutes ...

[AlexGR]

[20:29] <evan82> But that's not acceptable, so it must be reverted

I'm losing a little faith in Evan on this... He should know better...

I think, and it may be totally inaccurate, that he's probably seen something in a debug log that makes him believe the issue may reoccur. And 15 minutes are indeed not acceptable (2.5m x 6 conf = 15m...) You don't want to have 15-20 minute fork issues. It's beyond the confirmation window.

Yes and no.

This will continue as long as bad actors can hit it. Needs time and updated clients. You're right, it's outside standard conf depth. BTC hardforked and had problems like this for WEEKS... It finally leveled out. From waht I'm seeing in my debugs, it's just a matter of time...

I'm not coder, but I'm not stupid, either... This doesn't look so bad. In fact, it looks like exactly what I would expect...

Yes, I agree it looked FAR better than the random forks last time - achieving network consensus on its own, but I have no idea if it would remain that way or if it could divert & reconverge. As an outsider if it seems to be working, I align with "if it ain't broken don't fix it". If Evan saw something that needs fixing "under the hood", then he knows better than me (and others saying "keep it"). I believe he wouldn't revert it for the lulz. He probably saw something.

Anyway: Latest

[20:39] <yidakee> I'm not a pro!! BUT OFFICIAL TIMESTAMP ON BLOCK IS RIDICULOUS !!!
[20:39] <yidakee> Official Explorer has issues NOT THE NETWORK !
[20:39] <vercoint> yidakee: dude, calm down
[20:40] <yidakee> ok, shouting, sorry...
[20:40] --> PayRoutes__ (~PayRoutes@87.68.99.93) has joined this channel.
[20:40] <linedash> yidakee: because you know better than the official dev, right
[20:40] <vercoint> people being on a fork isn't acceptable. Be it for 10 minutes only.
[20:40] <yidakee> no not at all
[20:40] <linedash> hush already and let him get on with it
[20:41] <jimbit> vercoint, btc had a fork that took 6 hours to settle out
[20:41] <jimbit> just 1 year ago
[20:41] <elberethzone> my p2pool node is on .2 and on 827 block
[20:42] <plambe> 88815
[20:42] <plambe> 00000000001ba795834733878ace2c1f83b4d56cce84fc5168fa108373e081ab
[20:42] <plambe> that's at my p2pool node
[20:42] <plambe> windows and another linux (qt) wallet show the same block
[20:42] <elberethzone>   88827 00000000000bac8750fde88a52198fd6ea814d1484ab36d2a26072eef4d12f2f
[20:42] <jimbit> 00000000001ba795834733878ace2c1f83b4d56cce84fc5168fa108373e081ab
[20:42] <jimbit>  88815
[20:42] <jimbit> 00000000001ba795834733878ace2c1f83b4d56cce84fc5168fa108373e081ab
[20:43] <vercoint> jimbit, to me what evan says means forking might happen spontanuously and would be corrected, but it might take some time. And that shouldn't happen. It wouldn't be a problem if it was just happening once after the hard fork.
[20:43] <elberethzone> will update my MNs when the binaries are available
[20:43] <vercoint> *sporadically
[20:44] --> CryptoFa_ (~cryptofan@98.145.128.89) has joined this channel.
[20:44] <-- PayRoutes_ (~PayRoutes@87.68.99.93) has left this server (Ping timeout: 272 seconds).
[20:44] <heduciwo> Evan82 is your decision final?
[20:45] <linedash> its already being pushed out
[20:45] <linedash> there's no going back now
[20:45] <vertoe> any tl;dr?
[20:45] <linedash> too early
[20:45] <linedash> still dealing w/ the problem
[20:45] <plambe> vertoe, the darkcoin is being reverted
[20:46] <stu_> should we shut doen our MNs then and wait for the new binaries?
[20:46] <ogi84> final decision is dump
[20:46] <enzo86> time to buy
[20:46] <Propulsion> Ok updated client on p2pool.
[20:46] <ALDRED> now waiting for 10.10.2 binaries, then we update all nodes asap to it, right?
[20:46] <linedash> keep that crap out of here folks; this is NOT the trade channel
[20:46] *** ogi84 has been kicked from the channel by InternetApe (ogi84).
[20:46] <Propulsion> version 91002.
[20:46] <enzo86> sorry
[20:46] <-- IAmNotDoritos (3ab3e3ac@gateway/web/freenode/ip.58.179.227.172) has left this channel.
[20:46] <Propulsion> What's the current block?
[20:47] <ALDRED> 16
[20:47] <Propulsion> for new version.
[20:47] <elberethzone>   88828 0000000000091e18054bb62ab17e5ad5702eb40fa123a987a66279fdd4b07fe4
[20:47] <jimbit> crap!
[20:47] <elberethzone> that's what I have at least..
[20:47] <Propulsion> 28? thankyou I'll check once it finishes reindexing.
[20:47] <plambe> 88816
[20:47] <plambe> 000000000012dc81bfbf821e61a0ce09ea9dd8a9a1a62522992535430c6fd62a
[20:47] <ALDRED> 88816 000000000012dc81bfbf821e61a0ce09ea9dd8a9a1a62522992535430c6fd62a
[20:47] <Propulsion> Did you do git clone on the latest darkcoind?
[20:48] <plambe> not yet
[20:48] <Propulsion> Well your on the wrong chain then.
[20:48] <vertoe> reverted means we are going to shut down payments again?
[20:48] <plambe> doing it now then

[rickraw]

This is the biggest plunge of price which I have ever seen in my life ... The problem is that I am watching how I am loosing thousand of dollars just in a minutes ...

That's crypto, don't act like it can't happen at anytime.

[georgem]

This is the biggest plunge of price which I have ever seen in my life ... The problem is that I am watching how I am loosing thousand of dollars just in a minutes ...

Well, how does the saying go:

You win some, you lose some.
Easy come, easy go.

Or my favorite:

After the gathering comes the scattering.

[2dogs]

we should have known better!! It happened once. It would happen again. Fuck

Yup, traders know the saying:
If you can't stand the heat, get out of the kitchen.....

[eltito]

FYI - this was just sent out to the mailing list.  More information to follow.


Evan Duffield
10:43 AM (7 minutes ago)

to bcc: me
The Darkcoin network has been experiencing some issues with
intermittent blockchain forks. These forks are not as serious as the
last update, being they appear to fix themselves after 15-30 minutes.
However, we must revert to no masternode payments until we're sure
we've discovered the problem.

Please recompile if you're running a daemon, otherwise binaries will
be made available soon.

https://github.com/darkcoinproject/darkcoin

Thanks,

The Darkcoin Team

[camosoul]

Yes, I agree it looked FAR better than the random forks last time - achieving network consensus on its own, but I have no idea if it would remain that way or if it could divert & reconverge. As an outsider if it seems to be working, I align with "if it ain't broken don't fix it". If Evan saw something that needs fixing "under the hood", then he knows better than me (and others saying "keep it"). I believe he wouldn't revert it for the lulz. He probably saw something.

It didn't just look far better, it gave use useful feedback and proved it was self-fixing...

Yes, I'm seeing it spontaneously do this over and over. That's my point... Log Files! Nail it instead of throw it away...

[CryptoPleb]

Is this something that will be fixed in a matter of hours, days or weeks?

[binkshurts]

was evan that dumped ? since he knew firsthand?

[hellyeahent]

Ok im out. Going to buy BC, They at least have solid dev team who can write few lines of code

[KryptoFoo]

I have capitulated.

[toknormal]

Ok im out. Going to buy BC, They at least have solid dev team who can write few lines of code

Good f*ckng riddance.

They deserve parasites like you  

[camosoul]

Let me interject a common-sense course of action which will be ignored.

Yes, it's going outside confirmation window. But it IS fixing itself.

Reverting will only rob us of the log files needed to find the problem. Let it go for a while, find the problem, then fix it. If we revert we'll never find it...

+1

It's sad... This is EXACTLY what I expected to happen... And it's really NOT a problem... Could nail this without reverting.

[AlexGR]

[20:48] <elberethzone> Propulsion> git pull
[20:48] <Propulsion> yes.
[20:48] <plambe> vertoe, I think so, that's how I understand it
[20:48] <Propulsion> thats what i meant
[20:48] <Propulsion> git pull
[20:48] <donho> payments are off
[20:48] <elberethzone>
[20:48] <vertoe> why?
[20:48] <plambe> forks
[20:48] <vertoe> so what?
[20:48] <donho> no forks
[20:48] <elberethzone> mini-forks
[20:48] <vertoe> all my machines are on the correct fork
[20:49] <Propulsion> Showing current block 88830.
[20:49] <Propulsion> after update.
[20:49] <Propulsion> 00000000000b630ff3ddf3db73093b85e38b9bb93e9874883cedb39f2173af7c
[20:49] <elberethzone> 88830 hash=00000000000b630ff3ddf3db73093b85e38b9bb93e9874883cedb39f2173af7c
[20:49] <Propulsion> yep same.
[20:49] <donho> no forks just some clients lagging behind
[20:50] <donho> evan wants to fix it
[20:50] <elberethzone> donho> I had at least 2 forks
[20:50] <Propulsion> donho he's fixing it with the patch.
[20:50] <linedash> we did have some forks
[20:50] <dstorm> 88831 000000000004e5644016c4f305f423b322b316c24237dd8088e331a73a0cdaa9
[20:50] <donho> no he's reverting it
[20:50] <donho> then he will fix it
[20:50] <Propulsion> Reverting. Doing a git clone. new block height.
[20:50] <elberethzone> the statement from evan82 was right, it was fixing itself in 15-20min timeframe
[20:50] <elberethzone> but he thinks that's not acceptable, that's his call
[20:50] <linedash> yes; but as he also said - it's unacceptable for a blockchain.
[20:51] <elberethzone> 88832 hash=00000000000ef942f1e9b1db42d3728bdde011f8c76c025f3391a7b265654dba
[20:51] <linedash> anyway; lets try not to clutter up this w/ speculation and whatnot
[20:51] <donho> The Darkcoin network has been experiencing some issues with
[20:51] <donho> intermittent blockchain forks. These forks are not as serious as the
[20:51] <donho> last update, being they appear to fix themselves after 15-30 minutes.
[20:51] <dstorm> 88832 00000000000ef942f1e9b1db42d3728bdde011f8c76c025f3391a7b265654dba
[20:51] <donho> However, we must revert to no masternode payments until we're sure
[20:51] <donho> we've discovered the problem.
[20:51] <donho> Please recompile if you're running a daemon, otherwise binaries will
[20:51] <donho> be made available soon.
[20:51] <donho> email just got out
[20:51] <InternetApe> Windows binaries are on the darkcoin.io site.
[20:51] <Propulsion> Ok p2pool is back up.
[20:52] <Propulsion> excellent Ape.
[20:52] <elberethzone> thanks InternetApe
[20:52] <yidakee> wget on linux ?
[20:52] <InternetApe> I will check if the verbage has been updated, but the files are the reverted.
[20:52] <sipher_> InternetApe: I can just checkout the git source?
[20:52] <donho> linux 10.10.2 binaries online?
[20:52] <stu_> stopeed mns, awaiting binaries
[20:53] <-- Stealth95 (Stealth95@27-32-51-54.static.tpgi.com.au) has left this server.
[20:54] <-- heduciwo (~androirc@p4FE8BE66.dip0.t-ipconnect.de) has left this channel ("Trennungsnachricht").
[20:55] <elberethzone> also stopped mines while waiting for the 10.10.2 binary
[20:55] <-- Light_ (~light@szlak.net.imsmultimedia.eu) has left this server.
[20:55] <-- nj4752 (~AndChat65@2600:1014:b103:db23:9e72:731a:af29:b2c7) has left this server (Quit: Bye).
[20:56] --> Light_ (~light@szlak.net.imsmultimedia.eu) has joined this channel.
[20:56] <Propulsion> ok reverting the mpos pool now.
[20:56] <linedash> wrong version showing on website
[20:56] <linedash> for new win binary

[binkshurts]

oh my goodness.

people want to sell and dump it, the problem is the buy support is so weak. there's hardly any btc that want to buy it atm

[rickraw]

New binaries available on Darkcoin site.  Just downloaded and its .02 version.



https://www.darkcoin.io/getstarted.html

Code:

"version" : 101002,
"protocolversion" : 70018,

[MasterMined710]

Ok im out. Going to buy BC, They at least have solid dev team who can write few lines of code

You were never in

[alwa1]

The buy support will came when everything is fine /maybe its fine even now/

[battbot]

Fool me once, shame on you.  Fool me twice, shame on me.

...