Sorry if anyone recently tried to join, was modifying some code to make it run more efficiently.
Pool is back up.
To connect:
Hostname: mining.peermining.us:8332
Username: Your Bitcoin Address
Password: Whatever You Want
Topic: PeerMining.us - Mining Pool - Instant Payouts - Proportional Payouts 0% FEES! (Read 1945 times)
October 03, 2012, 12:41:44 AM
October 02, 2012, 09:32:00 PM
New users to the pool, please just use your Bitcoin address and whatever password you want for your username/password combo for now, it will accept it without registering.
Thanks
October 02, 2012, 08:38:03 PM
As an update, since I'm working on the other website, so that you can still mine.
The new address to connect to, so that there will be no downtime in the future is:
http://mining.peermining.us:8332
The new address to connect to, so that there will be no downtime in the future is:
http://mining.peermining.us:8332
October 02, 2012, 08:24:34 AM
Here's a thought - nobody offers PPS with dynamic difficulty yet... It can't be any tougher to implement than dynamic difficulty DGM...
Just FYI: BTC Guild uses dynamic difficulty on the stratum server, which has been part of the main pool for almost 2 weeks. Difficulty is adjusted for each connection to a steady rate of share submissions (1 per 3-5 seconds).
October 02, 2012, 08:14:35 AM
Here's a thought - nobody offers PPS with dynamic difficulty yet... It can't be any tougher to implement than dynamic difficulty DGM...
Just FYI: BTC Guild uses dynamic difficulty on the stratum server, which has been part of the main pool for almost 2 weeks. Difficulty is adjusted for each connection to a steady rate of share submissions (1 per 3-5 seconds).
October 02, 2012, 01:00:41 AM
Good to hear. I'm definitely interested in trying PPS on your pool. Also, what will the difficulty be set at for mining on PPS?
I'm working on a custom difficulty PPS setup right now. Should have something working, though the front end might not be to pretty at first, but this way it gives the miner more flexibility. Will keep you all posted!
October 02, 2012, 12:19:53 AM
Here's a thought - nobody offers PPS with dynamic difficulty yet... It can't be any tougher to implement than dynamic difficulty DGM...
I fully support this idea!
I'm actually working on it as we speak. As a result though, the proportional system is still working if you still want to mine, however I've detached the front end from the MySQL database, so the graphs and statistics are not going to show up properly.
The shares ARE being logged still in MySQL, but while I'm working on the code it will not display for the time being, but will be back up soon and your correct shares will show once I have completed it.
October 01, 2012, 10:19:57 PM
Here's a thought - nobody offers PPS with dynamic difficulty yet... It can't be any tougher to implement than dynamic difficulty DGM...
I fully support this idea!
October 01, 2012, 10:01:15 PM
Here's a thought - nobody offers PPS with dynamic difficulty yet... It can't be any tougher to implement than dynamic difficulty DGM...
Will look into it!
October 01, 2012, 05:55:47 PM
Here's a thought - nobody offers PPS with dynamic difficulty yet... It can't be any tougher to implement than dynamic difficulty DGM...
October 01, 2012, 05:50:00 PM
Good to hear. I'm definitely interested in trying PPS on your pool. Also, what will the difficulty be set at for mining on PPS?
October 01, 2012, 05:47:40 PM
When do you plan on rolling out PPS for your pool, and what will the fees be?
Soon is the best I can tell you right now, as we have a lot on our plate. We're redeveloping the website, acquiring funds for the reserve, re-developing our payout systems.
Fees will be very competitive is what I can tell you right now.
October 01, 2012, 05:45:07 PM
When do you plan on rolling out PPS for your pool, and what will the fees be?
October 01, 2012, 05:02:53 PM
How many GH/s can you handle at the moment? What is your current approx hash rate? Hopping proof?
Well based on the current maximum getwork rate it's 4GH/s with "rollntime" extension, we have a very very low stale rate less than 0.1% and even lower on rejected.
"The original getwork protocol only provides a single block header, which is sufficient for a total of about 4 GH of mining. With the "rollntime" extension, this can be extended to 4 GH *per second*, but even that is far from sufficient for the next generation of mining equipment (ASICs) which are capable of 1000 GH/s on the high end.
By moving block creation to the miners, they are enabled to create as much work as they need locally, thus overcoming this limitation."
Which is why we will be support both getwork and getblocktemplate in there very near future.
Well that is from the Bitcoin wiki. It does say 4GH *per second*, so I'm sure it can handle more, I'm just not exactly sure where the -actual- amount of total GH/s it can handle would be. From my understanding its a limitation on the JSON being the 4 GH *per second*.
October 01, 2012, 04:51:02 PM
How many GH/s can you handle at the moment? What is your current approx hash rate? Hopping proof?
Well based on the current maximum getwork rate it's 4GH/s with "rollntime" extension, we have a very very low stale rate less than 0.1% and even lower on rejected.
"The original getwork protocol only provides a single block header, which is sufficient for a total of about 4 GH of mining. With the "rollntime" extension, this can be extended to 4 GH *per second*, but even that is far from sufficient for the next generation of mining equipment (ASICs) which are capable of 1000 GH/s on the high end.
By moving block creation to the miners, they are enabled to create as much work as they need locally, thus overcoming this limitation."
Which is why we will be support both getwork and getblocktemplate in there very near future.
October 01, 2012, 04:05:39 PM
How many GH/s can you handle at the moment? What is your current approx hash rate? Hopping proof?
Well based on the current maximum getwork rate it's 4GH/s with "rollntime" extension, we have a very very low stale rate less than 0.1% and even lower on rejected.
"The original getwork protocol only provides a single block header, which is sufficient for a total of about 4 GH of mining. With the "rollntime" extension, this can be extended to 4 GH *per second*, but even that is far from sufficient for the next generation of mining equipment (ASICs) which are capable of 1000 GH/s on the high end.
By moving block creation to the miners, they are enabled to create as much work as they need locally, thus overcoming this limitation."
Which is why we will be support both getwork and getblocktemplate in there very near future.
October 01, 2012, 12:49:16 PM
How many GH/s can you handle at the moment? What is your current approx hash rate? Hopping proof?
October 01, 2012, 12:24:03 PM
More miners are welcome!
September 30, 2012, 12:58:56 PM
Yes, the graphs and the hash rates aren't extremely accurate but the shares are 100% accurate as that number is directly pulled from MySQL. The graphs are simple Java scripts that calculate your hash rate based on the time stamp and how often you send shares, so it's not actually reading your hash rate in real time, thus making it inaccurate from what I understand. I'll see what I can do on fixing this, however, for now it won't be something that is immediately resolved since I believe an update of the entire website will be coming soon enough.
Oh crud - total shares - My mistake. I'll be editing my posts to reflect it.
As for the hash - I went ahead and sold my free hashes to someone so I won't be able to mine on your pool for the next 13 days... unless more hardware arrives --- if ASICs don't start shipping in october, I may just hit you up to 90% of pool capacity then. Is that number accurate... if not how much getwork could you actually handle?
Currently we are working to be able to support both Getwork and Getblocktemplate. Once we have Getblocktemplate, we'll be able to support a lot more.
September 30, 2012, 12:25:51 PM
Yes, the graphs and the hash rates aren't extremely accurate but the shares are 100% accurate as that number is directly pulled from MySQL. The graphs are simple Java scripts that calculate your hash rate based on the time stamp and how often you send shares, so it's not actually reading your hash rate in real time, thus making it inaccurate from what I understand. I'll see what I can do on fixing this, however, for now it won't be something that is immediately resolved since I believe an update of the entire website will be coming soon enough.
Oh crud - total shares - My mistake. I'll be editing my posts to reflect it.
As for the hash - I went ahead and sold my free hashes to someone so I won't be able to mine on your pool for the next 13 days... unless more hardware arrives --- if ASICs don't start shipping in october, I may just hit you up to 90% of pool capacity then. Is that number accurate... if not how much getwork could you actually handle?
Jump to: