Pages:
Author

Topic: [250GH/s] BitClockers.com Merged/No Invalids/Pure PPS/DDoS-Resistant/Live Stats - page 3. (Read 75796 times)

donator
Activity: 2058
Merit: 1007
Poor impulse control.
I suppose it could be ABCProxy then.
Id still like to see the block id's clipse has been mining at his pool, but I guess thats for another thread.

Could be ABC but I still doubt it. I honestly do not think it's real work being done.

How would the pool profit from that? Use it explain block lengths maybe?
donator
Activity: 532
Merit: 501
We have cookies
More interesting stuff when you just glance over the block history. Blocks are now linked to blockexplorer, I guess that proves they are legit. Or are they? The times dont match the ones in blockexporer, I mean they are not even close. Its not a timezone issue either  with a constant number of hours difference and perhaps a few minutes fluctuation, its like there is no correlation whatsoever.  Only the day usually matches.
I wonder why some pools still don't use block HASH instead of block height for blockexplorer links.
hero member
Activity: 518
Merit: 500
I suppose it could be ABCProxy then.
Id still like to see the block id's clipse has been mining at his pool, but I guess thats for another thread.
hero member
Activity: 518
Merit: 500
Quote
Where I mine with my farm is none of your business, I bet that hurts. I will give you a small hint, my farm have multiple workers on bitclockers, now sniff them out lassi.

Im not interested in your private farm Clipse. And you would lose the bet Smiley.
Im interested in the pool you claim to operate and the blocks it isnt publishing.  
hero member
Activity: 504
Merit: 502
Ah, clipse, there is only ONE worker hidden on bitclockers and you just happened to know the answer. Coincidence of course.

Moreover, there is not a single other worker hopping bitclockers atm that has even the hashrate you claim to have yourself (what was it, 50GH?), so either we should believe you are not hopping bitclockers at all, not even with your private farm,  or you are the hidden user.
Which is it?

Thats extremely convenient that the hidden_by_user's isnt on now, cause I initially saw a couple other users displayed as hidden_by_user and the 1969 date thats when I first checked how they got such a strange date.

Where I mine with my farm is none of your business, I bet that hurts. I will give you a small hint, my farm have multiple workers on bitclockers, now sniff them out lassi.

Oh to answer your silly question, as soon as you can show me your Badge that displays , "Every person needs to answer my stupid questions" I will respond to your stupid questions.
hero member
Activity: 518
Merit: 500
Ah, clipse, there is only ONE worker hidden on bitclockers and you just happened to know the answer. Coincidence of course.

Moreover, there is not a single other worker hopping bitclockers atm that has even the hashrate you claim to have yourself (what was it, 50GH?), so either we should believe you are not hopping bitclockers at all, not even with your private farm,  or you are the hidden user.
Which is it?
hero member
Activity: 504
Merit: 502
If you set your worker on hide then you get the date 1969, not everything is a conspiracy hehe

Ah, gotcha. One mystery solved.
BTW, nice hashrate your "private farm" has clipse. Thats what, ~3-400GH? And Im sure they are all yours Wink.

Cute, I explain the mystery of the date that you couldnt figure out by just looking into it for 1 second rather than spewing conspiracy after conspiracy and you immediately point it to me lmao.

But I do enjoy reading your posts, its amusing since there is a couple every day and perfect for lunch break Tongue
hero member
Activity: 518
Merit: 500
If you set your worker on hide then you get the date 1969, not everything is a conspiracy hehe

Ah, gotcha. One mystery solved.
BTW, nice hashrate your "private farm" has clipse. Thats what, ~3-400GH? And Im sure they are all yours Wink.
donator
Activity: 2058
Merit: 1007
Poor impulse control.

How did he manage to register in december 31, 1969?


OK, good point. But since 0 seconds in unixtime is (1970,1,1) wouldn't that be a more likely null date? This looks more like a hack tag.

Still, it certainly does smell like unwashed gymclothes, and what you and Goat mention seems like the Occams razor explanation. It would be easy for the pool to come clean if not.

It is a great way for the pool to make cash though. Make a bunch of accounts and hop your own prop pool. Make it impossible for other miners to submit shares at the start of a round.

If you set your worker on hide then you get the date 1969, not everything is a conspiracy hehe

Talking from experience, Clipse? Wink
hero member
Activity: 504
Merit: 502

How did he manage to register in december 31, 1969?


OK, good point. But since 0 seconds in unixtime is (1970,1,1) wouldn't that be a more likely null date? This looks more like a hack tag.

Still, it certainly does smell like unwashed gymclothes, and what you and Goat mention seems like the Occams razor explanation. It would be easy for the pool to come clean if not.

It is a great way for the pool to make cash though. Make a bunch of accounts and hop your own prop pool. Make it impossible for other miners to submit shares at the start of a round.

If you set your worker on hide then you get the date 1969, not everything is a conspiracy hehe
donator
Activity: 2058
Merit: 1007
Poor impulse control.
By the way, notice anything odd about the round shares on 25th March? Coincidence? Any other pool I'd say 'yes'. At bitclockers I start to wonder how they coud be profiting from it. This is the price of publishing fake stats and not being transparent.
donator
Activity: 2058
Merit: 1007
Poor impulse control.

How did he manage to register in december 31, 1969?


OK, good point. But since 0 seconds in unixtime is (1970,1,1) wouldn't that be a more likely null date? This looks more like a hack tag.

Still, it certainly does smell like unwashed gymclothes, and what you and Goat mention seems like the Occams razor explanation. It would be easy for the pool to come clean if not.

It is a great way for the pool to make cash though. Make a bunch of accounts and hop your own prop pool. Make it impossible for other miners to submit shares at the start of a round.
hero member
Activity: 518
Merit: 500
Maybe. But more likely a proxy pool. It's getting harder to hop pools now, and 120% at bitlockers is better than nothing.

How did he manage to register in december 31, 1969?
That date is no coincidence btw, for those that dont know, unixtime is a way to format date and time thats calculated as seconds since January 1st 1970. IOW, this particular worker has an empty or "null" creation date. Probably an oversight by the pool op when he made it.
donator
Activity: 2058
Merit: 1007
Poor impulse control.
Maybe. But more likely a proxy pool. It's getting harder to hop pools now, and 120% at bitlockers is better than nothing.
hero member
Activity: 518
Merit: 500
"Hidden by user" is back. The worker created in unixtime=0. Check this out:



He has supposedly mined 60500 shares out of a total of 78000 this round.


Hypothesis: this is a fabricated worker whos purpose is to artifically inflate share count at the beginning of a round. IOW, bitclockers are hopping themselves.

Good plan: blame the hoppers, but reek in the profits yourself! No wonder they are hesitant to switch to a fair payout system.
rjk
sr. member
Activity: 448
Merit: 250
1ngldh
on top of that, my payout seems wonky again in the past few days.

did they mess with the stats again?

I also have problem with bitclockers near two days now. I dirty hopper so maybe that is problem ?

Maybe time to remove bitclocker from hopping config ? This thread make very fishy smell about bitclocker admin and I no like fishy smell. Remind me of prostitute Oksana I once meet in Kiev.
Very well said, sir. Also, Grin I don't like fishy smells either.
newbie
Activity: 45
Merit: 0
on top of that, my payout seems wonky again in the past few days.

did they mess with the stats again?

I also have problem with bitclockers near two days now. I dirty hopper so maybe that is problem ?

Maybe time to remove bitclocker from hopping config ? This thread make very fishy smell about bitclocker admin and I no like fishy smell. Remind me of prostitute Oksana I once meet in Kiev.
legendary
Activity: 1764
Merit: 1006
on top of that, my payout seems wonky again in the past few days.

did they mess with the stats again?
hero member
Activity: 518
Merit: 500
Interesting stuff:



Note the "hidden_by_user", who somehow created his worker in 1969, probably before Satoshi was even born.
During other blocks, that same user sometimes had more hashrate than the entire pool combined, I assumed it to be goat or clipse though I never understood how they could change the registration date without hacking the site. I guess it must be something registered by the poolop.

THen, and hour later, same round:



Now he actually is hidden?

More interesting stuff when you just glance over the block history. Blocks are now linked to blockexplorer, I guess that proves they are legit. Or are they? The times dont match the ones in blockexporer, I mean they are not even close. Its not a timezone issue either  with a constant number of hours difference and perhaps a few minutes fluctuation, its like there is no correlation whatsoever.  Only the day usually matches. Still ahm, stretching the length truth?

Some of the blocks are even in the wrong order. Look at blockid 570 (1722286) which was listed before blocks 571 and 572 (172345). I suppose typos can happen, if you manually invent your blocks.

I can guess the response though. " We dont support pool hopping ".
 Roll Eyes
donator
Activity: 2058
Merit: 1007
Poor impulse control.
you guys keep avoiding answering the real question being asked about stolen hashes.  the bitcoin community is too smart to be duped like this Smiley
And yet the pools hashrate remains. Who are you kidding, anyway?

Sad, that. As long as miners think they're getting paid properly, they'll ignore anything to the contrary and stay. It's just like miners at proportional pools that were just sticking their heads in the sand last year.
Pages:
Jump to: