website unreachable
ssl_error_bad_mac_read
Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 390. (Read 903150 times)
July 24, 2012, 08:42:40 AM
July 22, 2012, 05:25:42 PM
All the servers are back online, and payouts are working again. I removed the automatic payouts that never completed, so they will execute again in 35 minutes.
July 22, 2012, 03:22:29 PM
Some problems with the node BTC Guild is running on. Things are starting to come back online after about 30 minutes of downtime. de and mine2 are online, mine1 should be shortly.
UPDATE: Servers are back online.
UPDATE: Servers are back online.
July 20, 2012, 01:15:13 PM
my bitcoin client seems to be stuck on "catching up" it's not doing anything.
edit: Corrupted client... or blockchain on my end.... fixing..... Sorry aboot that
edit: Corrupted client... or blockchain on my end.... fixing..... Sorry aboot that
July 20, 2012, 10:25:53 AM
any issues with payments? My last request has not been put through since last night... I have never waited anymore than a couple minutes in the past.
Your payout was confirmed in a block 4 minutes after requested, and has 96 confirmations already, I sent you a PM with the txid.
July 20, 2012, 08:19:52 AM
any issues with payments? My last request has not been put through since last night... I have never waited anymore than a couple minutes in the past.
July 19, 2012, 03:38:16 PM
any news on savings wallet and other features to come?
Current To-Do List (in order of importance):
1) New pool software being developped from scratch to allow more control over load balancing, share difficulty, and inefficient worker handling.
2) Savings Accounts [these will be pass-through accounts, not fully insured]
3) New mining protocol pool software (modification of new software being developed in #1 to support "infinite" growth of miner speeds with no change in pool load)
4) Cash withdrawals [still not sure which service(s)/currencies will be offered]
#1 is moving along, though slowly. Many of the internals of Bitcoin aren't well documented (the general nature is, but specifics are hard to come by), most of it has to be reverse engineered by looking at how it works in the source. I'm hopeful that a working prototype will be done by the end of the month, and deployed to the live servers early August.
July 19, 2012, 03:18:18 PM
any news on savings wallet and other features to come?
July 18, 2012, 05:21:29 PM
What's up with the website?
Some kind of detail of what you're experiencing would be helpful. It's been working perfectly since the SSL update for me on IE, Firefox, and Chrome.
Fair enough.
It was unreachable for a while and now its back. I've had problems connecting my miners for the last day or so and my "24 Hour Earnings" column does not reflect the true hash rate as it's been for months. My fallback pool is showing shares earned. To me this says periodic problems. Do you agree?
Edit: Also the "Unpaid Rewards" column is skewed to one side and the buttons look like they are out of position.
Regarding the columns being skewed: That seems to be on your end. Do you have any kind of Ease of Access options turned on that might screw with font settings?
There was some brief downtime on mine1.btcguild.com (which is the same as btcguild.com) in the last 24 hours. ~3 minutes actually offline, but maybe 30 minutes where the pool may not have served work fast enough.
Your 24 hour earnings dropped a lot because of the difficulty yesterday. The 24 hour earnings has -always- been a calculated value, not an actual value. It takes 24 hour share submissions multiplied by the CURRENT rates. So when difficulty changes, the value will be higher/lower than your actual 24 hour value.
July 18, 2012, 04:56:35 PM
What's up with the website?
Some kind of detail of what you're experiencing would be helpful. It's been working perfectly since the SSL update for me on IE, Firefox, and Chrome.
July 18, 2012, 12:04:23 PM
SSL Certificate has been updated. Sorry this would not completed last night, my home connection was experiencing 35~40% packet loss last night which made it pretty much impossible to use my browser or SSH.
July 18, 2012, 01:35:54 AM
The SSL certificate for BTC Guild expired today. I will have to issue a new SSL cert when I get home this evening. Until then, if your browser states that the SSL connection is insecure, you can check the certificate yourself and see that is still valid, simply expired.
Additionally, if you use any kind of SSL certificate monitoring addons for your browser, you may see another warning tonight/tomorrow when the certificate is changed.
Additionally, if you use any kind of SSL certificate monitoring addons for your browser, you may see another warning tonight/tomorrow when the certificate is changed.
You can get a free ssl cert at startssl.com. I've StartCom them before and they worked fine and were recognized in all browsers. Seems like a waste to pay for one at GoDaddy. I don't think it does anything any better. StartCom has been around for many years and is widely known...
July 17, 2012, 06:14:02 PM
The SSL certificate for BTC Guild expired today. I will have to issue a new SSL cert when I get home this evening. Until then, if your browser states that the SSL connection is insecure, you can check the certificate yourself and see that is still valid, simply expired.
Additionally, if you use any kind of SSL certificate monitoring addons for your browser, you may see another warning tonight/tomorrow when the certificate is changed.
Additionally, if you use any kind of SSL certificate monitoring addons for your browser, you may see another warning tonight/tomorrow when the certificate is changed.
July 11, 2012, 10:42:27 AM
A few adjustments were made on mine2.btcguild.com to reduce load in the last 24 hours. Things are looking very good on the new node. Downtime only lasted a few seconds late last night.
A new pool daemon is being worked on currently to better handle increased loads. The first version should be ready later this month, and will correct nTime Rolling support, along with optimizations to reduce the effects of inefficient miners on overall pool performance. This is an intermediate fix though.
After the new pool code is completed, a new version will be developed to support the new mining protocol that I've been working on with ArtForz. Once a proof of concept is completed, we'll be sending information to miner software developers to work on getting support added to clients. This is a very exciting development that offers "infinite" scaling. The data going from the pool to the client will be the same whether you mine at 1 Kh/s or 100 Th/s. The only increase will be in the data you send to the pool (share submissions). Since BTC Guild is PPS, even that can be limited by giving miners the option to change their share difficulty, which the new pool and protocol will support.
A new pool daemon is being worked on currently to better handle increased loads. The first version should be ready later this month, and will correct nTime Rolling support, along with optimizations to reduce the effects of inefficient miners on overall pool performance. This is an intermediate fix though.
After the new pool code is completed, a new version will be developed to support the new mining protocol that I've been working on with ArtForz. Once a proof of concept is completed, we'll be sending information to miner software developers to work on getting support added to clients. This is a very exciting development that offers "infinite" scaling. The data going from the pool to the client will be the same whether you mine at 1 Kh/s or 100 Th/s. The only increase will be in the data you send to the pool (share submissions). Since BTC Guild is PPS, even that can be limited by giving miners the option to change their share difficulty, which the new pool and protocol will support.
July 05, 2012, 05:16:33 PM
Completed the switch of hot wallets early. Payouts were unavailable for about 3 minutes while unloading the old wallet and loading the new wallet. Hopefully this shouldn't be required more than every month or two.
Dang how big's your wallet.dat? I defrag my blk0001.dat and blkindex.dat about once a week.The hot wallet wasn't as bad as I figured it would be (125 MB).
July 05, 2012, 04:41:43 PM
Completed the switch of hot wallets early. Payouts were unavailable for about 3 minutes while unloading the old wallet and loading the new wallet. Hopefully this shouldn't be required more than every month or two.
July 05, 2012, 03:02:43 PM
The pool wallet has finally gotten fragmented to the point that a payout times out about once per day. Payouts still get processed, but the frontend isn't given a txid and the user ends up not seeing the payout on their history until a cleanup is run manually.
Payouts will be disabled from 3:30 PM (PDT) until 3:50 PM (PDT) in order to move coins to switch over to a new wallet.dat.
UPDATE: There was a very brief (~60 second) outage on the mining servers to update which address they mine coins to for the wallet switch.
Payouts will be disabled from 3:30 PM (PDT) until 3:50 PM (PDT) in order to move coins to switch over to a new wallet.dat.
UPDATE: There was a very brief (~60 second) outage on the mining servers to update which address they mine coins to for the wallet switch.
July 03, 2012, 01:42:51 PM
Yeah, probably a bad word to use. Although there will also be TOR mining through a .onion as well ;p Basically the actual servers won't be exposed to traffic anymore. The website would be attackable since it must be exposed, but the mining pools would never be exposed to a direct connection.
July 03, 2012, 01:22:40 PM
Thanks for running an excellent and reliable service (minus the few DDoS beyond your control)
Thank you
. If things work as I believe they will with the protocol rewrite, I'm going to have some extra lines of defense against DDoS as well. The new system reduces bandwidth consumption dramatically (uploaded data to miners should be in the realm of 1-2 KB/MINUTE regardless of how fast the miner is). With that, I might be able to affordably move the servers to new IPs privately, and setup a proxy layer of Amazon EC2 instances using Elastic IPs. If a DDoS were to hit them, I could swap IPs in just a few seconds. It wouldn't eliminate a DDoS, and would interrupt mining, but it would make a sustained DDoS (like last years' 3-4 day long DDoS) impossible. 
July 03, 2012, 12:24:57 PM
Thanks for running an excellent and reliable service (minus the few DDoS beyond your control)
Jump to: