Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 424. (Read 903206 times)
October 24, 2011, 08:19:18 PM
Hey, I just wanted to point out that I was sort of completely ignored earlier. I'm still getting the 403 error on the new btcguild.com site when I try to connect my miners to it. Login's d3m0n1q733rz. Would appreciate if you could take a look at it and let me know why it's forbidding me to connect to it via port 8332.
October 24, 2011, 05:42:32 PM
3 days and no more info while other pools have been running for a while, why cant he figure it out? Does he not understand it, is it something else? would love to know...
Only one LARGE pool has made the switch so far, and that is slush. And I have never hidden the fact that slush is significantly more experienced and knowledgable on the inner workings of both bitcoin and merged mining. He made the first pool.
I'm waiting on shadders to work out some of the final parts of merged mining, specifically related to Long Poll situations, with PoolServerJ before I risk implementing it on the live pool. I'm assuming a risk when I implement it. If something goes wrong, I have to start buying up BTC/NMC to payout user rewards.
You're welcome to go to a different pool and either come back when its done, or just stay wherever you end up. Merged mining is not being added until I'm confident its ready.
October 24, 2011, 04:57:14 PM
3 days and no more info while other pools have been running for a while, why cant he figure it out? Does he not understand it, is it something else? would love to know...
If the pool was smaller, he might have implemented it before...
so the best solution is to go to another, more capable pool.
Way to misquote...
This pool is not incapable, it is large and as such needs to take scaling problems into account where smaller pools can get away with ignoring them.If you're unhappy with a pool's offerings, the solution is always to switch to one that better suits your requirements/preferences.
October 24, 2011, 04:03:55 PM
3 days and no more info while other pools have been running for a while, why cant he figure it out? Does he not understand it, is it something else? would love to know...
If the pool was smaller, he might have implemented it before...
so the best solution is to go to another, more capable pool.
October 24, 2011, 02:12:39 PM
3 days and no more info while other pools have been running for a while, why cant he figure it out? Does he not understand it, is it something else? would love to know...
What are you failing to understand here? He's waiting for the pool software he uses to work more efficiently with merged mining. He has a pretty big pool and needs to make sure the servers won't go down from the additional load when he implements MM. If the pool was smaller, he might have implemented it before...
October 24, 2011, 12:50:01 PM
I asked a question, I expected an answer. I was ignored so well, I will ignore him. I do not like his working with the bot net providers, I dont like how there is 4% missing and I don't like the direction on how things are going. I am willing to listen, but if nothing is said...
https://bitcointalksearch.org/topic/m.588952
October 24, 2011, 12:42:11 PM
SSL security - Access the website via https://www.btcguild.com to protect your information from being sent in plaintext. That part isn't 100% working for me, but maybe it is just me?
Just you. SSL has always worked 100% for me. Now, if you go to the old page, https://old.btcguild.com it will throw an SSL error. That is because the subdomain was never registered in the cert. No big deal, though.Correct. The https://www.btcguild.com cert works fine. Subdomains are not registered on the cert, so https://old.btcguild.com will throw up an error on almost all browsers. It's still an HTTPS connection, its just giving you the warning because that subdomain is not a part of the cert.
October 24, 2011, 12:12:00 PM
Why are there other pools already running with merged mining then? I might be unfair here as I really do not know what is going on. I would life some information, and if i was in error I will come back and will apologize. I am just waiting for a response. Also, if I am missing something please educate me why this pool cant and others can. Peace
I'm "assuming" that he wants something more stable than what is currently in place. I'm a fan of a more conservative approach myself.
But there is certainly nothing wrong with asking questions and I don't see that you need to apologize for anything. I was just pointing out that your question was previously answered to some extent, less than desired of course
.Take Care,
Sam
October 24, 2011, 11:56:43 AM
Since my question to get an ETA on the merged mining was ignored I am going to assume you are a long ways off on getting this done.
Seems to me he answered this to the best of his ability on page 1 of this thread.
He can't get an ETA until someone else do their part.
Sam
October 24, 2011, 08:47:03 AM
SSL security - Access the website via https://www.btcguild.com to protect your information from being sent in plaintext. That part isn't 100% working for me, but maybe it is just me?
Just you. SSL has always worked 100% for me. Now, if you go to the old page, https://old.btcguild.com it will throw an SSL error. That is because the subdomain was never registered in the cert. No big deal, though.Correct. The https://www.btcguild.com cert works fine. Subdomains are not registered on the cert, so https://old.btcguild.com will throw up an error on almost all browsers. It's still an HTTPS connection, its just giving you the warning because that subdomain is not a part of the cert.
October 24, 2011, 08:41:41 AM
SSL security - Access the website via https://www.btcguild.com to protect your information from being sent in plaintext. That part isn't 100% working for me, but maybe it is just me?
Just you. SSL has always worked 100% for me. Now, if you go to the old page, https://old.btcguild.com it will throw an SSL error. That is because the subdomain was never registered in the cert. No big deal, though. 
October 24, 2011, 08:31:16 AM
(marking) 
October 24, 2011, 03:02:08 AM
I just signed up for btcguild and created a worker account but my workers are refusing to connect at all. I know for a fact that the how to connect page isn't accurate because of the format of the phoenix commands. But I'm getting a 403 error when trying to connect to the port. The site shows up, but the port's blocked.
October 23, 2011, 06:47:02 PM
SSL security - Access the website via https://www.btcguild.com to protect your information from being sent in plaintext. That part isn't 100% working for me, but maybe it is just me?
October 23, 2011, 04:35:52 PM
I have to chime in too, why Deepbit? Ars is now the largest pool without fees. Deepbit is also too big to succeed at 3 thash (or a significant fraction of the total network hashrate).
Edit: Sorry, I meant HALF THE NETWORK HASHRATE. Tycho can now perform a 51% attack.
Edit: Sorry, I meant HALF THE NETWORK HASHRATE. Tycho can now perform a 51% attack.
October 23, 2011, 02:33:14 PM
Whenever I try to do the reset pw, the email link just sends me back to the new btcguild. Or should I just wait for my rewards to transfer over to the new btcguild and then payout?
October 23, 2011, 11:33:28 AM
There's a lot of other places that offer autopayout. That reason really doesn't make sense to me.
October 23, 2011, 11:11:40 AM
Autopayout.
October 23, 2011, 10:37:03 AM
Pool is back up. There was one configuration issue on the new server that the beta pool never had changed due to low volume.
All PPS Guild workers were redirected to the main pool, BUT: If you used different user/workernames it doesn't work. The pool is using the old BTC Guild username/worker database. MOST users had the same details for both, but I'm sure a few probably had different setups.
All PPS Guild workers were redirected to the main pool, BUT: If you used different user/workernames it doesn't work. The pool is using the old BTC Guild username/worker database. MOST users had the same details for both, but I'm sure a few probably had different setups.
October 23, 2011, 10:34:49 AM
Jump to: