Old simplecoin thread

[sirky]

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.

[1715020133]

1715020133

[sirky]

Its not real... 141014 belongs to us with 28 network confirms already.  Looks like we raced you guys for it and won.

I have noticed that our block numbers are often off by 1 or so for whatever reason, so this is probably it.

They are talking about this issue with the Simplecoin frontend in the BTCGuild thread now

[simplecoin]

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.

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.

[AnnihilaT]

Mike you are welcome to have a look at cronjob.php from my fork and see how i do it.   It's been running solid for 30+ blocks now and its just some simple math to determine which block we just solved.  Take a look and you are welcome to use it if you can.

[simplecoin]

Mike you are welcome to have a look at cronjob.php from my fork and see how i do it.   It's been running solid for 30+ blocks now and its just some simple math to determine which block we just solved.  Take a look and you are welcome to use it if you can.

Thanks, I'll definitely take a look. I've gotten it much closer, but apparently not quite there.

[sirky]

Mike you are welcome to have a look at cronjob.php from my fork and see how i do it.   It's been running solid for 30+ blocks now and its just some simple math to determine which block we just solved.  Take a look and you are welcome to use it if you can.

Thanks, I'll definitely take a look. I've gotten it much closer, but apparently not quite there.

Eleuthria says that he just waits for Block Explorer to update and then matches the hash. Allegedly the client isn't really trustworthy.

[simplecoin]

Mike you are welcome to have a look at cronjob.php from my fork and see how i do it.   It's been running solid for 30+ blocks now and its just some simple math to determine which block we just solved.  Take a look and you are welcome to use it if you can.

Thanks, I'll definitely take a look. I've gotten it much closer, but apparently not quite there.

Eleuthria says that he just waits for Block Explorer to update and then matches the hash. Allegedly the client isn't really trustworthy.

That sounds like a better option, assuming block explorer has a simple api and has reliable uptime.

[simplecoin]

Looks like the unconfirmed estimate stat needs some work... Just so you know I'm on top of it.

[RyNinDaCleM]

Looks like the unconfirmed estimate stat needs some work... Just so you know I'm on top of it.

Was it accurate before? or is it accurate now?
I lost roughly .25BTC in that confirm!  

Edit:
It's back now! 

[simplecoin]

Looks like the unconfirmed estimate stat needs some work... Just so you know I'm on top of it.

Was it accurate before? or is it accurate now?
I lost roughly .25BTC in that confirm!  

Edit:
It's back now! 

No, the unconfirmed estimate isn't quite right (It was close, but counted all shares in the round, not just last_n). However, I'll get it sorted, as I want to make unconfirmed payouts possible eventually.

The payout calculation is 100% correct, so your balance is ALWAYS what it should be

[RyNinDaCleM]

Looks like the unconfirmed estimate stat needs some work... Just so you know I'm on top of it.

Was it accurate before? or is it accurate now?
I lost roughly .25BTC in that confirm!  

Edit:
It's back now! 

No, the unconfirmed estimate isn't quite right (It was close, but counted all shares in the round, not just last_n). However, I'll get it sorted, as I want to make unconfirmed payouts possible eventually.

The payout calculation is 100% correct, so your balance is ALWAYS what it should be

Ok! Cool!
Thanks a lot man!

[simplecoin]

Looks like the unconfirmed estimate stat needs some work... Just so you know I'm on top of it.

Was it accurate before? or is it accurate now?
I lost roughly .25BTC in that confirm!  

Edit:
It's back now! 

No, the unconfirmed estimate isn't quite right (It was close, but counted all shares in the round, not just last_n). However, I'll get it sorted, as I want to make unconfirmed payouts possible eventually.

The payout calculation is 100% correct, so your balance is ALWAYS what it should be

Ok! Cool!
Thanks a lot man!

Alright, unconfirmed estimates should be exact now

[simplecoin]

Just bringing a new replication server online, sorry for the 30-45 seconds of rejects....

[sirky]

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.

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?

[simplecoin]

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.

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)

[sirky]

I think the top 30 lifetime shares is broken again, because almost surely loderunner would be up there just from this round.

[RyNinDaCleM]

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!

[Jine]

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.

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

[simplecoin]

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.

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/

[teukon]

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?