Seems very odd though we are essentially stuck at $5. It's nice to see some stability, but it's kind of weird considering difficulty has gone up close to 50% this year. BTC is not responding to supply and demand curves...lol. Although maybe we have reached an equilibrium in the speculator market.
As a miner I'd like to see the coin follow economic fundamentals more closely.
Difficulty gone up 50% while the price stays stable got you confused? The hash rate should double every 18 months assuming a constant price due to moores law. https://en.wikipedia.org/wiki/Moore%27s_lawThat, plus difficulty does not change the supply one bit. Not only does difficulty not change supply (at least not in a material way), supply has very little to do with the value of bitcoins. Daily volume on Mt.Gox is much higher than the number of coins created each day through mining. |
|
|
|
I'm pretty sure the bitcoin watch chart is accurate, but it's because I [believe] they're using the 24 hour chart from blockchain.info . BTC Guild had a -massive- surge of luck in the last 12 hours [after a day of bad luck]. It's just the nature of mining and luck. Tycho's charts are less jumpy, due to using a 2016 block window [roughly 2 weeks], which make them a much more accurate number if you're trying to compare reported speed of pools to their block find %. Actually I recommend that site for another reason: Blockchaininfo is trying to guess block origin from possible broadcasting source IP address and blockorigin.pfoe.be is using real data. Yes, I forgot to mention that reason as well. Blockchain.info has been getting more accurate, though blockorigin.pfoe.be doesn't make any assumptions when assigning blocks to pools which is certainly preferred to 'best guess'. |
|
|
|
I'm looking at the pie @ bitcoin watch and it looks wierd...
BTC guild with pool speed of 1,591.79 Gh/sec is taking 15% of the pie.
Deepbit with pool speed of 3,198.49 Gh/sec is taking 18% of the pie.
Unknown is 37% of the pie. Use this. http://blockorigin.pfoe.be/chart.phpI'm pretty sure the bitcoin watch chart is accurate, but it's because I [believe] they're using the 24 hour chart from blockchain.info . BTC Guild had a -massive- surge of luck in the last 12 hours [after a day of bad luck]. It's just the nature of mining and luck. Tycho's charts are less jumpy, due to using a 2016 block window [roughly 2 weeks], which make them a much more accurate number if you're trying to compare reported speed of pools to their block find %. |
|
|
|
Bug fix: When a user who has been inactive for a long time attempts to connect, it will restore their account if it was previously pruned for being inactive. The process of pruning inactive users does not affect rewards in any way, so everything will be waiting for you upon return if you did not cash out.
Please define what qualifies as being 'inactive'? Like... a couple months? a week? a long holiday weekend? etc -- Smoov Only users who haven't logged in since October should have been marked inactive. The process of being marked inactive doesn't actually mean much. It's simply copying their stats to a different table so that queries which require a full table scan on the users don't look at the inactive users and their workers. I did it manually in January, because we had over 50,000 registered users, but close to 30,000 which hadn't logged in since August 2011 or earlier due to the bubble popping. |
|
|
|
|
Bug fix: When a user who has been inactive for a long time attempts to connect, it will restore their account if it was previously pruned for being inactive. The process of pruning inactive users does not affect rewards in any way, so everything will be waiting for you upon return if you did not cash out.
|
|
|
|
This thread is a copy of our primary thread in Mining -> Pools, so that newbie users can ask questions if they run into any problems with our pool. BTC Guild - https://www.btcguild.com
Advantages- Pure PPS - We pay a fixed rate per share, period. There is no buffer, there is no limit based on good/bad luck. If your share is valid, your account is credited for the value of that share almost instantly.
- Merged Mining - Earn Namecoins and Bitcoins at the same time without any reduction in your BTC earnings.
- Long-polling support, reducing the number of stale shares if your miner supports it.
- SSL security - Our website forces all connections to be carried out through HTTPS.
- Automatic Payouts - Receive payouts automatically when they hit a certain threshold (full BTCs only).
- Full precision payouts - Get all 8 decimals of your balance transferred when you request a manual payout.
- On-demand payouts - Request your balance be paid to your wallet at any time by clicking the Request Payout button on the My Account page (minimum 0.1).
- No invalid blocks - PPS Guild is Pure PPS. You get paid a fixed rate per valid share. If a block is later invalid/orphaned, your earnings aren't affected.
BTC Guild is a Pure Pay-per-Share pool. This means that every valid share you submit is always worth a fixed amount, based on the current bitcoin difficulty. Each share is worth (1 / difficulty) * 47.5. It is multiplied by 47.5 instead of 50 because we charge a 5% fee for Pure PPS. This is because in a Pure PPS model, you assume no risk, and the only variance you will have is your luck on finding shares. We assume all the risk of block finding variance, and will purchase additional BTC to meet our liabilities if we have not found enough blocks to make payouts. To point your miner at the pool, you can use the following (examples for poclbm and Diablo): poclbm.exe -d1 --host=mine2.btcguild.com --port=8332 --user=[username]_[workername] --pass=[anything]DiabloMiner-Linux.sh -b -o mine3.btcguild.com -r 8332 -u [username]_[workername]Detailed instructions for GUI Miner, cgminer, and ZTex's FPGA miner are available on our website. Mining is enabled on Port 80 if you use mine2.btcguild.com or mine3.btcguild.com!European and Asian users may prefer to connect to our Germany server: de.btcguild.comVisit our IRC channel on FreeNode.net to chat with other members or the pool operator: #btcguild |
|
|
|
Please be advised, since you can do anonymous PPS on the same server port, if you enter incorrect authenticated credentials the system will treat your shares as anonymous PPS shares, so be sure you are using the correct worker name.
Just a suggestion, because it WILL happen that somebody screws up their credentials: Add a length check on the username field so that it will reject the miner credentials if they're not the length of a wallet address, assuming it doesn't match regular mining credentials. |
|
|
|
The whole point of it denying you entry (with an increasing timer) is to prevent somebody guessing common passwords and eventually finding the right one for your account. Allowing someone to bypass the lockout once they enter the correct password would completely defeat the point of the lockout.
If you've tried to send me an email, I have not received one describing anything remotely related to what you've stated in this thread.
EDIT: If you're trying to login via TOR, it is entirely possible that somebody else using the same exit node was trying to get into someone's account. The lockout is IP based. You're allowed one failure in 24 hours with no penalty. Then the penalty is 1 second. Then 2, 4, 8, etc. The lockout is exponential based on failed attempts from your IP in the past 6 hours. The maximum lockout being 1 hour between attempts (3600 seconds).
The email I sent went to " webmaster@btcguild.com". And I did get a response, just checked. My account apparently got "pruned" or deactivated due to my inactivity (I was out of the country for 9 months). I understood the point of it increasing the timeouts. It makes sense from a security standpoint. But after I saw that the time keep going up, I waited more than an hour and it still didn't work. But it was made clear to me that the problem was my inactivity... and trying again (just now) a new message appears. I did not see this one erlier today. The message reads: "Your account was pruned from the active users database due to inactivity. An automated restoration of your account is being run, please try logging in again in a few seconds." Which concurred with the email from the webmaster. I tried again...and it let me log in. So, my problem was resolved. However, I do recommend the website be reprogrammed to warn people that login is failing due to a pruned inactive accounts. Seeing what happened, I will not use this as an excuse to move to another pool. I'll stick with it for now.  Thanks for your thoughts and help. Ah, that was you. Your email was quite different from this post in terms of what the exact problem was. There WAS a bug fix performed this afternoon related to pruned accounts that will attempt to automatically restore inactivate accounts when they attempt to login, so it looks like that kicked in and your account became reactivated. Sorry for the inconvenience and the time to resolve it. |
|
|
|
|
The whole point of it denying you entry (with an increasing timer) is to prevent somebody guessing common passwords and eventually finding the right one for your account. Allowing someone to bypass the lockout once they enter the correct password would completely defeat the point of the lockout.
If you've tried to send me an email, I have not received one describing anything remotely related to what you've stated in this thread.
EDIT: If you're trying to login via TOR, it is entirely possible that somebody else using the same exit node was trying to get into someone's account. The lockout is IP based. You're allowed one failure in 24 hours with no penalty. Then the penalty is 1 second. Then 2, 4, 8, etc. The lockout is exponential based on failed attempts from your IP in the past 6 hours. The maximum lockout being 1 hour between attempts (3600 seconds).
|
|
|
|
Is there an issue with the 24 hour earnings counter ? Mine seems to be dropping buy my total worker speed has been pretty much constant for the last 2-3 days Thanks, keep up the good work The 24 hour earnings calculation uses the current PPS rate multiplied by your share submissions in the last 24 hours. This causes the calculation to be inaccurate for the first 24 hours after the difficulty change. If your speed stays constant, your average 24 hour earnings will be the new value as a result of the difficulty increase. |
|
|
|
I have managed to get my hands on iMine botnet thingy and all it does is connects to a specified pool.
Of course I will not be using it as a botnet as advertised.
Are you able to determine who's code it is based on? Ufasoft, cgminer, etc? Can you tell what language it is written in? I can't comment on iMine, but I can tell you that so far every known botnet that has tried mining on BTC Guild has been Ufasoft. Sometimes they'll mask the UserAgent though. |
|
|
|
|
FPGAs are a decent investment for someone in my situation. Central Valley California stuck with PG&E. Top tier electricity rates are at 0.34/kWh (it was actually 0.40 last summer!). During summer, I will be locked into top tier pricing just because I have the nerve to set my AC to 75-78F instead of 85F+.
At those prices, GPU mining is a loss for me, even if you don't include the extra power offset the additional heat.
|
|
|
|
|
Two minor updates along with the API bugfix:
1: Earnings History now puts the most recent difficulty at the top. This matches the Payout History which has most recent on top.
2: API page has reduced the timer between refreshing to 55 seconds instead of 60 seconds. This should keep any external timers/cron scripts from accidentally getting a "you've checked in the last 60 seconds" error due to just fractions of a second differences between polling the API.
|
|
|
|
|
Requested last Tuesday, arrived Monday. I'm hoping now that their holiday is over we'll see them catch up a bit better. A week delay isn't too bad in my case, though there is still the 2 day wait for it to hit my bank account after it gets to Dwolla.
|
|
|
|
I found a minor bug when working on the latest revision of my Cacti templates for BTC Guild. It appears that the Reset Stats buttons on the Worker Summary (NMC) don't actually reset the API counters (for NMC) when pressed. They do reset the counters shown on the web interface, just not the API. The Worker Summary (BTC) Reset Stats buttons work as expected.
Thank you for the bug report! It has been fixed. |
|
|
|
if I rent a VPS to mine the litecoin, will the VPS service provider ban my account? It's using KVM.
Probably. Any real VPS provider will have an acceptable use policy, and you can be sure abusing CPU resources is a part of it. |
|
|
|
|
Fun read whether its real or not. I would side more towards it being real for the simple fact that it basically states that while Bitcoin is a potential problem for laundering/illegal activities, it's not seen as a significant problem or threat. I'd be much more likely to call fake/troll if it was using hyperbole and an aggressive stance towards the "looming Bitcoin threat".
|
|
|
|
|
I haven't used bitcoins specifically for too many purchases, other than some time cards for MMORPGs a few months ago. Mostly I just cash them out in mid-sized chunks to supplement my monthly bills.
|
|
|
|
I'm on US3, and for the past few days my miners have been failing over to my backup pool almost every time that work gets pushed out for a new block. I caught it the latest time it happened, and I was disconnected from the server for up to a minute and a half. Any suggestions?
Are you using cgminer? If so, have you updated to 2.3.6 or 2.4? 2.3.6 pushed a fix to solve problems that were sometimes showing up when a long poll message was received, which caused exactly the behavior you're describing. |
|
|
|
Everybody want to see pics of your Serverbedroom.  C'mon  You know, when things break I sometimes wish I had a giant server rack in my house hosting all this. Then I remember how damn loud servers are . Right now I have a server living room, but that's all for the VPS offerings. 6 servers waiting to be shipped out in the next month =). |
|
|
|
|
Show Posts
