Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 111. (Read 1601412 times)
October 19, 2011, 11:00:46 AM
You can use the ipconfig flushdns command, do not need to reboot anything....I hope
October 19, 2011, 10:14:04 AM
We have some problems at this moment and I'm working on this.
Hashrate display is temporarily disabled for debugging purposes, sorry (that's why we aren't on bitcoinwatch).
You may need to flush DNS cache.
sht, cant connect with any miners... Hashrate display is temporarily disabled for debugging purposes, sorry (that's why we aren't on bitcoinwatch).
You may need to flush DNS cache.
Please do fix this soon in a manner that doesnt require us to reboot everything...
October 19, 2011, 09:43:01 AM
We have some problems at this moment and I'm working on this.
Hashrate display is temporarily disabled for debugging purposes, sorry (that's why we aren't on bitcoinwatch).
You may need to flush DNS cache.
Hashrate display is temporarily disabled for debugging purposes, sorry (that's why we aren't on bitcoinwatch).
You may need to flush DNS cache.
October 19, 2011, 09:39:32 AM
I can access the site but the pool hash rate as displayed is Pool rate: 0 Gh/s
October 19, 2011, 09:33:31 AM
what is happening to deepbit at the moment ? It is not accessible and it disappeared from bitcoinwatch.com. Anybody any news?
October 19, 2011, 12:48:41 AM
Lol where the why such crippling 3-4hr blocks xD :"D
Could it be because deepbit went from 5+ TH to under 3 TH ?
October 19, 2011, 12:36:44 AM
Lol where the why such crippling 3-4hr blocks xD :"D
October 17, 2011, 01:15:09 PM
Hey are we having bad luck... Or is this like... Pool Hopping gone wild... Deepbit's doing a kinda bad job at grabbing blocks lately...
Was wondering if during the DDoSing something was changed to stop the DDoSing and inadvertably allowed poolhoppers to get into deepbit(Afaik im stupid)
No, this is not related to poolhopping in any way.Was wondering if during the DDoSing something was changed to stop the DDoSing and inadvertably allowed poolhoppers to get into deepbit(Afaik im stupid)
Average shares per block: 1668282 (+13.6%)
Average in last 24 hours: 2039335 (+38.9%)
It happens even to the biggest of them at times. Variance is a biach!
October 17, 2011, 12:43:07 PM
Hey are we having bad luck... Or is this like... Pool Hopping gone wild... Deepbit's doing a kinda bad job at grabbing blocks lately...
Was wondering if during the DDoSing something was changed to stop the DDoSing and inadvertably allowed poolhoppers to get into deepbit(Afaik im stupid)
No, this is not related to poolhopping in any way. Was wondering if during the DDoSing something was changed to stop the DDoSing and inadvertably allowed poolhoppers to get into deepbit(Afaik im stupid)
October 17, 2011, 09:00:56 AM
1-. Only hopping to help.
2-. no login nor horsepower stealth... we wrote it for US (4 friends) and put it online for other 3 months ago. if you dont like, dont use it. i only wanted to help.
3-. I dont use windows, so dont know about the ie9 problem. i tried to code html as standard as i know.
4-. i am spanish and tried to write in english as well as i can. can you please write the correct sintax of the sentence?
You forgot:
5-. Copper doesn't rust (it oxidizes)
... And when iron rusts... It turns to iron oxide.
So there's that. Hair splitting, we're both doing it.
Hey are we having bad luck... Or is this like... Pool Hopping gone wild... Deepbit's doing a kinda bad job at grabbing blocks lately...
Was wondering if during the DDoSing something was changed to stop the DDoSing and inadvertably allowed poolhoppers to get into deepbit(Afaik im stupid)
October 17, 2011, 01:46:58 AM
so tired of changing passwords
In this day and age there is absolutly ZERO reason to use any part of the same e-mail, username, password, etc for more than one site. Something that takes 2 minutes to do will save hours of headache and butt hurt in the long run.....
Sure it will take 2 minutes to have a new password. But the problem of remembering them forever or using some password remembering softwares to store password is time consuming.
Still, anyone give me good password managing software names please.
No. Really, they're good. 1Password on the Macintosh should be quite good, too.
Thanks
October 17, 2011, 12:43:42 AM
so tired of changing passwords
In this day and age there is absolutly ZERO reason to use any part of the same e-mail, username, password, etc for more than one site. Something that takes 2 minutes to do will save hours of headache and butt hurt in the long run.....
Sure it will take 2 minutes to have a new password. But the problem of remembering them forever or using some password remembering softwares to store password is time consuming.
Still, anyone give me good password managing software names please.
No. Really, they're good. 1Password on the Macintosh should be quite good, too.
October 16, 2011, 11:49:03 PM
so tired of changing passwords
In this day and age there is absolutly ZERO reason to use any part of the same e-mail, username, password, etc for more than one site. Something that takes 2 minutes to do will save hours of headache and butt hurt in the long run.....
Sure it will take 2 minutes to have a new password. But the problem of remembering them forever or using some password remembering softwares to store password is time consuming.
Still, anyone give me good password managing software names please.
October 16, 2011, 10:17:28 PM
Tycho... Just wanted your opinion.
If there were some consensus within the developer community to add RSA 4096 or some other such hash function to create a paired key that would belong to a specific address for SENDING BTC, would you get behind it?
Basically attach an encrypted key to address for the purpose of validating transactions. That way thiefs would have to gain access to both a wallet and a key file in order to actually transact a theft.
I figure the added security would make it a lot more enticing for average people to get involved with BTC because it would resolve some of the concerns pertaining to ongoing theft via worms and such.
It is a hell of a lot harder to find two encrypted files in separate locations than one.
I feel that the system itself should be integrated with a security method to avoid illegitimate transactions.
If there were some consensus within the developer community to add RSA 4096 or some other such hash function to create a paired key that would belong to a specific address for SENDING BTC, would you get behind it?
Basically attach an encrypted key to address for the purpose of validating transactions. That way thiefs would have to gain access to both a wallet and a key file in order to actually transact a theft.
I figure the added security would make it a lot more enticing for average people to get involved with BTC because it would resolve some of the concerns pertaining to ongoing theft via worms and such.
It is a hell of a lot harder to find two encrypted files in separate locations than one.
I feel that the system itself should be integrated with a security method to avoid illegitimate transactions.
October 16, 2011, 10:11:26 PM
Totally. I use 4 different password families based upon the trustworthiness of the organization. If someone pulled my password off here, they could definitely get into my old adult friend finder account though.
Get to talk to some bots.
It'd probably be pretty cool.
Get to talk to some bots.
It'd probably be pretty cool.
October 16, 2011, 09:37:11 PM
so tired of changing passwords
In this day and age there is absolutly ZERO reason to use any part of the same e-mail, username, password, etc for more than one site. Something that takes 2 minutes to do will save hours of headache and butt hurt in the long run.....
October 16, 2011, 09:26:29 PM
so tired of changing passwords
October 16, 2011, 02:10:58 PM
WARNING
Today someone tried some userlist against this pool. It may be the user/password database stolen from bitcointalk forum or somewhere else.
While most usernames didn't match, tens of users have same password in the pool and in this list. PLEASE consider taking appropriate actions immediately:
1. If you used same password in this pool and somewhere else - change your pool's password.
2. If you used same password in this pool and in your e-mail - change both (this is not secure).
3. If you used same password somewhere else and you have bitcoins on your pool balance - please use permanent bitcoin address lock function at the pool's advanced settings page (this can't be undone). You have to be the real owner of this address' private keys (wallet.dat) and keep a backup copy of it.
Today someone tried some userlist against this pool. It may be the user/password database stolen from bitcointalk forum or somewhere else.
While most usernames didn't match, tens of users have same password in the pool and in this list. PLEASE consider taking appropriate actions immediately:
1. If you used same password in this pool and somewhere else - change your pool's password.
2. If you used same password in this pool and in your e-mail - change both (this is not secure).
3. If you used same password somewhere else and you have bitcoins on your pool balance - please use permanent bitcoin address lock function at the pool's advanced settings page (this can't be undone). You have to be the real owner of this address' private keys (wallet.dat) and keep a backup copy of it.
Folks should probably change their password regardless.
What's the maximum Password length Deepbit accepts?
Also maybe you should consider allowing more complex characters too.
Thanks,
Sam
October 16, 2011, 11:02:35 AM
WARNING
Today someone tried some userlist against this pool. It may be the user/password database stolen from bitcointalk forum or somewhere else.
While most usernames didn't match, tens of users have same password in the pool and in this list. PLEASE consider taking appropriate actions immediately:
1. If you used same password in this pool and somewhere else - change your pool's password.
2. If you used same password in this pool and in your e-mail - change both (this is not secure).
3. If you used same password somewhere else and you have bitcoins on your pool balance - please use permanent bitcoin address lock function at the pool's advanced settings page (this can't be undone). You have to be the real owner of this address' private keys (wallet.dat) and keep a backup copy of it.
Today someone tried some userlist against this pool. It may be the user/password database stolen from bitcointalk forum or somewhere else.
While most usernames didn't match, tens of users have same password in the pool and in this list. PLEASE consider taking appropriate actions immediately:
1. If you used same password in this pool and somewhere else - change your pool's password.
2. If you used same password in this pool and in your e-mail - change both (this is not secure).
3. If you used same password somewhere else and you have bitcoins on your pool balance - please use permanent bitcoin address lock function at the pool's advanced settings page (this can't be undone). You have to be the real owner of this address' private keys (wallet.dat) and keep a backup copy of it.
I suggest you should sent an e-mail to all users in the userlist about this.
October 16, 2011, 10:35:15 AM
WARNING
Today someone tried some userlist against this pool. It may be the user/password database stolen from bitcointalk forum or somewhere else.
While most usernames didn't match, tens of users have same password in the pool and in this list. PLEASE consider taking appropriate actions immediately:
1. If you used same password in this pool and somewhere else - change your pool's password.
2. If you used same password in this pool and in your e-mail - change both (this is not secure).
3. If you used same password somewhere else and you have bitcoins on your pool balance - please use permanent bitcoin address lock function at the pool's advanced settings page (this can't be undone). You have to be the real owner of this address' private keys (wallet.dat) and keep a backup copy of it.
Today someone tried some userlist against this pool. It may be the user/password database stolen from bitcointalk forum or somewhere else.
While most usernames didn't match, tens of users have same password in the pool and in this list. PLEASE consider taking appropriate actions immediately:
1. If you used same password in this pool and somewhere else - change your pool's password.
2. If you used same password in this pool and in your e-mail - change both (this is not secure).
3. If you used same password somewhere else and you have bitcoins on your pool balance - please use permanent bitcoin address lock function at the pool's advanced settings page (this can't be undone). You have to be the real owner of this address' private keys (wallet.dat) and keep a backup copy of it.
Jump to: