[CLOSED] BTCMine - ZERO fee mining pool (LP, SSL, JSON API, P2SH)

[cdb000]

My last contact was [21/06/2011 13:06:01] Result: fc94ae0e rejected

[1714797960]

1714797960

[1714797960]

1714797960

[1714797960]

1714797960

[1714797960]

1714797960

[Saturn7]

Still down?  Any updates?

[Hands]

Still down here (Austin TX, 8:12am Central DST)

[dbitcoin]

Pool hosting have a problem with upstream network provider. This should be fixed within 1-2 hour (I hope).

[jwzguy]

Why is payment disabled for those of us who already locked our payment addresses?

[dbitcoin]

Why is payment disabled for those of us who already locked our payment addresses?

Because one miner lost money with locked address.
Thief login with his password, change payment address and then lock it.
There is no way for prevent such situation without additional verification by email.
I'm just wait when all active miners recheck payment addresses and update passwords.

[Hands]

Two question,
 
1) Do we have an ETA on when payments will start back up?
2) where can I find documentation on the available JSON APIs?

Thanks
Hands

[dbitcoin]

Hosting channel problem resolved.

[dbitcoin]

Two question,
 
1) Do we have an ETA on when payments will start back up?
2) where can I find documentation on the available JSON APIs?

Thanks
Hands

1) 06/22/2011
2) only examples here: http://btcmine.com/page/api/

[MaGNeT]

Two question,
 
1) Do we have an ETA on when payments will start back up?
2) where can I find documentation on the available JSON APIs?

Thanks
Hands

1) 06/22/2011
2) only examples here: http://btcmine.com/page/api/

I changed my password (although it was safe) and locked my wallet adress so I don't see any reason to stall the payments... If others are slow in changing and can't be paid yet, it's not my problem...

You can understand I want to sell the coins I have before MtGox gets online again? Blocking payment can cost me $ and I don't guess you pay the difference from the 2% you get from us...

Maybe I look a bit like an ass but I think I have a valid point here.

[dbitcoin]

I changed my password (although it was safe) and locked my wallet adress so I don't see any reason to stall the payments... If others are slow in changing and can't be paid yet, it's not my problem...
You can understand I want to sell the coins I have before MtGox gets online again? Blocking payment can cost me $ and I don't guess you pay the difference from the 2% you get from us...
Maybe I look a bit like an ass but I think I have a valid point here.

Payments for accounts with locked payment address will be enabled soon  (within several hours).
Just be patient.

[dbitcoin]

Payments will be enabled around 06/22/2011 00:00 UTC for accounts with locked payment address.
For accounts without address lock, payments will be enabled around 06/22/2011 12:00 UTC.

[Veldy]

Why is payment disabled for those of us who already locked our payment addresses?

Because one miner lost money with locked address.
Thief login with his password, change payment address and then lock it.
There is no way for prevent such situation without additional verification by email.
I'm just wait when all active miners recheck payment addresses and update passwords.

Passwords, especially important passwords are really the responsibility of the users, not you. Your only responsibility is to keep the passwords on your system secure [ideally extremely difficult to impossible to retrieve even with physical access to the hardware].  A user should, for instance, NOT use their banking password as their forum password or their pool password or their email password or their rcairplanes.com (I don't know if that is real .. probably is) password.  Many people are willing to use one common unimportant password for many locations where there is no real risk should it be discovered.  People dealing with something important like their finances should definitely know better than to use the same password elsewhere.  Also, the people working with bitcoin mining are all or nearly all pretty technically savvy and it goes without saying.  Thus, if such a person had their account breached because they didn't use a secure password and used one that was available elsewhere [say a forum or something less secure ... DSLReports was recently compromised and passwords stolen, but even if that password had been one I use now, no real damage could be done; but as it stands, that is not a problem except perhaps on some benign site I may have registered and used years ago, but no longer use and maybe is still online].  Anything with financial information on record, uses a different password than others [and I keep most of those to a minimum anyway].  You implemented https not so long ago, and people had a chance to change their password after that time [and I did just that].  You are in no way responsible for this users loss and would not be judged poorly for not covering the loss, although, no doubt, if you did cover the loss, your social capital [in respect and honor] would increase [although some might think you set a precedent for yourself that may not be in your interest].  I don't know who this user is nor the circumstances, but did you follow the block chain at all to determine where it went?  For all you know, the user logged in and changed the address himself, locked it and had it sent to the very same wallet as before.  Did you verify the web server logs to see if access to his account was made from another address than is typical [assuming his isn't dynamic such that it changes frequently which is pretty rare these days unless you are on dial-up].  I refer to the user as "him" for lack of knowledge to the contrary, but also because most techies who would deal with bitcoin mining are undoubtedly male which I doubt anybody would argue.

Long paragraph to say the obvious; I think you over reacted by locking payouts. 

You are the pool operator though and can do what you feel is best and users will do accordingly.  You have restricted their ability to trade on an exchange however and added delays between their initial plan to move funds [bitcoins or cash] to an exchange for trading and the time when such a trade can occur and in a volatile market, that can make all the difference between making or breaking the deal to trade.  Private P2P bitcoin trades are less affected obviously beyond the delay of your payouts, but whatever they would get in return for sending coins may go up or down in price (BTC) by the time they get funds.  For most, it probably isn't a big deal.  I am just pointing out the ramifications and the likelihood that you prevented nothing [of what you intended to prevent] by your action.

Personally, I don't think your lock down was much of a negative reflection upon you, but perhaps a little one, but that is my opinion and others may not share it.  I do believe that you probably didn't really think it through before putting it in place. 

Fortunately, I am not doing any imminent trading nor am I mining on your pool [although I was less than a week ago], so it has no effect on me personally, but it does leave me with the knowledge that I might lose access temporarily to my mined coins through your voluntary action when I use your pool again [which I undoubtedly will; I still think it is a great pool].

Please take this as constructive criticism and my personal opinion and nothing more than that.   It is not intended as an attack, or scolding or anything of that nature; just an objective [well, on a couple of points it is personally biased where I am clearly stating opinion] response.

[dbitcoin]

Payments enabled for all accounts.

[FreeJAC]

Wow our luck has really turned around! I can't believe what my measly 300Mh/s has been bringing in as of late. This is fun!

[Timon2010]

Yeah, it has been great.

I have one question for dbitcoin. On the "payments" page it, the last payment says "NOT SENT".
It's the first time I see it I think.

[dbitcoin]

I have one question for dbitcoin. On the "payments" page it, the last payment says "NOT SENT".
It's the first time I see it I think.

This payment just scheduled and will be processed in the next 30min.

[shivansps]

What was the pool round shares record?? we are just passing over 5M on this round.

[Jokah]

I'm running 1.7 Gh/s and I've got 0.4 btc in the last 24 hours. Surely we're currently experiencing the worst pool luck yet. -50%?   

[Veldy]

I'm running 1.7 Gh/s and I've got 0.4 btc in the last 24 hours. Surely we're currently experiencing the worst pool luck yet. -50%?   

You realize the difficulty just increased more than 50% again, right?  On a pool the size of BTCMine, the variability will be enough to have very low daily payouts and very high daily payouts.  For 24 hours after that, you can't look at the 24 hour window preceding the current time to determine your "luck", at least not without calculations and even then, with long rounds, you might have a 10 hour round that hasn't ended and you can't exactly count that in your calculations.  Daily rates have less value for a small pool; weekly rates.