u5sos
Member
Offline
Activity: 108
Merit: 10
|
|
June 03, 2014, 09:28:49 PM |
|
very promising coin
|
|
|
|
Vz
Member
Offline
Activity: 64
Merit: 10
|
|
June 03, 2014, 09:33:17 PM Last edit: June 03, 2014, 09:43:56 PM by Vz |
|
We made it! *what the hell) Blocks start to go sooo fast.. I collect nothing for that two hours)..
|
|
|
|
cryptoyeah
Member
Offline
Activity: 84
Merit: 10
|
|
June 03, 2014, 10:35:33 PM |
|
formulacoin, hitmancoin, gtacoin, dukenukemcoin, tom&jerrycoin, cs1.6coin, wolfensteincoin, princecoin, nfscoin.... we are the champions! we are the gamblers!
|
|
|
|
merlin0113
Newbie
Offline
Activity: 60
Merit: 0
|
|
June 04, 2014, 12:21:32 AM |
|
|
|
|
|
sparkster
|
|
June 04, 2014, 01:15:20 AM |
|
It's over.
|
|
|
|
|
e1ghtSpace
Legendary
Offline
Activity: 1526
Merit: 1001
Crypto since 2014
|
|
June 04, 2014, 04:07:56 AM |
|
It seems that the bots are now dominating.
Is there actually bots?
|
|
|
|
e1ghtSpace
Legendary
Offline
Activity: 1526
Merit: 1001
Crypto since 2014
|
|
June 04, 2014, 04:09:03 AM |
|
I smell a dump on c-cex.
|
|
|
|
psychocoin
|
|
June 04, 2014, 06:07:23 AM |
|
I don't think there are bots at work. If there were, there would be block solve times of under 10 seconds, because a bot doesn't need to actually drive the path it calculates, it only needs to figure out the move sequence and then send it to the network.
|
|
|
|
|
Jacqul
|
|
June 04, 2014, 07:03:24 AM |
|
Hmmm. Block found in <5 secs = bot But I suspect that it is more likely a problem with the timing blockexplorer? If you actually look at the replays, it doesn't look like bot. For example 14001. And also one of the ones you listed I think I got.
|
|
|
|
psychocoin
|
|
June 04, 2014, 07:13:33 AM |
|
There is not a chance in hell that 14002 which took 4 seconds to solve but is a 21/22 seconds long map was driven by a human at 6x increased speed. Let's be real here.
And the link to 14001 is only there so you see how short 14002 was, not saying that 14001 must have been botted. Sure, the bot could get some unlucky bruteforce streaks and not get anything for a minute or so and a human may get luckier in that time. But overall - the picture is clear here.
|
|
|
|
Jacqul
|
|
June 04, 2014, 07:30:31 AM |
|
There is not a chance in hell that 14002 which took 4 seconds to solve but is a 21/22 seconds long map was driven by a human at 6x increased speed. Let's be real here.
And the link to 14001 is only there so you see how short 14002 was, not saying that 14001 must have been botted. Sure, the bot could get some unlucky bruteforce streaks and not get anything for a minute or so and a human may get luckier in that time. But overall - the picture is clear here.
14416 I think happened in less than 3 seconds so I now agree with you.
|
|
|
|
WilliamLie2 (OP)
|
|
June 04, 2014, 07:37:40 AM |
|
There is not a chance in hell that 14002 which took 4 seconds to solve but is a 21/22 seconds long map was driven by a human at 6x increased speed. Let's be real here.
And the link to 14001 is only there so you see how short 14002 was, not saying that 14001 must have been botted. Sure, the bot could get some unlucky bruteforce streaks and not get anything for a minute or so and a human may get luckier in that time. But overall - the picture is clear here.
14416 I think happened in less than 3 seconds so I now agree with you. I really wasn't expecting this to happen so fast. Oh well. Times in blocks are not precise. You can just set your system time to several minutes in past and you will be able to generate block in negative amount of time. You can even find such blocks in block explorer, where next block was generated before previous, at least according to their times. In fact, it just means that these times can not be fully trusted.
|
|
|
|
Jacqul
|
|
June 04, 2014, 07:41:25 AM |
|
There is not a chance in hell that 14002 which took 4 seconds to solve but is a 21/22 seconds long map was driven by a human at 6x increased speed. Let's be real here.
And the link to 14001 is only there so you see how short 14002 was, not saying that 14001 must have been botted. Sure, the bot could get some unlucky bruteforce streaks and not get anything for a minute or so and a human may get luckier in that time. But overall - the picture is clear here.
14416 I think happened in less than 3 seconds so I now agree with you. I really wasn't expecting this to happen so fast. Oh well. Times in blocks are not precise. You can just set your system time to several minutes in past and you will be able to generate block in negative time. You can even find such blocks in block explorer, where next block was generated before previous, at least according to their times. In fact, it just means that these times can not be fully trusted. Shhh WilliamLie2, I'm about to buy a shitload of MOTO on C-Cex!
|
|
|
|
|
psychocoin
|
|
June 04, 2014, 07:51:12 AM |
|
Yes, I said that before I actually checked enough blocks to see myself.
|
|
|
|
|
Jacqul
|
|
June 04, 2014, 08:00:46 AM |
|
Actually there is an hour difference isn't there? jumps from 20h to 21h and back. Thanks for your explanation by the way WilliamLie.
|
|
|
|
WilliamLie2 (OP)
|
|
June 04, 2014, 08:07:08 AM |
|
Actually there is an hour difference isn't there? jumps from 20h to 21h and back. Thanks for your explanation by the way WilliamLie. Yes, actually it is just block 7872 that has wrong time. You can find similar blocks for Bitcoin as well.
|
|
|
|
|