[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too

[TheShoura]

All of my miners just went down with "Problems communicating with bitcoin RPC"

and then switched to "deepbit is currently unavailable"




edit: its back already...server reboot?

[1594866931]

1594866931

[1594866931]

1594866931

[maxcorrads]

The statistics on the right of the account page are delayed or are in real time?

Block history is delayed by one hour and shows only the reward from Proportional mode.

Thank you
Edit: And why there is a delay? Sorry for my stupid question!

[new_in_this]

I'm not sure is this OT to this thread, but after deepbit went down i pointed to j2 and then back to deepbit my miner is not getting full power?

Tried rebooting, restarting and re-installing. Still no full speed. Full speed is ~280Mhash/s  and so far i get ~140Mhash/s?


EDIT: guiminer is what i use

[[Tycho]]

The statistics on the right of the account page are delayed or are in real time?

Block history is delayed by one hour and shows only the reward from Proportional mode.

Edit: And why there is a delay? Sorry for my stupid question! :D

It's to make pool-hopping more difficult.

[matteumayo]

SO....

I have a strange situation.

In 8 hours, at ~305 m/hash, I only (barely) got 0.1 BTC.

I also want to mention that with 305 m/hash I get 0.06 % average share whereas my friend who has 350 m/hash gets up to 0.16%.

What gives?

[DiabloD3]

It seems LP has been shut off on Deepbit. Why?

[mjsbuddha]

it seems we have our first invalid block...

[VastLite]

But we got paid, just as [Tycho] Promised

[d3athrow]

But we got paid, just as [Tycho] Promised

paid a bit whole .04 btc
woo!

[JoeTheTech]

Pool rate: 600 Gh/s

And yet another record is set. Deepbit is getting very deep 

Grats [Tycho]. You are a grand pool master. Thank you.


Cheers.

[Veldy]

Pool rate: 600 Gh/s

And yet another record is set. Deepbit is getting very deep 

Grats [Tycho]. You are a grand pool master. Thank you.


Cheers.

Approaching 50% again Tycho?  Personally, I would rather Bitcoin go down because it is unsound than to have it go down because somebody attacked it and got rich.  Time to tweet.  Deepbit, stop your expansion now, please!

[VTCarter]

I think I recall tycho making a comment sometime back that he had some 'brakes' set up to prevent going over 50%. Which you're probably right would be a Bad Thing (tm) , the going over 50% that is. This is not what I'd call an attack though and use of that word seems a bit unfair. What it will do is drive the difficulty up which is Bitcoins basis for stability. Remember initially Satoshi had 100% of the mining , on his own pc. My advice to others concerned about one pool getting to large is this, open others! In the bitcoin economy competition is a good thing !





Hate, me love me, just want to toss away a couple coins? :1KNZSyAYKAZzFZC2pBWt3D4jGu5uJZCWSr  

[luffy]

Tycho, in order to avoid all these hysterical voices 
please implement a second pool! 

[new_in_this]

I'm not sure is this OT to this thread, but after deepbit went down i pointed to j2 and then back to deepbit my miner is not getting full power?

Tried rebooting, restarting and re-installing. Still no full speed. Full speed is ~280Mhash/s  and so far i get ~140Mhash/s?


EDIT: guiminer is what i use

Few hours ago it went back to normal/full speed, not sure what happened?

[Veldy]

Tycho, in order to avoid all these hysterical voices 
please implement a second pool! 

Same man and same code = same pool for all intents and purposes.  If a cracker can break one, then both can be cracked ... then hacked. 

[Veldy]

This is not what I'd call an attack though and use of that word seems a bit unfair.

I never called it an attack.  I am not sure if you were referring to me or not.  What I said is that we are setup for one with deepbit that large.  It has already been shown, that in the short term, if somebody knocks out Slush [why was his pool down again? ... I didn't see a post on it, but I may not have been subscribed to his thread] most flee to deepbit.  Last time it resulted in, I think an additional 20% hashing power [and it has been largely recovered either by new mining power or attrition from other pools].  The amount of money to be made by such an attack is growing rapidly.  Further, the more hashing power at the attackers disposal means the more that can double spent because the more that can be "rechained" for lack of a better term before anybody catches on. 

I bet there are cracker/hacker groups out there that would do it for just a few thousand USD and that means with the means to do it, the ends are more likely.  The fact that this can be done now [since I have little doubt somebody could take down Slush with ease at this point], the less trust I have in the bitcoin I am sorry to say.  That is why I am asking people to do what Tycho won't, and goto or form other pools so that this can't happen.  I don't want deepbit disappear, I simply want it to be "community aware" if you will.

Sorry Tycho.  I feel bad that you have lost sight of what you once had sight of [or at least appeared to].

[mroth7684]

All aboard the 1Thash/s train! toot toot!

I say if a system can be brought down by something as simple as going over 50% then it was a poorly designed system and never should have been invented in the first place. Might as well test the theories on the 50% rumors now rather than later.

[zimpixa]

Tycho, could u add some kind if information to account page, which would show time of last submitted share? My rig are on other floor and since Im changing sometimes clocks I'd like to know if rig is down faster than 30 minutes(the noise is terrible there, so I cant stand being ther more than 2 minutes...).

[mroth7684]

Tycho, could u add some kind if information to account page, which would show time of last submitted share? My rig are on other floor and since Im changing sometimes clocks I'd like to know if rig is down faster than 30 minutes(the noise is terrible there, so I cant stand being ther more than 2 minutes...).

It sounds like you're referring to the Failure Detection Threshold. If you setup a separate worker for each rig and set the Failure Detection Threshold as low as 1 minute you will know if a rig is down because the worker will turn red if it hasn't submitted a share in the last minute. This doesn't necessarily mean it's down though... I have mine set to 10 minutes and sometimes it will turn red as if its down, but it's not, just took longer to submit a share.

[zimpixa]

Thanks, thats exacly what I was looking for, but apparently missed it.