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

[Bitcycle]

[19:49] <evan82> There's definitely something wrong. There are many chains again
[19:49] <evan82> I'm going to patch and turn it off...

For those of us without IRC, is evan gonna let it run or is it going to be rolled back?

Just wondering how cheap DRK might get... 

If he has to roll it back... very, very cheap.

[AlexGR]

[19:49] <evan82> There's definitely something wrong. There are many chains again
[19:49] <evan82> I'm going to patch and turn it off...

For those of us without IRC, is evan gonna let it run or is it going to be rolled back?

Just wondering how cheap DRK might get... 

No idea yet

[19:55] <enzo86> maybe a restart ?
[19:55] <plambe> 88806
[19:55] <plambe> 00000000000d68171854da2437660e6aac2eca58dbf46cbe400048ea9305a95c
[19:55] <tifozi> too bad I dont have ops here
[19:55] <ffs|> can someone elaborate whats wrong ?
[19:55] <tifozi> if you are not helping with test , get out
[19:55] <yidakee> masternode 88805 - 00000000001392f1652e9bf45cd8bc79dc60fe935277cd11538565b4a94fa85f
[19:55] --> PayRoutes__ (~PayRoutes@87.68.99.93) has joined this channel.
[19:55] <dstorm> 88806: 00000000000d68171854da2437660e6aac2eca58dbf46cbe400048ea9305a95c
[19:55] <plambe> p2pool seems to have mined a block
[19:55] <donho>  darkcoind getblockhash 88806
[19:56] <donho> 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:56] <elberethzone> 88806 00000000000d68171854da2437660e6aac2eca58dbf46cbe400048ea9305a95c
[19:56] <jimbit> crap...  I think I have to update "version" : 101000 to "version" : 101001
[19:56] <elberethzone> shit
[19:56] <jimbit> version 101001  darkcoind getblockhash 88806
[19:56] <jimbit> 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:56] <weirdgod> 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:56] <enzo86> evan82 debug email sent to you
[19:57] <jimbit> 101000 is on wrong fork
[19:57] <yidakee> 101001 - 88806 - 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:57] --> Kong_ (53d987a0@gateway/web/freenode/ip.83.217.135.160) has joined this channel.
[19:57] <Propulsion> 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:57] <elberethzone> 88806 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2 for other nodes
[19:57] <yidakee> Seems to be good!!
[19:57] <Propulsion> all good it seems
[19:57] <moarrr_darkcoin> you sure?
[19:57] <moarrr_darkcoin> im waiting for reindex
[19:57] --> whazzledazzle (~whazzleda@CPE-65-26-197-197.wi.res.rr.com) has joined this channel.
[19:57] <yidakee> local wallet got stuck on 87xxx  - re-indexed and got up good
[19:58] --> SomeGuy (45f72fba@gateway/web/freenode/ip.69.247.47.186) has joined this channel.
[19:58] --> stu_ (~stu@host86-154-220-147.range86-154.btcentralplus.com) has joined this channel.
[19:58] <donho> 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:58] --> scottj_ (026055a4@gateway/web/freenode/ip.2.96.85.164) has joined this channel.
[19:58] <jimbit> guys.. i think everyone needs to be on the same version..  101001  my rig with 101000 is on wrong chain
[19:58] <elberethzone> 101001 and 91001 here
[19:58] --> bitcoinmercenary (329f17df@gateway/web/cgi-irc/kiwiirc.com/ip.50.159.23.223) has joined this channel.
[19:59] --> vp1777 (~Android@199.119.233.181) has joined this channel.
[19:59] <elberethzone> still not all my nodes are on the same fork
[19:59] <-- PayRoutes_ (~PayRoutes@87.68.99.93) has left this server (Ping timeout: 255 seconds).
[19:59] <elberethzone> https://elbzo.net/masternodes.html
[19:59] <-- ALDRED (58668a62@gateway/web/freenode/ip.88.102.138.98) has left this server (Ping timeout: 246 seconds).
[19:59] <vertoe> looks like we did it?
[19:59] <Propulsion> yeah looks like everyhting is working.
[19:59] <elberethzone> ?

[miningpoolhub]

Dont worry.

miningpoolhub is a troll. Know why he never confims that he has updated clients? Never participates here but to post that he got forked yup. He will be taken care of after a few hours. Trust me.

Any miners on miningpoolhub, prpepare to waste your hashes soon

Sorry again.

Actually I found the fork issue from the last update, posted fork issue, and sent PM to evan to fix.
I tried to alarm and it was fixed quite quickly. At that time, 3 major pools were mining on different blockchain, and some pool mined on wrong block chain for more than 6 hours.

I just wanted to get things better quickly, fast fix. Sorry.

TOTALLY IRRESPONSIBLE !!

 THIS DAY HAS BEEN WARNED FOR A MONTH NOW !!

TOTALLY UNEXCUSABLE !!

YOU ARE INCOMPETENT!!

Please, it was not an update problem. I'm not a lazy pool operator.
I updated before and even tested on testnet. You can find my posts on darkcointalk for testing compatibility with NOMP. Chaeplin replied and I replied that it works well too. You can find my comments even on github.

You know what happened at previous release. I was monitoring if fork happens again.
Yes, this is my most concern about this update.

Orphan blocks are determined quite quickly at normal case, but it didn't appear that quick as previous.
I think it jumped block chain but auto synced a bit later which is added from this release.

I have seen many other coin blocks determined as orphan since I'm running many coin pools, and it didn't take long time like this.

I was suspicious about the phenomenon and I asked about it with this.
"fork occurred?"

Did I act like a troll or told everybody to dump? No. Sorry that it seemed like that.

It was just a mistake and I was so sensitive about it. I even opened new tab to write PM to evan.

Sorry about my mistake again.

[camosoul]

[19:49] <evan82> There's definitely something wrong. There are many chains again
[19:49] <evan82> I'm going to patch and turn it off...

uh oh...

Actually, too soon to say. Bad chains were expected due to so many failing to update. They could get pruned, but that takes time. This is much bigger network that testnet... On testnet it was fast to prune becasue they only pushed one or two bad clients at a time.., realnet has a lot more...

[Ozziecoin]

Looks fine to me. I think some clients on wrong chain due to versioning?

[toknormal]

okay.. who is ready to analyze what we are seeing on mintpal ?

I think that's known as the "adrenalin crossover"  

You can have as many heart attacks as you want cos there's enough adrenalin flying around to resuscitate you instantly

[roede94105]

Why Mintpal blocking it now?

We should give it time to be sure, not shut it off now

[sukottosan_d]

Lol, wow, so many people dumped for no reason.
That's a lesson in how people act. -> remember this for next time.

[toknormal]

Everything's perfect.

Evan just needed some cheap DRK's to pay his new QA guy cos he's so expensive.

[tungfa]

Why Mintpal blocking it now?

We should give it time to be sure, not shut it off now

where is mint pal blocking
prices are still going up and down !!!

[camosoul]

Looks fine to me. I think some clients on wrong chain due to versioning?

Wrong client == wrong chain.

This was the whole point of telling people this shit for a fucking month!

It'll prune out eventually, but there si a LOT of bad clients on the realnet. It's going to be slower to weed them out. Chain will be messy for a while. This is expected.

[abercrombie]

Please, it was not an update problem. I'm not a lazy pool operator.
I updated before and even tested on testnet. You can find my posts on darkcointalk for testing compatibility with NOMP. Chaeplin replied and I replied that it works well too. You can find my comments even on github.

You know what happened at previous release. I was monitoring if fork happens again.
Yes, this is my most concern about this update.

Orphan blocks are determined quite quickly at normal case, but it didn't appear that quick as previous.
I think it jumped block chain but auto synced a bit later which is added from this release.

I have seen many other coin blocks determined as orphan since I'm running many coin pools, and it didn't take long time like this.

I was suspicious about the phenomenon and I asked about it with this.
"fork occurred?"

Did I act like a troll or told everybody to dump? No. Sorry that it seemed like that.

It was just a mistake and I was so sensitive about it. I even opened new tab to write PM to evan.

Sorry about my mistake again.

Thanks miningpoolhub, appreciate your input.

Unlike others here that only want to hear positive news, I want to hear the real news.

[stealth923]

Network looks solid to me...

[dotnetmin]

Lol, wow, so many people dumped for no reason.
That's a lesson in how people act. -> remember this for next time.

My wallet is still synch on block 88807. last time i forcked it wasn't synch

[AlexGR]

[19:58] <jimbit> guys.. i think everyone needs to be on the same version..  101001  my rig with 101000 is on wrong chain
[19:58] <elberethzone> 101001 and 91001 here
[19:58] --> bitcoinmercenary (329f17df@gateway/web/cgi-irc/kiwiirc.com/ip.50.159.23.223) has joined this channel.
[19:59] --> vp1777 (~Android@199.119.233.181) has joined this channel.
[19:59] <elberethzone> still not all my nodes are on the same fork
[19:59] <-- PayRoutes_ (~PayRoutes@87.68.99.93) has left this server (Ping timeout: 255 seconds).
[19:59] <elberethzone> https://elbzo.net/masternodes.html
[19:59] <-- ALDRED (58668a62@gateway/web/freenode/ip.88.102.138.98) has left this server (Ping timeout: 246 seconds).
[19:59] <vertoe> looks like we did it?
[19:59] <Propulsion> yeah looks like everyhting is working.
[19:59] <elberethzone> ?
[20:00] <-- Minotaur (bef20c5a@gateway/web/cgi-irc/kiwiirc.com/ip.190.242.12.90) has left this server (Quit: http://www.kiwiirc.com/ - A hand crafted IRC client).
[20:00] --> flare (258a3ae6@gateway/web/freenode/ip.37.138.58.230) has joined this channel.
[20:00] --> qqr (~kktr_@91.224.47.20) has joined this channel.
[20:00] <moarrr_darkcoin> can anyone else confirm its all working?
[20:01] <elberethzone> not me..
[20:01] --> youyi (17ef0583@gateway/web/freenode/ip.23.239.5.131) has joined this channel.
[20:01] <jimbit> still dealing with forks moarrr_darkcoin
[20:01] --> n77b (5cecd38b@gateway/web/freenode/ip.92.236.211.139) has joined this channel.
[20:01] <enzo86> i am reindexing
[20:01] <donho> network is a little slow
[20:01] <jimbit> me too.
[20:01] <tombtc> 88806 here
[20:01] --> rickraw (d8d3767a@gateway/web/freenode/ip.216.211.118.122) has joined this channel.
[20:01] <yidakee> all my nodes are on correct block heigh and same hash 88802 - 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[20:01] --> DeathRay77 (~quassel@cpc5-haye18-2-0-cust342.haye.cable.virginm.net) has joined this channel.
[20:01] --> sdffef2 (4df9350c@gateway/web/freenode/ip.77.249.53.12) has joined this channel.
[20:02] <yidakee> evan82 - its looking good right?
[20:02] <donho> 88806 yidakee
[20:02] <Propulsion> 8806 is last reported block
[20:02] <donho> is the newest
[20:02] <yidakee> yeah!!
[20:02] <plambe> yup
[20:02] <yidakee> Sorry !
[20:02] <yidakee> 88806 !
[20:02] --> CryptoFan (~cryptofan@98.145.128.89) has joined this channel.
[20:02] <yidakee> hash proves it
[20:02] <AndyVorpal> Yay!!!
[20:03] <enzo86> http://chainz.cryptoid.info/drk/ and http://explorer.darkcoin.io/chain/DarkCoin dont agree
[20:03] <yidakee> I still think its totally weird for Chainz to not show tx info, and official showing up "m" addressses
[20:03] <stu_> official has always shown 'm' addresses
[20:03] <jimbit> some MN on right fork, some not...
[20:03] <donho> enzo86 I think they agree but chainz is slower
[20:03] <qqr> i got both nodes on 88807 which is ok
[20:03] <ffs|> so, besides some pools/idiots not updating, any other problem ?
[20:04] <Propulsion> Showing 8807 as well. Looking great.
[20:04] <dstorm> 88807: 000000000015426875b0125a3d0e4f0bcea496ef77d83137aac407792b85ebb5
[20:04] <tombtc> 88807 here
[20:04] <stu_> linux qt and 3 nodes on 88807 other node still reindexing
[20:04] <elberethzone> 88807 000000000015426875b0125a3d0e4f0bcea496ef77d83137aac407792b85ebb5
[20:04] <aaxx1503> me too
[20:04] <donho> http://chainz.cryptoid.info and OFFICIAL AGREE on the hash of 88805
[20:04] <elberethzone> 3 nodes on that

[smoothdoger]

lol look at them all tripping over each other to get back in on cryptsy

[Junkey]

Best panic sells of the month!

[camosoul]

All of my clients/daemons are 10.10.1 and I see absolutely NO forking going on. Running perfectly.

[georgem]

Yeah, people sure overreact.... but that's how deer caught in the headlights are:

[Ozziecoin]

Looks fine to me. I think some clients on wrong chain due to versioning?

Wrong client == wrong chain.

This was the whole point of telling people this shit for a fucking month!

It'll prune out eventually, but there si a LOT of bad clients on the realnet. It's going to be slower to weed them out. Chain will be messy for a while. This is expected.

27% of network on obsolete version: http://drk.poolhash.org/subver.html