Krak
|
|
January 22, 2014, 05:49:02 PM |
|
I think -f 50 is for the Windows version of P2Pool. I am running the Linux version.
It's the same on both. You can also use --fee 50.
|
BTC: 1KrakenLFEFg33A4f6xpwgv3UUoxrLPuGn
|
|
|
smoothrunnings
|
|
January 22, 2014, 06:53:54 PM |
|
I think -f 50 is for the Windows version of P2Pool. I am running the Linux version.
It's the same on both. You can also use --fee 50. Thanks Krak! I do have one more question for you, do I need to remove the --give-author 0 command from the startup in order for the --fee 50 to work? Thanks
|
|
|
|
jedimstr
|
|
January 22, 2014, 08:10:50 PM |
|
I think -f 50 is for the Windows version of P2Pool. I am running the Linux version.
It's the same on both. You can also use --fee 50. Thanks Krak! I do have one more question for you, do I need to remove the --give-author 0 command from the startup in order for the --fee 50 to work? Thanks That's the donation amount to forrestv. Totally separate from the fee to you. You really should put something more than 0 to be fair actually. Just like the fee parameter though, it's in percent so --give-author 0.25 is 0.25% donated.
|
|
|
|
freebit13
|
|
January 22, 2014, 09:11:02 PM |
|
Hi everyone, I just have a question whether these latest issues may have affected payouts at all or if I just didn't p2pool long enough? I managed to set up p2pool and bitcoin-qt server node on my local pc and it all connected and synchronized, but I couldn't connect to it with my miner, so after enough head-scratching I needed to get hashing again and tried a couple of public nodes and mined for approx 40hrs at around 180GH/s, mostly at http://196.2.147.115:9332 [16dAGWVSbxT3Zek84FuUMQGccfdyih8KrK] (that node eventually gave out) and http://78.27.191.182:8349 [1Ky5rbwSGVXvBQuqa7d7d49TnVmcM5Kaq2] among others, but I've received no payment at all and I'm sure at least one block was found during that time. I did jump around a bit while looking for the closest node with the lowest latency and shortest ping so that could have affected things. Does anyone know why I received nothing at all for the time I spent? Was I just not on long enough? Thanks for any clarification in advance!
|
Decentralize EVERYTHING!
|
|
|
smoothrunnings
|
|
January 22, 2014, 09:24:00 PM |
|
I think -f 50 is for the Windows version of P2Pool. I am running the Linux version.
It's the same on both. You can also use --fee 50. Thanks Krak! I do have one more question for you, do I need to remove the --give-author 0 command from the startup in order for the --fee 50 to work? Thanks That's the donation amount to forrestv. Totally separate from the fee to you. You really should put something more than 0 to be fair actually. Just like the fee parameter though, it's in percent so --give-author 0.25 is 0.25% donated. That makes sense. Sorry I am was going off the complete guide to setup P2Pool on Ubuntu that someone posted here. He never really explained it as you did what the --give-author was for.
|
|
|
|
nreal
Full Member
Offline
Activity: 932
Merit: 100
arcs-chain.com
|
|
January 23, 2014, 11:44:20 AM Last edit: January 23, 2014, 02:05:45 PM by nreal |
|
Has anyone any idea how to run p2pool with pp ? http://www.parallelpython.com/I think it could help boost performance, if its running on all cores instead of normal python is on one core only. This would be the case with intel atom 330 prosessors for example ( 4 threads - 2 cores) 4x1600 mhz. Installed p2pool on such a thing but there is peaks with 100% sometimes on one core, allthough the system is compiled with minimal gentoo -march=native... Tried that jython 2.7 but had problems with twisted web with it.. Have to run it on i7 4.5ghz 32gb ram for now
|
|
|
|
smoothrunnings
|
|
January 23, 2014, 12:35:42 PM |
|
What's the current payouts to default address reflect? Is that the pool's bitcoin address or the miners?
Also when does the "local rate reflected in shares" and peers graphs update?
Thanks
|
|
|
|
smoothrunnings
|
|
January 23, 2014, 12:41:29 PM |
|
Hi everyone, I just have a question whether these latest issues may have affected payouts at all or if I just didn't p2pool long enough? I managed to set up p2pool and bitcoin-qt server node on my local pc and it all connected and synchronized, but I couldn't connect to it with my miner, so after enough head-scratching I needed to get hashing again and tried a couple of public nodes and mined for approx 40hrs at around 180GH/s, mostly at http://196.2.147.115:9332 [16dAGWVSbxT3Zek84FuUMQGccfdyih8KrK] (that node eventually gave out) and http://78.27.191.182:8349 [1Ky5rbwSGVXvBQuqa7d7d49TnVmcM5Kaq2] among others, but I've received no payment at all and I'm sure at least one block was found during that time. I did jump around a bit while looking for the closest node with the lowest latency and shortest ping so that could have affected things. Does anyone know why I received nothing at all for the time I spent? Was I just not on long enough? Thanks for any clarification in advance! 1. if you have setup P2Pool using the defaults port 9332 is used for Bitcoin mining. 2. you have to be vigilant as there will be days where you see no payouts and other days were you see a lot of payouts; what I saying is P2Pool payout system doesn't work the same way as these fee based systems do. 3. make sure you open port 9333 on your firewall/router to your P2Pool server. 4. If your miners are on the same network as your server, use your internal address. Most firewall/routers don't permit you to go outside only to route back through.
|
|
|
|
freebit13
|
|
January 23, 2014, 12:58:24 PM |
|
Hi everyone, I just have a question whether these latest issues may have affected payouts at all or if I just didn't p2pool long enough? I managed to set up p2pool and bitcoin-qt server node on my local pc and it all connected and synchronized, but I couldn't connect to it with my miner, so after enough head-scratching I needed to get hashing again and tried a couple of public nodes and mined for approx 40hrs at around 180GH/s, mostly at http://196.2.147.115:9332 [16dAGWVSbxT3Zek84FuUMQGccfdyih8KrK] (that node eventually gave out) and http://78.27.191.182:8349 [1Ky5rbwSGVXvBQuqa7d7d49TnVmcM5Kaq2] among others, but I've received no payment at all and I'm sure at least one block was found during that time. I did jump around a bit while looking for the closest node with the lowest latency and shortest ping so that could have affected things. Does anyone know why I received nothing at all for the time I spent? Was I just not on long enough? Thanks for any clarification in advance! 1. if you have setup P2Pool using the defaults port 9332 is used for Bitcoin mining. 2. you have to be vigilant as there will be days where you see no payouts and other days were you see a lot of payouts; what I saying is P2Pool payout system doesn't work the same way as these fee based systems do. 3. make sure you open port 9333 on your firewall/router to your P2Pool server. 4. If your miners are on the same network as your server, use your internal address. Most firewall/routers don't permit you to go outside only to route back through. Thanks for the reply I had p2pool and bitcoin-qt set up on my pc which would be 192.168.1.3 and my miner on 192.168.1.99 and my router with the default gateway to 192.168.1.1. I can access my miner from my pc through the network, but the miner doesn't seem to be able to 'see' my PC (I tried a ping from within the user interface). I'm not sure if it's firewall issues or something like that I'll have to look a little deeper. I forwarded port 9332 on my router but that didn't make a difference and I saw in the tutorial that it was optional so didn't think it was too important. I just found it a little disheartening as I'd done most of the 40hrs on public nodes and didn't get a single satoshi... I would have liked to know if it was working just a little, but I guess I chose a bad 2 days I'm going to give it another go after the weekend once I get some new hardware as I'll at least have one miner hashing while I test with another. P.S. my understanding is that payouts to the default address would be payouts to the bitcoind wallet running on the server node, so it would be a pool fee on a public node or it would payout to your local wallet if it was your own installation.
|
Decentralize EVERYTHING!
|
|
|
smoothrunnings
|
|
January 23, 2014, 02:31:45 PM |
|
Hi everyone, I just have a question whether these latest issues may have affected payouts at all or if I just didn't p2pool long enough? I managed to set up p2pool and bitcoin-qt server node on my local pc and it all connected and synchronized, but I couldn't connect to it with my miner, so after enough head-scratching I needed to get hashing again and tried a couple of public nodes and mined for approx 40hrs at around 180GH/s, mostly at http://196.2.147.115:9332 [16dAGWVSbxT3Zek84FuUMQGccfdyih8KrK] (that node eventually gave out) and http://78.27.191.182:8349 [1Ky5rbwSGVXvBQuqa7d7d49TnVmcM5Kaq2] among others, but I've received no payment at all and I'm sure at least one block was found during that time. I did jump around a bit while looking for the closest node with the lowest latency and shortest ping so that could have affected things. Does anyone know why I received nothing at all for the time I spent? Was I just not on long enough? Thanks for any clarification in advance! 1. if you have setup P2Pool using the defaults port 9332 is used for Bitcoin mining. 2. you have to be vigilant as there will be days where you see no payouts and other days were you see a lot of payouts; what I saying is P2Pool payout system doesn't work the same way as these fee based systems do. 3. make sure you open port 9333 on your firewall/router to your P2Pool server. 4. If your miners are on the same network as your server, use your internal address. Most firewall/routers don't permit you to go outside only to route back through. Thanks for the reply I had p2pool and bitcoin-qt set up on my pc which would be 192.168.1.3 and my miner on 192.168.1.99 and my router with the default gateway to 192.168.1.1. I can access my miner from my pc through the network, but the miner doesn't seem to be able to 'see' my PC (I tried a ping from within the user interface). I'm not sure if it's firewall issues or something like that I'll have to look a little deeper. I forwarded port 9332 on my router but that didn't make a difference and I saw in the tutorial that it was optional so didn't think it was too important. I just found it a little disheartening as I'd done most of the 40hrs on public nodes and didn't get a single satoshi... I would have liked to know if it was working just a little, but I guess I chose a bad 2 days I'm going to give it another go after the weekend once I get some new hardware as I'll at least have one miner hashing while I test with another. P.S. my understanding is that payouts to the default address would be payouts to the bitcoind wallet running on the server node, so it would be a pool fee on a public node or it would payout to your local wallet if it was your own installation. If your miner can't see your PC then go into the firewall on your PC and or the AV firewall if you have one installed and either disable them both or add ports 9332 and 9333 to it. I have 280 ~ 290 GH/s on my pool. I started one of my avy's on a my friends Wallet ID because he wants to run it at his place; I have setup --fee at 50%; and my one avy 107GH/s has yet to show any BTC's.
|
|
|
|
smoothrunnings
|
|
January 23, 2014, 02:58:27 PM |
|
Hi everyone, I just have a question whether these latest issues may have affected payouts at all or if I just didn't p2pool long enough? I managed to set up p2pool and bitcoin-qt server node on my local pc and it all connected and synchronized, but I couldn't connect to it with my miner, so after enough head-scratching I needed to get hashing again and tried a couple of public nodes and mined for approx 40hrs at around 180GH/s, mostly at http://196.2.147.115:9332 [16dAGWVSbxT3Zek84FuUMQGccfdyih8KrK] (that node eventually gave out) and http://78.27.191.182:8349 [1Ky5rbwSGVXvBQuqa7d7d49TnVmcM5Kaq2] among others, but I've received no payment at all and I'm sure at least one block was found during that time. I did jump around a bit while looking for the closest node with the lowest latency and shortest ping so that could have affected things. Does anyone know why I received nothing at all for the time I spent? Was I just not on long enough? Thanks for any clarification in advance! 1. if you have setup P2Pool using the defaults port 9332 is used for Bitcoin mining. 2. you have to be vigilant as there will be days where you see no payouts and other days were you see a lot of payouts; what I saying is P2Pool payout system doesn't work the same way as these fee based systems do. 3. make sure you open port 9333 on your firewall/router to your P2Pool server. 4. If your miners are on the same network as your server, use your internal address. Most firewall/routers don't permit you to go outside only to route back through. P.S. my understanding is that payouts to the default address would be payouts to the bitcoind wallet running on the server node, so it would be a pool fee on a public node or it would payout to your local wallet if it was your own installation. The fee is share based not fee based you see on major pools. The way it currently works if you don't have the --fee or -f option enabled the wallet ID you use on your miners is were the payment goes to. When you have --fee or -f enabled the %50 of the shares which I am guess is figured out in bitcoin shows up in your Pool's wallet. the --give-author is for giving the developer of P2Pool a certain percentage of your mining.
|
|
|
|
smoothrunnings
|
|
January 23, 2014, 02:59:28 PM |
|
Can the armory be used on P2Pool with the Bitcond wallet?
|
|
|
|
freebit13
|
|
January 23, 2014, 03:17:57 PM |
|
Hi everyone, I just have a question whether these latest issues may have affected payouts at all or if I just didn't p2pool long enough? ...
1. if you have setup P2Pool... Thanks for the reply... If your miner can't see your PC then go into the firewall on your PC and or the AV firewall if you have one installed and either disable them both or add ports 9332 and 9333 to it. I have 280 ~ 290 GH/s on my pool. I started one of my avy's on a my friends Wallet ID because he wants to run it at his place; I have setup --fee at 50%; and my one avy 107GH/s has yet to show any BTC's. And boom, it's working! It was a combination of firewall and antivirus which is now sorted and I can connect I'm getting other errors now though, but I'll read through this topic again first before I ask any more questions. Thanks for the help smoothrunnings!
|
Decentralize EVERYTHING!
|
|
|
TierNolan
Legendary
Offline
Activity: 1232
Merit: 1104
|
|
January 23, 2014, 03:27:15 PM |
|
Can the armory be used on P2Pool with the Bitcond wallet?
You mean run Armory + p2pool + bitcoind all on the same machine? An interesting feature would be to allow Armory wallets to be used. Instead of an address, you would give it the chaincode and root public key. It could then generate new addresses every time you hit a share.
|
1LxbG5cKXzTwZg9mjL3gaRE835uNQEteWF
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
January 23, 2014, 03:54:43 PM |
|
Can the armory be used on P2Pool with the Bitcond wallet?
Of course
|
|
|
|
roy7
|
|
January 23, 2014, 04:02:20 PM |
|
Would a high performance p2pool be more limited by cpu or disk I/O?
|
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
January 23, 2014, 04:16:36 PM |
|
Would a high performance p2pool be more limited by cpu or disk I/O?
Bitcoin requires high cpu for a second on each new work
|
|
|
|
nreal
Full Member
Offline
Activity: 932
Merit: 100
arcs-chain.com
|
|
January 23, 2014, 05:01:27 PM |
|
Would a high performance p2pool be more limited by cpu or disk I/O?
P2pool is limited to only use 1 core, celeron does as good job as xeon, because its written in Python... Ssd helps bitcoind alot, and bitcoind uses all cores available - theres no issues with it. Theres small performance gain if bitcoind is on ramdisk vs ssd- not worth it.
|
|
|
|
smoothrunnings
|
|
January 23, 2014, 05:40:09 PM |
|
Looking at the graphs page on my P2Pool site I have some questions. I set one of my avy's to a different wallet ID. The avy does 106~107GH/s, I see the hashing graph which has -mean 106GH/s. The other bar graph below it that I guess is for the BTC's (it show's BTCs on my main wallet ID) is completely blank, there isn't even the slightest blue line. I wonder if this is a fault in the data making not appear normally or if it's something else? If you want to see what I mean have a look at my page. You can see the main wallet which shows the data under its hashing data, but the second one shows nothing under its hashing data. Thanks http://p2pool.smoothrunnings.ca:9332/
|
|
|
|
bitpop
Legendary
Offline
Activity: 2912
Merit: 1060
|
|
January 23, 2014, 05:47:09 PM |
|
Looking at the graphs page on my P2Pool site I have some questions. I set one of my avy's to a different wallet ID. The avy does 106~107GH/s, I see the hashing graph which has -mean 106GH/s. The other bar graph below it that I guess is for the BTC's (it show's BTCs on my main wallet ID) is completely blank, there isn't even the slightest blue line. I wonder if this is a fault in the data making not appear normally or if it's something else? If you want to see what I mean have a look at my page. You can see the main wallet which shows the data under its hashing data, but the second one shows nothing under its hashing data. Thanks http://p2pool.smoothrunnings.ca:9332/ How about here http://p2pool.smoothrunnings.ca:9332/static/graphs.html?Day
|
|
|
|
|