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

Ozziecoin

sr. member

Activity: 448

Merit: 250

Quote from: camosoul on June 20, 2014, 12:04:13 PM

Quote from: Ozziecoin on June 20, 2014, 12:02:01 PM

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

georgem

legendary

Activity: 1484

Merit: 1007

spreadcoin.info

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

camosoul

hero member

Activity: 560

Merit: 500

www.OroCoin.co

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

Junkey

full member

Activity: 164

Merit: 100

Best panic sells of the month!

smoothdoger

full member

Activity: 210

Merit: 100

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

AlexGR

legendary

Activity: 1708

Merit: 1049

[19:58] guys.. i think everyone needs to be on the same version.. 101001 my rig with 101000 is on wrong chain
[19:58] 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 ([email protected]) has joined this channel.
[19:59] still not all my nodes are on the same fork
[19:59] <-- PayRoutes_ ([email protected]) has left this server (Ping timeout: 255 seconds).
[19:59] 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] looks like we did it?
[19:59] yeah looks like everyhting is working.
[19:59] ?
[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 ([email protected]) has joined this channel.
[20:00] can anyone else confirm its all working?
[20:01] not me..
[20:01] --> youyi (17ef0583@gateway/web/freenode/ip.23.239.5.131) has joined this channel.
[20:01] still dealing with forks moarrr_darkcoin
[20:01] --> n77b (5cecd38b@gateway/web/freenode/ip.92.236.211.139) has joined this channel.
[20:01] i am reindexing
[20:01] network is a little slow
[20:01] me too.
[20:01] 88806 here
[20:01] --> rickraw (d8d3767a@gateway/web/freenode/ip.216.211.118.122) has joined this channel.
[20:01] all my nodes are on correct block heigh and same hash 88802 - 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[20:01] --> DeathRay77 ([email protected]) has joined this channel.
[20:01] --> sdffef2 (4df9350c@gateway/web/freenode/ip.77.249.53.12) has joined this channel.
[20:02] evan82 - its looking good right?
[20:02] 88806 yidakee
[20:02] 8806 is last reported block
[20:02] is the newest
[20:02] yeah!!
[20:02] yup
[20:02] Sorry !
[20:02] 88806 !
[20:02] --> CryptoFan ([email protected]) has joined this channel.
[20:02] hash proves it Wink

[20:02] Yay!!!
[20:03] http://chainz.cryptoid.info/drk/ and http://explorer.darkcoin.io/chain/DarkCoin dont agree
[20:03] I still think its totally weird for Chainz to not show tx info, and official showing up "m" addressses
[20:03] official has always shown 'm' addresses Huh

[20:03] some MN on right fork, some not...
[20:03] enzo86 I think they agree but chainz is slower
[20:03] i got both nodes on 88807 which is ok
[20:03] so, besides some pools/idiots not updating, any other problem ?
[20:04] Showing 8807 as well. Looking great.
[20:04] 88807: 000000000015426875b0125a3d0e4f0bcea496ef77d83137aac407792b85ebb5
[20:04] 88807 here
[20:04] linux qt and 3 nodes on 88807 other node still reindexing
[20:04] 88807 000000000015426875b0125a3d0e4f0bcea496ef77d83137aac407792b85ebb5
[20:04] me too
[20:04] http://chainz.cryptoid.info and OFFICIAL AGREE on the hash of 88805
[20:04] 3 nodes on that

dotnetmin

hero member

Activity: 756

Merit: 500

Quote from: sukottosan_d on June 20, 2014, 12:03:25 PM

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

stealth923

legendary

Activity: 1036

Merit: 1000

Network looks solid to me...

abercrombie

legendary

Activity: 1159

Merit: 1001

Quote from: miningpoolhub on June 20, 2014, 12:00:58 PM

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.

camosoul

hero member

Activity: 560

Merit: 500

www.OroCoin.co

Quote from: Ozziecoin on June 20, 2014, 12:02:01 PM

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.

tungfa

legendary

Activity: 1834

Merit: 1023

Quote from: roede94105 on June 20, 2014, 12:03:00 PM

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 !!!

toknormal

legendary

Activity: 3066

Merit: 1188

Everything's perfect.

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

sukottosan_d

member

Activity: 84

Merit: 10

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

roede94105

sr. member

Activity: 294

Merit: 250

Why Mintpal blocking it now?

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

toknormal

legendary

Activity: 3066

Merit: 1188

Quote from: qwizzie on June 20, 2014, 11:59:51 AM

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

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

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

Ozziecoin

sr. member

Activity: 448

Merit: 250

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

camosoul

hero member

Activity: 560

Merit: 500

www.OroCoin.co

Quote from: abercrombie on June 20, 2014, 11:56:33 AM

Quote from: AlexGR on June 20, 2014, 11:52:00 AM

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

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

miningpoolhub

legendary

Activity: 1456

Merit: 1006

Mining Pool Hub

Quote from: GhostPlayer on June 20, 2014, 11:42:58 AM

Quote from: miningpoolhub on June 20, 2014, 11:38:43 AM

Quote from: slapper on June 20, 2014, 11:32:03 AM

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 Wink

yup. He will be taken care of after a few hours. Trust me.

Any miners on miningpoolhub, prpepare to waste your hashes soon Cheesy

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.

AlexGR

legendary

Activity: 1708

Merit: 1049

Quote from: abercrombie on June 20, 2014, 11:59:32 AM

Quote from: AlexGR on June 20, 2014, 11:52:00 AM

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

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

No idea yet

[19:55] maybe a restart ?
[19:55] 88806
[19:55] 00000000000d68171854da2437660e6aac2eca58dbf46cbe400048ea9305a95c
[19:55] too bad I dont have ops here
[19:55] can someone elaborate whats wrong ?
[19:55] if you are not helping with test , get out
[19:55] masternode 88805 - 00000000001392f1652e9bf45cd8bc79dc60fe935277cd11538565b4a94fa85f
[19:55] --> PayRoutes__ ([email protected]) has joined this channel.
[19:55] 88806: 00000000000d68171854da2437660e6aac2eca58dbf46cbe400048ea9305a95c
[19:55] p2pool seems to have mined a block
[19:55] darkcoind getblockhash 88806
[19:56] 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:56] 88806 00000000000d68171854da2437660e6aac2eca58dbf46cbe400048ea9305a95c
[19:56] crap... I think I have to update "version" : 101000 to "version" : 101001
[19:56] shit
[19:56] version 101001 darkcoind getblockhash 88806
[19:56] 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:56] 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:56] evan82 debug email sent to you
[19:57] 101000 is on wrong fork
[19:57] 101001 - 88806 - 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:57] --> Kong_ (53d987a0@gateway/web/freenode/ip.83.217.135.160) has joined this channel.
[19:57] 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:57] 88806 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2 for other nodes
[19:57] Seems to be good!!
[19:57] all good it seems
[19:57] you sure?
[19:57] im waiting for reindex
[19:57] --> whazzledazzle ([email protected]) has joined this channel.
[19:57] 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_ ([email protected]) has joined this channel.
[19:58] 00000000000cd327c630f528107c2c6d4e77f42463d295afaf7d60d1d513b6a2
[19:58] --> scottj_ (026055a4@gateway/web/freenode/ip.2.96.85.164) has joined this channel.
[19:58] guys.. i think everyone needs to be on the same version.. 101001 my rig with 101000 is on wrong chain
[19:58] 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 ([email protected]) has joined this channel.
[19:59] still not all my nodes are on the same fork
[19:59] <-- PayRoutes_ ([email protected]) has left this server (Ping timeout: 255 seconds).
[19:59] 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] looks like we did it?
[19:59] yeah looks like everyhting is working.
[19:59] ?

Bitcycle

sr. member

Activity: 420

Merit: 250

Quote from: abercrombie on June 20, 2014, 11:59:32 AM

Quote from: AlexGR on June 20, 2014, 11:52:00 AM

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

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

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

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 5139. (Read 9723733 times)