Author

Topic: [DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too - page 171. (Read 1601343 times)

legendary
Activity: 1162
Merit: 1000
DiabloMiner author
Just me - or is the instant payment button not working at the moment?
Yes, I have this problem too. Maybe Tycho will clarify situation?

Probably disabled it to prevent post-mtgox bullshit.
jr. member
Activity: 56
Merit: 1
I'm also having a problem with the instant payout button and it is making my feet itchy. Please resolve this immediately.
legendary
Activity: 1218
Merit: 1019
Just me - or is the instant payment button not working at the moment?
Yes, I have this problem too. Maybe Tycho will clarify situation?
newbie
Activity: 32
Merit: 0
Just me - or is the instant payment button not working at the moment?
newbie
Activity: 34
Merit: 0
UPDATE:

  • HTTPS/SSL is supported now for improved security

how is it secure when the miner is still using insecure http to send the user and password?
You can only change any settings with the account password, which really should be different from your worker password (which is only used for accessing the API, getting work and submitting shares, so nothing bad can come of others knowing it).

thanks i didn't realize the worker could have a different passwd.  i only have one so far so it is still the same as my account passwd.  will change them both now...
member
Activity: 87
Merit: 10
What does "locking" your bitcoin address in your deepbit account do? I assume it means you simply can not change it in the future. Mining and payments still proceed as normal, correct?
newbie
Activity: 32
Merit: 0
Just want to inform the pool of unsolicited wallet change requests. If you are using a simple password (like I was, doh!) I would suggest changing it since the Mt. Gox incident. People who are smart enough to use different logins for everything should be fine. I am very glad there are email verifications of wallet address changes, luckily my email password is a lot stronger than the one I had picked for Deepbit. I'm currently changing my passwords for pretty much everything, even differently named accounts. I figured now is as good of a time as any; they have been the same for quite a while. It's just good net practice to change passwords periodically, I just fell into a rut of laziness. The last thing I need is for my bank account to be compromised; I barely have enough to get by as it is, a run on it would not be good for my livelihood.

So, I urge everyone who uses the same username for multiple things to change their passwords before it's too late.
newbie
Activity: 46
Merit: 0
why are accounts and pws needed anyway? it appears that eligius does fine without them.
full member
Activity: 373
Merit: 100
how is it secure when the miner is still using insecure http to send the user and password?
You can only change any settings with the account password, which really should be different from your worker password (which is only used for accessing the API, getting work and submitting shares, so nothing bad can come of others knowing it).

I think it could be used to connect and flood in random hash values at a high rate as a denial of service attempt [...]
Yes, and with any luck those values will be shares and up your share counter... Tongue
Seriously, though, this is not a security problem, which is what I was pointing out.

Also, why sniff worker passwords when you can just write a quick script that creates a couple of accounts with a couple of workers and use those for your flooding attack? It just doesn't change anything, and the extra overhead created by the SSL connection will put as much load on the server as a mid-size DOS attack (and cause more stales and idle miners).
There is such a thing as sub-optimisation... Wink
member
Activity: 98
Merit: 10
UPDATE:

  • HTTPS/SSL is supported now for improved security

how is it secure when the miner is still using insecure http to send the user and password?
You can only change any settings with the account password, which really should be different from your worker password (which is only used for accessing the API, getting work and submitting shares, so nothing bad can come of others knowing it).

I think it could be used to connect and flood in random hash values at a high rate as a denial of service attempt, but I am not sure that would be a preferred method of attack anyway.  It would be nice if the account login wasn't part of the worker name however.  So, deepbit could implement a system where the user enters their desired worker name [say you have a rig called "saturn" on your network with three miners and thus, you want workers for saturn1, saturn2 and saturn3] and deepbit could create the worker with a unique name that does not contain your account name [i.e. 3xZy9!Q_saturn1].  That would at least not make the accounts on the system not known as easily and carries no overhead of connection encryption.
full member
Activity: 373
Merit: 100
UPDATE:

  • HTTPS/SSL is supported now for improved security

how is it secure when the miner is still using insecure http to send the user and password?
You can only change any settings with the account password, which really should be different from your worker password (which is only used for accessing the API, getting work and submitting shares, so nothing bad can come of others knowing it).
newbie
Activity: 34
Merit: 0
UPDATE:

  • HTTPS/SSL is supported now for improved security

how is it secure when the miner is still using insecure http to send the user and password?
full member
Activity: 373
Merit: 100
If any of them were on PPS, the reward shown in the statistics would be less than the reward received, the amount of shares displayed would be the actual amount of shares submitted, though. (If this doesn't explain the discrepancy, Tycho will have to go through his logs.)
newbie
Activity: 46
Merit: 0
Are any of your workers using PPS?
i tried it a while back.
full member
Activity: 373
Merit: 100
Are any of your workers using PPS?
newbie
Activity: 46
Merit: 0
Block 131803
my share:   115   
pool share:  2965964
reward:       0.00068679 btc
mode: prop.

but when i count this:  50* (115/2965964) = 0.001938661427

and so on every block - less reward
where is the mistake??
Should be 48.5 instead of 50
right, but the result ist still way off.
0.00068679 / (48.5 * (115 / 2 965 964)) = 0.36521639
just a bit more than one third paid out.

one of mine is broken too:
Time/Link 16.0602:47:24   Foundin 0h29m   Your 15   Total 1149726   Reward 0,00012655   Hashvalue 8,18356666666667E-006   missing btc 0,0005062095   should reward 0,0006327595
just one fifth paid out. and that was just in the 30 last stats i still have, so there could be many more            
hero member
Activity: 742
Merit: 500
Does deepbit make automatic daily payments?
I need to know as I've only made instant payments in the past, but took a break, and my accumulated coins have been withdrawn to my BTC address
Yes, automatic payment is triggered after 24 hours since last payment if your balance is over the threshold.
hero member
Activity: 742
Merit: 500
Block 131803
my share:   115   
pool share:  2965964
reward:       0.00068679 btc
mode: prop.

but when i count this:  50* (115/2965964) = 0.001938661427

and so on every block - less reward
where is the mistake??
Should be 48.5 instead of 50
newbie
Activity: 40
Merit: 0
sr. member
Activity: 252
Merit: 251
Does deepbit make automatic daily payments?

I need to know as I've only made instant payments in the past, but took a break, and my accumulated coins have been withdrawn to my BTC address.
Jump to: