IYFTech
|
|
October 31, 2014, 11:31:50 AM Last edit: October 31, 2014, 11:43:22 AM by IYFTech |
|
Bitmains new S2 firmware improves p2pool compatibility, it's still not optimal, but much more bearable with a lower DOA/reject rate than before - as well as almost a 100Gh/s increase! (in my case, one went from 880 to 980) Bitmain let me test their beta releases on my node & they seem to have got this one right - shows what a little R&D can do..... I'm using --queue 1 atm, will test with queue 0 later.
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
October 31, 2014, 01:12:50 PM |
|
Bitmains new S2 firmware improves p2pool compatibility, it's still not optimal, but much more bearable with a lower DOA/reject rate than before - as well as almost a 100Gh/s increase! (in my case, one went from 880 to 980) Bitmain let me test their beta releases on my node & they seem to have got this one right - shows what a little R&D can do..... I'm using --queue 1 atm, will test with queue 0 later. Better late then never I guess, that is good news
|
|
|
|
IYFTech
|
|
October 31, 2014, 01:28:43 PM |
|
Bitmains new S2 firmware improves p2pool compatibility, it's still not optimal, but much more bearable with a lower DOA/reject rate than before - as well as almost a 100Gh/s increase! (in my case, one went from 880 to 980) Bitmain let me test their beta releases on my node & they seem to have got this one right - shows what a little R&D can do..... I'm using --queue 1 atm, will test with queue 0 later. Better late then never I guess, that is good news Shame they didn't do it 10 weeks ago. Running with --queue 0 is proving the best setting again I'm finding - it's like a new miner!
|
|
|
|
jonnybravo0311
Legendary
Offline
Activity: 1344
Merit: 1023
Mine at Jonny's Pool
|
|
October 31, 2014, 04:50:42 PM |
|
Bitmains new S2 firmware improves p2pool compatibility, it's still not optimal, but much more bearable with a lower DOA/reject rate than before - as well as almost a 100Gh/s increase! (in my case, one went from 880 to 980) Bitmain let me test their beta releases on my node & they seem to have got this one right - shows what a little R&D can do..... I'm using --queue 1 atm, will test with queue 0 later. Better late then never I guess, that is good news Shame they didn't do it 10 weeks ago. Running with --queue 0 is proving the best setting again I'm finding - it's like a new miner! Wow... they're just now releasing p2pool compatible firmware for the S2. I remember discussing this here in May/June. Glad you finally got your S2 to work on p2pool, though
|
Jonny's Pool - Mine with us and help us grow! Support a pool that supports Bitcoin, not a hardware manufacturer's pockets! No SPV cheats. No empty blocks.
|
|
|
PatMan
|
|
October 31, 2014, 05:10:39 PM |
|
Bitmains new S2 firmware improves p2pool compatibility, it's still not optimal, but much more bearable with a lower DOA/reject rate than before - as well as almost a 100Gh/s increase! (in my case, one went from 880 to 980) Bitmain let me test their beta releases on my node & they seem to have got this one right - shows what a little R&D can do..... I'm using --queue 1 atm, will test with queue 0 later. Better late then never I guess, that is good news Shame they didn't do it 10 weeks ago. Running with --queue 0 is proving the best setting again I'm finding - it's like a new miner! Wow... they're just now releasing p2pool compatible firmware for the S2. I remember discussing this here in May/June. Glad you finally got your S2 to work on p2pool, though Yeah, it really is a massive improvement, some of mine are humming away at just below 1Th/s using the -q 0 setting with very acceptable DOA, such a shame Bitmain didn't do this kind of testing right from the beginning with all their firmware.....
|
|
|
|
|
PatMan
|
|
October 31, 2014, 06:59:59 PM |
|
Yeah, I posted there already...... Shame though, it was probably the best centralised pool out there. This is what US regulations do........f*ck everything up
|
|
|
|
jedimstr
|
|
October 31, 2014, 11:20:07 PM |
|
Yeah, I posted there already...... Shame though, it was probably the best centralised pool out there. This is what US regulations do........f*ck everything up There's a followup update... it's not shutting down afterall since Eleuthuria found a buyer. Also, part of their deal will probably include him sticking around for a few more years.
|
|
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
November 01, 2014, 02:22:18 AM |
|
|
|
|
|
HellDiverUK
|
|
November 01, 2014, 09:38:49 AM |
|
There's a followup update... it's not shutting down afterall since Eleuthuria found a buyer. Also, part of their deal will probably include him sticking around for a few more years.
That's not accurate at all. He has two interested parties. He never said it wasn't shutting down, and he never said he found a buyer.
|
|
|
|
jedimstr
|
|
November 01, 2014, 11:22:24 AM |
|
There's a followup update... it's not shutting down afterall since Eleuthuria found a buyer. Also, part of their deal will probably include him sticking around for a few more years.
That's not accurate at all. He has two interested parties. He never said it wasn't shutting down, and he never said he found a buyer. More accurate than your response, but yes, I should have said "potential buyer(s)". For reference: https://bitcointalk.org/index.php?topic=49417.msg9397724#msg9397724And: https://bitcointalk.org/index.php?topic=49417.msg9397811#msg9397811 Re: [CLOSING] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers October 31, 2014, 03:42:16 PM Reply with quote #7961 BTC Guild Shutting Down Likely Being Sold Earlier today, a news post was made identifying that BTC Guild would be shutting down on January 31, 2015. This post is still available in its entirety on the Bitcointalk forum ( https://bitcointalk.org/index.php?topic=49417.msg9395478#msg9395478). Just hours after making this post, multiple parties have expressed strong interest in purchasing BTC Guild and keeping it running. As a result, the previously announced timeline for closure of operations has been cancelled, and the site will likely continue without interruption.This was just updated on the BTC Guild website after it was clear that it is almost certain that BTC Guild will not be shutting its doors. While I may be ending my watch over the pool in the coming months, it will continue. Quote from: Miner-TE on October 31, 2014, 03:43:43 PM Smiley Good news ... But were still loosing you ... Sad
Eventually, yes. Part of negotiations (regardless of who ends up buying the pool) will almost certainly revolve around how much time I remain involved with the pool. Depending on the final terms, it is possible you continue to see me around for years to come in some capacity.
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
November 01, 2014, 04:58:42 PM |
|
Heh - I am potentially one of them, despite the on/off nature of the Guild's announcement. I was hoping to find some words-of-one-syl tutorials for setting up a p2pool account from scratch and using Bitmain's Antminer (S1, S2, S3) LuCI interface with it. I've found tantalizing hints that it can be done but no obvious tutorials. I hope they are not right under my nose, but if so I'm just not seeing them. Do such tutorials exist (something like Dogie's or rubicite's tutorials for centralized pool users), and if so, can anyone point me to them? Thanks!
|
|
|
|
mdude77
Legendary
Offline
Activity: 1540
Merit: 1001
|
|
November 01, 2014, 05:13:32 PM |
|
Heh - I am potentially one of them, despite the on/off nature of the Guild's announcement. I was hoping to find some words-of-one-syl tutorials for setting up a p2pool account from scratch and using Bitmain's Antminer (S1, S2, S3) LuCI interface with it. I've found tantalizing hints that it can be done but no obvious tutorials. I hope they are not right under my nose, but if so I'm just not seeing them. Do such tutorials exist (something like Dogie's or rubicite's tutorials for centralized pool users), and if so, can anyone point me to them? Thanks! On windows in linux? On windows it's pretty easy. Download the p2pool executable, and fire it up with your payout address. Then point each of your Ants to that address ... stratum+tcp://internal.address.in.numeric.format:9332 If running locally, the usernames don't matter. To set the difficulty, suffix them with a +number ... for S1s and S3s, I'd use +518. For S2 I'd use +1024. But it'll run just fine w/o the +difficulty as well. You can also install python and the required modules for p2pool and run the latest git. On linux it's a little more complicated, but roughly the same idea. M
|
I mine at Kano's Pool because it pays the best and is completely transparent! Come join me!
|
|
|
aigeezer
Legendary
Offline
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
November 01, 2014, 07:24:01 PM Last edit: November 01, 2014, 07:59:11 PM by aigeezer |
|
Heh - I am potentially one of them, despite the on/off nature of the Guild's announcement. I was hoping to find some words-of-one-syl tutorials for setting up a p2pool account from scratch and using Bitmain's Antminer (S1, S2, S3) LuCI interface with it. I've found tantalizing hints that it can be done but no obvious tutorials. I hope they are not right under my nose, but if so I'm just not seeing them. Do such tutorials exist (something like Dogie's or rubicite's tutorials for centralized pool users), and if so, can anyone point me to them? Thanks! On windows in linux? On windows it's pretty easy. Download the p2pool executable, and fire it up with your payout address. Then point each of your Ants to that address ... stratum+tcp://internal.address.in.numeric.format:9332 If running locally, the usernames don't matter. To set the difficulty, suffix them with a +number ... for S1s and S3s, I'd use +518. For S2 I'd use +1024. But it'll run just fine w/o the +difficulty as well. You can also install python and the required modules for p2pool and run the latest git. On linux it's a little more complicated, but roughly the same idea. M Thank you, mdude77! That is exactly what I was hoping to find. Yes, Windows for me most of the time these days. Edit: I just noticed that my problem arose because I was thrashing around at http://p2pool.org/ rather than http://p2pool.in/ - each is useful in its own way.
|
|
|
|
windpath
Legendary
Offline
Activity: 1258
Merit: 1027
|
|
November 01, 2014, 11:12:19 PM |
|
Thank you, mdude77! That is exactly what I was hoping to find. Yes, Windows for me most of the time these days. Edit: I just noticed that my problem arose because I was thrashing around at http://p2pool.org/ rather than http://p2pool.in/ - each is useful in its own way. Any advice you can give as to how we could make p2pool.org experience more helpful for new users would be appreciated
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
November 02, 2014, 02:35:31 PM Last edit: November 02, 2014, 05:17:04 PM by aigeezer |
|
Thank you, mdude77! That is exactly what I was hoping to find. Yes, Windows for me most of the time these days. Edit: I just noticed that my problem arose because I was thrashing around at http://p2pool.org/ rather than http://p2pool.in/ - each is useful in its own way. Any advice you can give as to how we could make p2pool.org experience more helpful for new users would be appreciated OK. Here's a start, while I still have "beginner's mind". When I found out the Guild might be closing, I started to Google search for peer to pool alternatives - something that had been in the back of my mind for a long time. I was surprised to find few hits for the search phrases I tried - stuff like "p2pool antminer" and "p2pool tutorial" although perhaps not exactly these phrases (I forget). In general, I found a lot of single-issue hits but only one Big Picture hit, namely p2pool.org which looked like the centre of the p2pool universe to my rookie eye. I spent a lot of (useful) time there without noticing that it had an important link to p2pool.in Eventually I got to p2pool.in and it seemed to have exactly the step-by-step instructions I wanted. So far I have not got them working but chances are I've overlooked or misread something. Anyway, still with "beginner's mind", looking at the instructions on p2pool.in First I see a header for Download P2pool binary (Windows in my case). Great - this is going to be easy. Download went fine. Then I see a header Getting Started (odd - I wonder why the download came first - still looks easy though). Set up Bitcoin-QT. No problem. I already have it. Oh - it needs a conf file - I can do that. What's in it? RPC name and pw - I can do that (but a total rookie would be baffled, I think). Hmmn - it gives a specific name and pw. Must I use those exact ones? Nah - can't be - must be just an example. Where is the same pw to be used by the miner? skim, skim, can't find it. That's odd. When will this pw actually get used? Keep reading. Click on Example for Windows. It's well done, but it's stuff I already know - finding the elusive conf file and the old dotconfdottxt issue. Now what? Run run_p2pool.exe downloaded earlier. I can do that. I'll run it as administrator, just in case. Hmmn - small window pops up and closes before I have a chance to see what was in it. Looks like it might have been a command prompt console thing. Not what I was expecting. Frantic quick reading - no clues found. Quick look at Task Manager - no obvious new process running. Taking a guess - I'll set up a batch file and run it there to see if I can get it to stay on the screen. Nope, still disappears quickly. Time to RTFM - found a readme file in the download. Yikes - it is very Python-intensive - but, but - I thought the compiled version would avoid all that stuff. Time to step back and think about it a bit. That's it for now - I hope this is useful. Edit: Update. Thought about things a bit, found an old one-page tutorial here: https://bitcointalk.org/index.php?topic=64329.0From it I cribbed the idea of putting a pause in my batch file so I could see what was happening before the window closed. Added timeout /T 300 to the batch file. Bingo. Lots of useful detail had scrolled away before, including an error message - looks like I put my new conf file in the wrong folder. Doh! Edit: Update. Moved the conf file and the run_p2pool.exe is running fine now in its batch file command window. I notice it is donating 1% automatically to devs. Hmmn - I thought the tutorial said 0.5%. Oh well, it is settable and I don't yet know what a fair amount would be. I am seeing lots of "lost peer" and "failure" messages. That does not worry me yet, since I have not pointed any miners at it. Might alarm beginners though. Edit: Update. I set up an Antminer S2 to test things out, following advice under Run Miners at p2pool.in and adapting it to the S2 - which seemed easy but has not worked out yet. In the LuCI interface for my Ant, pool 1 shows http://127.0.0.1:9332/ with a BTC addy as username and an arbitrary password. Alas, the Ant shows the pool is "dead" and is mining on one of the centralized failover pools. The run_p2pool.exe continues to run in its command window. It scrolls pretty fast but seems OK, given that I don't really know what "normal" might look like. It shows the pool at 5578TH/s, for instance. I seem to be stuck now - getting close though. I'll think about it some more.
|
|
|
|
MissouriMiner
|
|
November 02, 2014, 04:12:18 PM |
|
Thank you, mdude77! That is exactly what I was hoping to find. Yes, Windows for me most of the time these days. Edit: I just noticed that my problem arose because I was thrashing around at http://p2pool.org/ rather than http://p2pool.in/ - each is useful in its own way. Any advice you can give as to how we could make p2pool.org experience more helpful for new users would be appreciated OK. Here's a start, while I still have "beginner's mind". When I found out the Guild might be closing, I started to Google search for peer to pool alternatives - something that had been in the back of my mind for a long time. I was surprised to find few hits for the search phrases I tried - stuff like "p2pool antminer" and "p2pool tutorial" although perhaps not exactly these phrases (I forget). In general, I found a lot of single-issue hits but only one Big Picture hit, namely p2pool.org which looked like the centre of the p2pool universe to my rookie eye. I spent a lot of (useful) time there without noticing that it had an important link to p2pool.in Eventually I got to p2pool.in and it seemed to have exactly the step-by-step instructions I wanted. So far I have not got them working but chances are I've overlooked or misread something. Anyway, still with "beginner's mind", looking at the instructions on p2pool.in First I see a header for Download P2pool binary (Windows in my case). Great - this is going to be easy. Download went fine. Then I see a header Getting Started (odd - I wonder why the download came first - still looks easy though). Set up Bitcoin-QT. No problem. I already have it. Oh - it needs a conf file - I can do that. What's in it? RPC name and pw - I can do that (but a total rookie would be baffled, I think). Hmmn - it gives a specific name and pw. Must I use those exact ones? Nah - can't be - must be just an example. Where is the same pw to be used by the miner? skim, skim, can't find it. That's odd. When will this pw actually get used? Keep reading. Click on Example for Windows. It's well done, but it's stuff I already know - finding the elusive conf file and the old dotconfdottxt issue. Now what? Run run_p2pool.exe downloaded earlier. I can do that. I'll run it as administrator, just in case. Hmmn - small window pops up and closes before I have a chance to see what was in it. Looks like it might have been a command prompt console thing. Not what I was expecting. Frantic quick reading - no clues found. Quick look at Task Manager - no obvious new process running. Taking a guess - I'll set up a batch file and run it there to see if I can get it to stay on the screen. Nope, still disappears quickly. Time to RTFM - found a readme file in the download. Yikes - it is very Python-intensive - but, but - I thought the compiled version would avoid all that stuff. Time to step back and think about it a bit. That's it for now - I hope this is useful. Edit: Update. Thought about things a bit, found an old one-page tutorial here: https://bitcointalk.org/index.php?topic=64329.0From it I cribbed the idea of putting a pause in my batch file so I could see what was happening before the window closed. Added timeout /T 300 to the batch file. Bingo. Lots of useful detail had scrolled away before, including an error message - looks like I put my new conf file in the wrong folder. Doh! More anon. Edit: Update. Moved conf file and the run_p2pool.exe is running fine now in its batch file command window. I notice it is donating 1% automatically to devs. Hmmn - I thought the tutorial said 0.5%. Oh well, it is settable and I don't yet know what a fair amount would be. I am seeing lots of "lost peer" and "failure" messages. That does not worry me yet, since I have not pointed any miners at it. Might alarm beginners though. More when I get a chance - may be a while. I think the Wiki page has most/all of the info consolidated in one page. https://en.bitcoin.it/wiki/P2PoolThere are 4 network ports you should pay attention to, and 2 of them you should port-forward on your router. These are the default ports. All can be changed. Keep in mind that there are Bitcoin wallet parameters and there are P2Pool parameters/settings. The wallet parameters should go in the bitcoin.conf file, and the P2Pool parameters should be in the command line to start your pool node. You set the RPC username and password in the bitcoin.conf file, and then you pass those parameters in when you start P2Pool. 8332/tcp Bitcoin Wallet RPC Port - For management/API communication to the Bitcoin Wallet. - NEVER FORWARD THIS PORT, SECURITY RISK 8333/tcp Bitcoin Wallet Node Port - For communicating with other nodes. Forward this port to allow inbound wallet connections. This is not required, but recommended to fully participate in the Bitcoin network. 9332/tcp Bitcoin P2Pool miner and web interface port. Forward this port if you want to allow other miners to mine on your node. And forward if you want to check your statistics (access web page) from outside your LAN. 9333/tcp Bitcoin P2Pool node port. Forward this port to allow inbound connections from other P2Pool nodes. This is not required, but recommended to fully participate in the P2Pool network.
|
|
|
|
PatMan
|
|
November 02, 2014, 04:19:47 PM |
|
I notice it is donating 1% automatically to devs. Hmmn - I thought the tutorial said 0.5%.
Use "--give-author 0" in the startup command (without quotes)
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
November 02, 2014, 05:19:30 PM |
|
I think the Wiki page has most/all of the info consolidated in one page. https://en.bitcoin.it/wiki/P2PoolThere are 4 network ports you should pay attention to, and 2 of them you should port-forward on your router. These are the default ports. All can be changed. Keep in mind that there are Bitcoin wallet parameters and there are P2Pool parameters/settings. The wallet parameters should go in the bitcoin.conf file, and the P2Pool parameters should be in the command line to start your pool node. You set the RPC username and password in the bitcoin.conf file, and then you pass those parameters in when you start P2Pool. 8332/tcp Bitcoin Wallet RPC Port - For management/API communication to the Bitcoin Wallet. - NEVER FORWARD THIS PORT, SECURITY RISK 8333/tcp Bitcoin Wallet Node Port - For communicating with other nodes. Forward this port to allow inbound wallet connections. This is not required, but recommended to fully participate in the Bitcoin network. 9332/tcp Bitcoin P2Pool miner and web interface port. Forward this port if you want to allow other miners to mine on your node. And forward if you want to check your statistics (access web page) from outside your LAN. 9333/tcp Bitcoin P2Pool node port. Forward this port to allow inbound connections from other P2Pool nodes. This is not required, but recommended to fully participate in the P2Pool network. Sounds promising, thanks. I'll check it out. Heh - my wife has other plans for me, so things may drag out a bit.
|
|
|
|
aigeezer
Legendary
Offline
Activity: 1450
Merit: 1013
Cryptanalyst castrated by his government, 1952
|
|
November 02, 2014, 05:35:22 PM |
|
I notice it is donating 1% automatically to devs. Hmmn - I thought the tutorial said 0.5%.
Use "--give-author 0" in the startup command (without quotes) Thanks for the suggestion. I couldn't remember where I had seen 0.5% - everything I looked at now seems to say 1.0% - but I just rediscovered that it shows 0.5% default in the Wiki, presumably out of date. https://en.bitcoin.it/wiki/P2PoolI haven't decided yet what value to actually use - got to get it running first. Unrelated - I notice the Wiki says there are issues with Antminer S2s, which is my test platform - bad choice perhaps, but I think I also saw somewhere that those issues have been fixed. If so, that may be another Wiki update in the making.
|
|
|
|
|