Another block,
quite good.
I concur!quite good.
Though, it is block 141553, and 0 confirms!?! We're currently on block 141559!
tvhwgt's block did the same so I'm not too worried. I guess we'll see.
Topic: Old simplecoin thread - page 14. (Read 99808 times)
Though, it is block 141553, and 0 confirms!?! We're currently on block 141559!
tvhwgt's block did the same so I'm not too worried. I guess we'll see.
Another block,
quite good.
I concur!quite good.
Though, it is block 141553, and 0 confirms!?! We're currently on block 141559!
Another block,
quite good.
quite good.
On the upside! 2 blocks, 1 day 
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it (will have much higher reject rate).... but it remains available.
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it (will have much higher reject rate).... but it remains available.
If running two servers concurrently are causing performance issues, I don't think there is anything wrong with posting something saying that 'at XYZ date simplecoin.us:8337 will no longer work. Please switch your miners to pool.simplecoin.us:8337.
In other news the website has been much more responsive recently though
Well, the pool on simplecoin.us is running off of the bitcoin client on pool.simplecoin.us now. However, since it's using blkmond remotely there are more chances for stale shares on it.
The only resource it's expending is disk space (slowly), and open tcp sockets. Neither of these is really hurting performance now.
That said, pool.simplecoin.us is handling things well. I think I'll reach disk I/O issues before I run into cpu/network bottlenecks. The pool should be able to handle about 500-1000mhs without issue. After I make a few adjustments to pushpool it should scale beyond that.
On the upside! 2 blocks, 1 day
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it (will have much higher reject rate).... but it remains available.
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it (will have much higher reject rate).... but it remains available.
If running two servers concurrently are causing performance issues, I don't think there is anything wrong with posting something saying that 'at XYZ date simplecoin.us:8337 will no longer work. Please switch your miners to pool.simplecoin.us:8337.
In other news the website has been much more responsive recently though
Our main sql server just took a dive. Had to fire up the backup.
Sorry for the few minutes downtime.
Sorry for the few minutes downtime.
On the upside! 2 blocks, 1 day
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it.... but it remains available.
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it.... but it remains available.
Wooooooooooooooooooooooooooooo
On the upside! 2 blocks, 1 day
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it (will have much higher reject rate).... but it remains available.
Also, the simplecoin.us pool isn't going anywhere
It won't perform quite as well as pool.simplecoin.us, and I don't recommend using it (will have much higher reject rate).... but it remains available.
A total of ~4 btc was overdrawn.
I have patched the issue to prevent the possibility of it happening again.
I have asked the users for their cooperation, and hope it was somehow accidental.
UPDATE: This was caused by nginx timing out during a payment, not a direct exploit. The fix in place should prevent this.
Does the automatic payout feature work for anyone or is it not implemented yet? My balance has been more than double my automatic payout amount for a few days now but no payout has been made.
It was turned off during the framework update. I'll check it and get it back online.
Does the automatic payout feature work for anyone or is it not implemented yet? My balance has been more than double my automatic payout amount for a few days now but no payout has been made.
Another block. Many thanks tvhwgt.
Nice. I go away for a few days and come back to find that not only has the pool doubled in size but two blocks have been found!
I'm using pool.simplecoin.us now and my stales situation seems to have improved to a comfortable 0.2% stales (for 7000 shares). Looks like I won't have to investigate cgminer further after all.
Please do keep the old server running for as long as you can. A reputation for reliability seems more important than a fast website.
May I ask what is the "Pool efficiency" statistic represents?
I'm using pool.simplecoin.us now and my stales situation seems to have improved to a comfortable 0.2% stales (for 7000 shares). Looks like I won't have to investigate cgminer further after all.
Please do keep the old server running for as long as you can. A reputation for reliability seems more important than a fast website.
May I ask what is the "Pool efficiency" statistic represents?
Probably 1 - the overall % of stales.
Nice. I go away for a few days and come back to find that not only has the pool doubled in size but two blocks have been found!
I'm using pool.simplecoin.us now and my stales situation seems to have improved to a comfortable 0.2% stales (for 7000 shares). Looks like I won't have to investigate cgminer further after all.
Please do keep the old server running for as long as you can. A reputation for reliability seems more important than a fast website.
May I ask what is the "Pool efficiency" statistic represents?
I'm using pool.simplecoin.us now and my stales situation seems to have improved to a comfortable 0.2% stales (for 7000 shares). Looks like I won't have to investigate cgminer further after all.
Please do keep the old server running for as long as you can. A reputation for reliability seems more important than a fast website.
May I ask what is the "Pool efficiency" statistic represents?
Great to see the new people in the pool!
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
If you ever want to pitch in any new stats or features, you're welcome to send pull requests on the git repository.
As for block reporting, it's getting closer. I'll get it nailed down soon.
I've heard some concerns about the website speed. The sooner everyone is using pool.simplecoin.us, the sooner I can get some more performance out of our webserver.
Can you redirect simplecoin.us:8337 to pool.simplecoin.us:8337?
I'd like to, but I'm not sure how to go about it. Everything I've read suggests that the traffic cannot be forwarded to a wholly different ip. I also cannot setup a proxy on that box as I was instructed not to (it's a rental, I don't plan on breaking the TOS)
Setup a simple nginx instance running at port 8337, add a Location: pool.simplecoin.us:8337
Should work for all miners that actually follows the HTTP/1.1 specification...
(Which prob. no-one does?) ;P
I thought of that, but that's still proxying.... which is against my datacenter's TOS. I'll have to run it by them.
Also, everyone can now monitor their stats at http://www.btc-poolwatch.com/
Great to see the new people in the pool!
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
If you ever want to pitch in any new stats or features, you're welcome to send pull requests on the git repository.
As for block reporting, it's getting closer. I'll get it nailed down soon.
I've heard some concerns about the website speed. The sooner everyone is using pool.simplecoin.us, the sooner I can get some more performance out of our webserver.
Can you redirect simplecoin.us:8337 to pool.simplecoin.us:8337?
I'd like to, but I'm not sure how to go about it. Everything I've read suggests that the traffic cannot be forwarded to a wholly different ip. I also cannot setup a proxy on that box as I was instructed not to (it's a rental, I don't plan on breaking the TOS)
Setup a simple nginx instance running at port 8337, add a Location: pool.simplecoin.us:8337
Should work for all miners that actually follows the HTTP/1.1 specification...
(Which prob. no-one does?) ;P
I think the top 30 lifetime shares is broken again, because almost surely loderunner would be up there just from this round.
In previous rounds, I've noticed that newcomers weren't added until the next round!On a side note:
My charts/graphs work now!
I think it has something to do with the old version of firefox I was using (3.6). Upgraded to 5.0, and they work!
I think the top 30 lifetime shares is broken again, because almost surely loderunner would be up there just from this round.
Great to see the new people in the pool!
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
If you ever want to pitch in any new stats or features, you're welcome to send pull requests on the git repository.
As for block reporting, it's getting closer. I'll get it nailed down soon.
I've heard some concerns about the website speed. The sooner everyone is using pool.simplecoin.us, the sooner I can get some more performance out of our webserver.
Can you redirect simplecoin.us:8337 to pool.simplecoin.us:8337?
I'd like to, but I'm not sure how to go about it. Everything I've read suggests that the traffic cannot be forwarded to a wholly different ip. I also cannot setup a proxy on that box as I was instructed not to (it's a rental, I don't plan on breaking the TOS)
Great to see the new people in the pool!
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
Anyway, can we be able to see a more accurate estimate? Also, can we see how many shares we submitted for each of the blocks, since we have changed the payout structure?
The website doesn't really do a good job of letting everyone know why they are getting paid what they are.
Let me know if you want some help writing some of the code or anything. I'd be happy to do what I can.
If you ever want to pitch in any new stats or features, you're welcome to send pull requests on the git repository.
As for block reporting, it's getting closer. I'll get it nailed down soon.
I've heard some concerns about the website speed. The sooner everyone is using pool.simplecoin.us, the sooner I can get some more performance out of our webserver.
Can you redirect simplecoin.us:8337 to pool.simplecoin.us:8337?
Jump to: