Me too, very talkative error message btw - I would suggest to use a custom 500-Error page in the future!
Also: Inline HTML!? Srsly? Google app engine supports Django templates!
|
|
|
I buy at any price below 1000EUR/BTC. I can offer you 5 BTC at 999$each - interested?
|
|
|
Maybe change the wording of "Invalid Payouts to Donators" to something like "Payouts to donators (>2,50%) for invalid blocks".
|
|
|
Just better to be cautious and no need to post this stuff online forever if there is no need to! Maybe (since you rely on donations more or less) also give the opportunity to donate a coin or something from your confirmed rewards - but then please with a confirmation prompt. On the other hand it might look a bit "beggarish", if that word exists...
|
|
|
With clearcoin I can say "I offer 277€ from my side to get x Bitcoin from your side" At the beginning of the month it os not clear, how many BTC that will be.
I could pay you right now for the month until now with clearcoin, as it is trivial to calculate the income there and demand a certain sum of BTC. Advance payments for mining is (as far as I understand it) currently not possible with Clearcoin and there are no other escrow services working directly with Bitcoin.
|
|
|
"Shipped" means shipped to which country/continent?!
|
|
|
Hmm I can't login anymore. Warning: mysqli_prepare() expects parameter 1 to be mysqli, boolean given in /media/OCZ60/www.btcguild.com/database.php on line 16
Warning: mysqli_prepare() expects parameter 1 to be mysqli, boolean given in /media/OCZ60/www.btcguild.com/database.php on line 38
I also got a few quite talkative errors: Empty page, only: Warning: mysql_pconnect() [function.mysql-pconnect]: Access denied for user 'root'@'S[*snip*]' (using password: YES) in /media/OCZ60/www.btcguild.com/database.php on line 3 Failed to connect to E[*snip*] G[*snip*] database. Please try again later. and now: Warning: mysqli_connect() [function.mysqli-connect]: (28000/1045): Access denied for user 'root'@'S[*snip*]' (using password: YES) in /media/OCZ60/www.btcguild.com/database.php on line 14 Warning: mysqli_prepare() expects parameter 1 to be mysqli, boolean given in /media/OCZ60/www.btcguild.com/database.php on line 16 Warning: mysqli_prepare() expects parameter 1 to be mysqli, boolean given in /media/OCZ60/www.btcguild.com/database.php on line 38 on top of the page.
|
|
|
Tried a payout btw. a few hours ago - everything went smoothly! (so you don't just have to read bug reports all the time )
|
|
|
Lost my miners last night for some reason, not sure if it was related to the connection issues, but back up and running this AM. Me too --> Windows Update + reboot but no autologin on my machines.
|
|
|
To the outside/whole network, the hashrate that matters is ~13GH/s --> this is the rate that determines how quickly the BTCguild pool finds blocks. Inside the pool I hash with 270MH/s --> ~2% of the pool's hashrate, meaning I discover ~2% of all blocks that the pool discovers. However this is irrelevant to my income of course, as I get ~2% of any other block's income too. So the probability of me showing up in the pool statistics is my hashrate/pool hashrate The probability of the pool showing up on blockexplorer is pool hashrate/total hashrate The probability of me finding a block on my own is my hashrate/total hashrate Maybe this explains it better what I tried to say... (it looks a bit wrong in hindsight up there as well, but I'll leave it there for documentary reasons)
|
|
|
Same here...this is nuts. This pool is cool and all but I am tempted to move somewhere cause of the connection issues.
Just set up a second miner on low priority in another pool of your choice.
|
|
|
Wohoo, I even found a block! However what ppl need to understand is, that in a pool you are only competing against the pool's hash rate. So it's not the hashrate of the whole network (>1 TH/s) but the pool you're in (currently <13GH/s) that determines your block finding probability (as you can only find blocks within your pool by definition!), so it's way easier to find a block in a pool, as I would need 2% of 1TH/s to have the same chance of finding a block as in this pool currently (meaning more power than this pool combined!).
|
|
|
1 month means 1 month (jan: 31 days, feb 28/29days, march: 31 days, april 30 days, ...) Like you prefer I can just pay you the expected mined coins with no hassle. Mostly I use clearcoin for my transactions ( https://clearcoin.appspot.com/); but you can choose another one if you want Well, the problem I have with clearcoin is, that the amount has to be fixed beforehand, but difficulty will change 2-3 times a month (every 10 days lately) so I have no idea how many bitcoins to demand for 1 month of rental. I could pay 277€/30 * days until the next difficulty shift though, as this would be calculable. Currently the eta from http://blockexplorer.com/q/eta is ~79600s --> 9,2 days. 277/30*7 (as you get the first 2 days for free, right?) would be 64,63€ and I would be willing to pay 75€ straight via clearcoin to proove that I want to continue at the next difficulty too (the excess money would then be used as rebate for these next ~10 days). ...Deal?
|
|
|
The amount is put directly into confirmed rewards, and is available even if the block is later found invalid. http://www.bitcoinpool.com/ has an invalid block rate of 3,5%, so in essence you offer better conditions than bitcoin itself! Might I suggest to just have a very short wait time instead of direct payout? The system you suggest would benefit the miners more than you as the pool operator and would probably eat up your ~1% profit that transactions make up currently (or even more). At the current model a miner would be stupid or very risk loving not to pay the 2,5%, as you have a loss of ~3,5% in the form of invalid blocks anyways (didn't find statistics from the other pools on the spot...)
|
|
|
Great solution, offering "premium services" like that for a higher fee, but still keeping the choice at the "customer"! Would it pay out all of my money or only the money I earned for that 2,5% donation block? (Example: I have 100 BTC confirmed and now set my donation over 2,5%, earning me 1 BTC - do I get 101 BTC or 1 BTC directly?)
|
|
|
I bought diapers.
Congratulations... If BTC really does as well as some people think, you could have financed your kid's studies if you had kept these few BTC. If it doesn't, then you were really better off with diapers - only time will tell.
|
|
|
I would prefer to just have Bitcoins daily transferred to my BTC address that are proportional to 800MHashes/s (currently 5.11136439 BTC/day) and not mess with remote connections etc.
Also, how long is "1 month"? 30 days or 31 days?
I would be interested, however I have to do a bit of research for escrows first...
|
|
|
What I just thought about: It might be interesting to see (if possible) an estimate when your BTC will be available for payout. Something along the lines of:
Confirmed Rewards: 1.000 Unconfirmed Rewards: 1.234 Estimated Rewards: 0.987
Estimated: Unconfirmed: Confirmed: 0.987 ..............|1.000|.................|0.234|...................... 0.987
The .| stuff could be a graph where you see how many of your BTC are where in the "maturing pipeline". The numbers in there could also be done via tooltips or so, to have a fixed length of the graph.
It's not a very important feature, but might be nice for less informed people to easily see how BTC generation works (as you see immediately after a block is generated, that the current estimated amount is "travelling" over 120 steps to the confirmed area).
|
|
|
At these prices, I don't feel sorry for a landlord! I live nicely for half the price in western Europe!
|
|
|
Hehe, that's why you set up a second miner on low priority in another pool/solo! Thanks for the fast response(s), much appreciated!
|
|
|
|