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

[hellyeahent]

fail dev is fail

[1715138462]

1715138462

[1715138462]

1715138462

[1715138462]

1715138462

[1715138462]

1715138462

[1715138462]

1715138462

[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.

[toknormal]

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

Maybe so, but if he sticks with it he'll become the worlds leading expert on hard forks 

[benthach]

FORKED! this is getting scary as we don't know what is going on right now.

[anonymousxx1503]

The price just plunged by 15 % after the wrong fork .... That is more than 5 million dollars sold in a minute ...

that's not how markets work..

[rickraw]

[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...

The short forks are just orphans. they become a short chain due to lag and then prune themselves over time. It's not a big deal and is entirely normal...

I think it is very professional / motivating to see him want things to be 100% correct and up to par.  

[georgem]

Those who panic-reverted are causing more problems on the network now than all of the bad actor/outdated nodes...

REVERT THE REVERT!

HAHA! This is dynamite comedy!

[Coolstoryteller]

Time 4 some distraction   

Lulz. That chick should of fixed her nose before she pumped up her chest.

[TsuyokuNaritai]

[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.

THIS. Nothing more needs to be said.

[AlexGR]

[20:34] <ALDRED> so i got that hash allrighty, but stuck there... its jsut because of the slow network?
[20:34] <fishyballs> this isnt the place to worry about your "investment"
[20:34] <linedash> exactly; keep the trade crap to the main chan or #darkcoin-trade please
[20:34] <weirdgod> http://explorer.darkcoin.io/chain/DarkCoin  shows 88827... i am stuck on 88815
[20:34] <ogi84> darkcoind getblockhash 88805 00000000001392f1652e9bf45cd8bc79dc60fe935277cd11538565b4a94fa85f
[20:34] <jimbit> ALDRED, i think so yes
[20:34] <yidakee> evan82 ... couldnt it be a "simple" error on the explorer? Everyone is reporting right hashes!
[20:34] <elberethzone> weirdgod> update to .2
[20:34] <yidakee> and official explorer is acting weird
[20:34] <weirdgod> oh
[20:34] <weirdgod> tnx
[20:34] <yidakee> that is all I wsww
[20:35] <yidakee> *see
[20:35] <nickiton> fishyballs, the situation seems quite confusing, but sorry
[20:35] <donho> so I guess all MN are still on 10.10.1 i guess as there are no binaries yet?
[20:35] <vercoint> I stopped my nodes until 10.10.2 binaries are up
[20:36] <_420moviez> vercoint +1
[20:36] <Henkie> New lowest point on Mintpal =(
[20:36] <flare> vertcoint +1
[20:36] <jimbit> all my nodes on the right fork.. one node is stuck on 805.. expect it to catch up
[20:36] <ALDRED> 10.10.2 is supposed to revert and disable Mn payments?
[20:36] <sipher_> jimbit: I'm also stuck there..
[20:36] <yidakee> jimbit Reboot that node!
[20:36] <yidakee> not stop/start - reboot
[20:36] <sipher_> yidakee: rebooting doesn't fix.
[20:36] <yidakee> ok.
[20:36] <_420moviez> ALDRED yes (for a short time)
[20:36] <jimbit> no reboot..  that changes my ip etc...
[20:37] <vertoe> are we forked yet?
[20:37] <yidakee> No!! Reboot within VPS, not OUTSIDE !!
[20:37] <Propulsion> no reverting
[20:37] <heduciwo> So is your decision final evan82 or will we stay on this fork?
[20:37] <yidakee> IP is the same, but flushes memory!´
[20:37] <sipher_> yidakee: REBOOTS WONT FIX IT!!
[20:37] <chaeplin> major pool is on 88827
[20:37] <Propulsion> or yes we are reverting.
[20:37] --> Minotaur (bef20c5a@gateway/web/cgi-irc/kiwiirc.com/ip.190.242.12.90) has joined this channel.
[20:37] <jimbit> that pool is on the old fork
[20:38] <chaeplin> except coinmine.pl
[20:38] <jimbit> or its own
[20:38] <chaeplin> official mininghub such explorer 88827
[20:38] --> sttroon (d02e04fa@gateway/web/cgi-irc/kiwiirc.com/ip.208.46.4.250) has joined this channel.
[20:38] <-- CryptoFan (~cryptofan@98.145.128.89) has left this server (Remote host closed the connection).
[20:39] <-- sttroon (d02e04fa@gateway/web/cgi-irc/kiwiirc.com/ip.208.46.4.250) has left this channel.
[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

[abercrombie]

women and children first!

[hellyeahent]

omg those idiots who sold at 17-18,5k sat


oh... w8. They werent ? This shit isnt working. Not 1st time

[camosoul]

[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...

[thcmakaveli]

Dark is going to hell.... 0.15 ....

[CryptoPleb]

Dont be fooled on mintpal, people taking advantage of the situation

[hartvercoint]

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

[baddw]

[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...

The short forks are just orphans. they become a short chain due to lag and then prune themselves over time. It's not a big deal and is entirely normal...

I think it is very professional / motivating to see him want things to be 100% correct and up to par.  

Agreed, and it's also good that this time A) Evan is awake for the hard fork and B) the exchanges and pool owners all seem to be on board and keeping track of things.  Last time was amateur hour, but this is a good deal better even if the hard fork didn't work as intended.

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.

+1

[Taxidermista]

I just realised the fork is going to coincide with New York waking up.
 Today is going to be epically crazy. If all goes well, RC4 will be insanity.

Fasten you seatbelts!!

It seems that nothing went well.

[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...

[MTJ151]

wow @ that dump!