Topic: A Complete Guide to P2Pool - Merged Mining (BTC/NMC/DVC/IXC/I0C) plus LTC, Linux - page 14. (Read 198749 times)
August 16, 2013, 08:15:54 AM
All I0coin users need to upgrade, a hard fork will occur on 2013-09-01 0:00 UTC or block 895000 (whichever is earlier). Please upgrade to version 0.8.3-2. See https://bitcointalksearch.org/topic/anni0c-resurrection-memory-problems-and-instabilitiy-fixed-268228 for more information.
August 12, 2013, 09:08:07 AM
Guys ioc is back, group coin only Linux for now, bytecoin soon
August 12, 2013, 08:56:19 AM
No, you don't. Just use a dynamic DNS service like no-ip or dyndns.
I use no-ip.biz - it's free, and my router has a no-ip.biz client built in, so always updates the IP without my intervention.
same, I also use https://www.noip.com/ I use no-ip.biz - it's free, and my router has a no-ip.biz client built in, so always updates the IP without my intervention.
August 11, 2013, 05:27:12 PM
No, you don't. Just use a dynamic DNS service like no-ip or dyndns.
I use no-ip.biz - it's free, and my router has a no-ip.biz client built in, so always updates the IP without my intervention.
I use no-ip.biz - it's free, and my router has a no-ip.biz client built in, so always updates the IP without my intervention.
August 11, 2013, 12:04:10 PM
Hi, I wanted to start a p2pool, but do i need to Static IP, so other's can mine at my pool?
Sorry noob question.
.
Sorry noob question.
.
July 17, 2013, 04:30:08 PM
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
I decided to just fix it:
Quote
This fixes it for me:
https://github.com/hardcpp/P2PoolExtendedFrontEnd/pull/17
For watchers, until this pull is merged, feel free to use my repo:
https://github.com/yrral86/P2PoolExtendedFrontEnd
https://github.com/hardcpp/P2PoolExtendedFrontEnd/pull/17
For watchers, until this pull is merged, feel free to use my repo:
https://github.com/yrral86/P2PoolExtendedFrontEnd
Update: it still seems to be leaking a bit, but not nearly as bad
July 17, 2013, 12:13:27 AM
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
I decided to just fix it:
Quote
This fixes it for me:
https://github.com/hardcpp/P2PoolExtendedFrontEnd/pull/17
For watchers, until this pull is merged, feel free to use my repo:
https://github.com/yrral86/P2PoolExtendedFrontEnd
https://github.com/hardcpp/P2PoolExtendedFrontEnd/pull/17
For watchers, until this pull is merged, feel free to use my repo:
https://github.com/yrral86/P2PoolExtendedFrontEnd
July 16, 2013, 11:11:38 PM
That highly depends on the browser...
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
According to the bug report[1] it affects firefox and chrome.
1. https://github.com/hardcpp/P2PoolExtendedFrontEnd/issues/5
I haven't tried firefox, but I can verify the issue is there with the latest Chrome on 64 bit Linux.
July 16, 2013, 10:39:21 PM
That highly depends on the browser...
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
July 16, 2013, 10:35:49 PM
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
So you are aware, there is a memory leak currently if you use the auto-refesh option. It will eat all of your memory fairly quickly.
July 16, 2013, 10:33:08 PM
I was trying to find that for my install, but couldn't remember what it's called or where it's located. Thanks for the link!
Now that the P2Pool network is on v13, I've pointed one of my Jalapeños at it. So far, so good...efficiency and %DOA are better than they were with v11. If things keep going well and I get decent payouts over a week or two, I'll take the other Jalapeño off of BTCGuild and put it on P2Pool.
July 15, 2013, 09:35:13 PM
re: merged mining - is there any way to verify that merged mining is occurring with P2pool? I've launched it with the --merged option, giving it my namecoind info - and on P2pool's console display, I do see, every once in a while, "new merged mining work received" - or some message similar to that, but that's the only reference I can find to anything to do w/merged mining. Is that message indicating that merged mining is happening, or is there any other way to verify that I have indeed set merged mining up properly? Many thanks for your time!
As bitpop said, there's no other way unless you solve a block.
July 15, 2013, 01:41:48 PM
There's no other way. I've previously wished the site would show merged mining.
July 15, 2013, 01:03:08 PM
re: merged mining - is there any way to verify that merged mining is occurring with P2pool? I've launched it with the --merged option, giving it my namecoind info - and on P2pool's console display, I do see, every once in a while, "new merged mining work received" - or some message similar to that, but that's the only reference I can find to anything to do w/merged mining. Is that message indicating that merged mining is happening, or is there any other way to verify that I have indeed set merged mining up properly? Many thanks for your time!
July 14, 2013, 08:46:53 PM
There's is also a lower threshold where you won't get a payout (0.001BTC from memory) as it'd just be dust, so if you drop below that, you'll won't get the payout. That may explain why your shares appear to expire more quickly than they should.
July 13, 2013, 09:56:14 AM
i think i wasn't mining for about 1 hour, but that was 10 hours before the 1st cutdown.
what happedn over night i cannot tell...
this is really frustrating - hadn't that expirence when using a "normal" pool :-/
what happedn over night i cannot tell...
this is really frustrating - hadn't that expirence when using a "normal" pool :-/
Yes, p2pool is different than normal PPS (pay per share) pools. When averaged over a few weeks, you will receive a higher payout with p2pool than any other pool (assuming average efficiency). However, on a given day you will see lots of variance and shares expiring. That is the pool operating normally.
It will be frustrating the days you have bad variance. The new version of p2pool increases the lifetime of shares and makes it easier for ASICs to mine, so hopefully hashrate will increase and variance will decrease.
Actually, "normal" PPLNS pools such as BTC-Guild behave the same way as the frustrating experience you mentioned, it's just that their hashrate is so much larger you don't notice. This is what they are currently posting:
Average luck this difficulty is 106.65%. The following is the average luck per 10 shifts this difficulty:
112.47% 90.83% 104.68% 110.03% 110.16% 97.19% 122.84%
so BTC-Guild has some time periods where people are getting paid 10% less, and some where people are getting paid 22% more. Overall the variance is lower since they have more hashing power.
July 13, 2013, 04:56:09 AM
my shares expired in less than 24 hours
July 13, 2013, 04:47:22 AM
i think i wasn't mining for about 1 hour, but that was 10 hours before the 1st cutdown.
what happedn over night i cannot tell...
this is really frustrating - hadn't that expirence when using a "normal" pool :-/
what happedn over night i cannot tell...
this is really frustrating - hadn't that expirence when using a "normal" pool :-/
July 13, 2013, 03:59:29 AM
Were you mining the entire time? I left for a bit and only got .02 from .39. Shares expired quick.
July 13, 2013, 03:28:33 AM
okay, not as clear as i thought...
this night there definitly was a block found. Block was found at Sat Jul 13 2013 05:11:46 GMT+0200
My "current payout" fell from 0.0045 to 0.0024 and then from 0.0024 to 0.0
This is a little annoying. Hope someone can clearify this for me.
P2Pool log dump (Timezone GMT+2):
this night there definitly was a block found. Block was found at Sat Jul 13 2013 05:11:46 GMT+0200
My "current payout" fell from 0.0045 to 0.0024 and then from 0.0024 to 0.0
This is a little annoying. Hope someone can clearify this for me.
P2Pool log dump (Timezone GMT+2):
Code:
[...]
2013-07-13 01:14:10.149000 New work for worker! Difficulty: 0.999985 Share difficulty: 1782.842626 Total block value: 25.161641 BTC including 331 transactions
2013-07-13 01:14:11.336000 P2Pool: 17532 shares in chain (17537 verified/17537 total) Peers: 7 (1 incoming)
2013-07-13 01:14:11.337000 Local: 136MH/s in last 10.0 minutes Local dead on arrival: ~5.3% (0-25%) Expected time to share: 15.5 hours
2013-07-13 01:14:11.337000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0045 BTC
2013-07-13 01:14:11.337000 Pool: 1043GH/s Stale rate: 14.9% Expected time to block: 1.2 days
2013-07-13 01:14:11.646000 Peer sent entire transaction a966dddcc04c01503679672cb33da72dff8a1175745146155792b130cbf7057e that was already received
2013-07-13 01:14:11.844000 Peer sent entire transaction 4dc3bf6c331f007f62b1eb416b3c4084190fc192a3dfacc0e70f66900f7cb2fc that was already received
2013-07-13 01:14:24.925000
2013-07-13 01:14:24.957000 New work for worker! Difficulty: 0.999985 Share difficulty: 1766.749855 Total block value: 25.164841 BTC including 337 transactions
2013-07-13 01:14:26.380000 P2Pool: 17533 shares in chain (17538 verified/17538 total) Peers: 7 (1 incoming)
2013-07-13 01:14:26.380000 Local: 143MH/s in last 10.0 minutes Local dead on arrival: ~5.0% (0-24%) Expected time to share: 14.7 hours
2013-07-13 01:14:26.380000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0024 BTC
2013-07-13 01:14:26.380000 Pool: 1021GH/s Stale rate: 14.9% Expected time to block: 1.3 days
[...]
2013-07-13 05:00:38.976000 P2Pool: 17380 shares in chain (17384 verified/17384 total) Peers: 7 (1 incoming)
2013-07-13 05:00:38.977000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:38.977000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0024 BTC
2013-07-13 05:00:38.977000 Pool: 1272GH/s Stale rate: 16.5% Expected time to block: 1.0 days
2013-07-13 05:00:42.591000 Skipping from block 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 to block 9f1d549b3850204997415feab785580613967c766843207fc!
2013-07-13 05:00:42.595000
2013-07-13 05:00:42.604000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.079370 Total block value: 25.000000 BTC including 0 transactions
2013-07-13 05:00:46.418000 Skipping from block 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 to block 9f1d549b3850204997415feab785580613967c766843207fc!
2013-07-13 05:00:47.374000
2013-07-13 05:00:47.388000 New work for worker! Difficulty: 0.999985 Share difficulty: 1901.013053 Total block value: 25.000000 BTC including 0 transactions
2013-07-13 05:00:47.434000 Peer sent entire transaction 02238e1c363e30889b9faf4e34a630817d78b4dd5639deb7c5a86f9add7340b5 that was already received
2013-07-13 05:00:47.586000 Peer sent entire transaction 02238e1c363e30889b9faf4e34a630817d78b4dd5639deb7c5a86f9add7340b5 that was already received
2013-07-13 05:00:47.996000 P2Pool: 17381 shares in chain (17385 verified/17385 total) Peers: 7 (1 incoming)
2013-07-13 05:00:47.996000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:47.997000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-13 05:00:47.997000 Pool: 1271GH/s Stale rate: 16.7% Expected time to block: 1.0 days
2013-07-13 05:00:50.034000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:50.045000
2013-07-13 05:00:50.056000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.079370 Total block value: 25.000000 BTC including 0 transactions
2013-07-13 05:00:50.286000
2013-07-13 05:00:50.318000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.079370 Total block value: 25.170584 BTC including 359 transactions
2013-07-13 05:00:50.384000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:50.395000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:50.514000 Peer sent entire transaction 02238e1c363e30889b9faf4e34a630817d78b4dd5639deb7c5a86f9add7340b5 that was already received
2013-07-13 05:00:51.005000 P2Pool: 17380 shares in chain (17385 verified/17385 total) Peers: 7 (1 incoming)
2013-07-13 05:00:51.006000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:51.006000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0024 BTC
2013-07-13 05:00:51.006000 Pool: 1272GH/s Stale rate: 16.5% Expected time to block: 1.0 days
2013-07-13 05:00:55.378000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:55.384000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:55.964000
[...]
2013-07-13 05:00:38.976000 P2Pool: 17380 shares in chain (17384 verified/17384 total) Peers: 7 (1 incoming)
2013-07-13 05:00:38.977000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:38.977000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0024 BTC
2013-07-13 05:00:38.977000 Pool: 1272GH/s Stale rate: 16.5% Expected time to block: 1.0 days
2013-07-13 05:00:42.591000 Skipping from block 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 to block 9f1d549b3850204997415feab785580613967c766843207fc!
2013-07-13 05:00:42.595000
2013-07-13 05:00:42.604000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.079370 Total block value: 25.000000 BTC including 0 transactions
2013-07-13 05:00:46.418000 Skipping from block 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 to block 9f1d549b3850204997415feab785580613967c766843207fc!
2013-07-13 05:00:47.374000
2013-07-13 05:00:47.388000 New work for worker! Difficulty: 0.999985 Share difficulty: 1901.013053 Total block value: 25.000000 BTC including 0 transactions
2013-07-13 05:00:47.434000 Peer sent entire transaction 02238e1c363e30889b9faf4e34a630817d78b4dd5639deb7c5a86f9add7340b5 that was already received
2013-07-13 05:00:47.586000 Peer sent entire transaction 02238e1c363e30889b9faf4e34a630817d78b4dd5639deb7c5a86f9add7340b5 that was already received
2013-07-13 05:00:47.996000 P2Pool: 17381 shares in chain (17385 verified/17385 total) Peers: 7 (1 incoming)
2013-07-13 05:00:47.996000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:47.997000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-13 05:00:47.997000 Pool: 1271GH/s Stale rate: 16.7% Expected time to block: 1.0 days
2013-07-13 05:00:50.034000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:50.045000
2013-07-13 05:00:50.056000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.079370 Total block value: 25.000000 BTC including 0 transactions
2013-07-13 05:00:50.286000
2013-07-13 05:00:50.318000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.079370 Total block value: 25.170584 BTC including 359 transactions
2013-07-13 05:00:50.384000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:50.395000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:50.514000 Peer sent entire transaction 02238e1c363e30889b9faf4e34a630817d78b4dd5639deb7c5a86f9add7340b5 that was already received
2013-07-13 05:00:51.005000 P2Pool: 17380 shares in chain (17385 verified/17385 total) Peers: 7 (1 incoming)
2013-07-13 05:00:51.006000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:51.006000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: ]0.0024 BTC
2013-07-13 05:00:51.006000 Pool: 1272GH/s Stale rate: 16.5% Expected time to block: 1.0 days
2013-07-13 05:00:55.378000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:55.384000 Punishing share for 'Block-stale detected! 1f0cc62044901c7f7bcf233e47243df47e2ab18c3c05f5e9e3 < 9f1d549b3850204997415feab785580613967c766843207fc'! Jumping from 13268a6c to bc3f5e2c!
2013-07-13 05:00:55.964000
2013-07-13 05:00:55.995000 New work for worker! Difficulty: 0.999985 Share difficulty: 1895.115327 Total block value: 25.170584 BTC including 359 transactions
2013-07-13 05:00:57.012000 P2Pool: 17381 shares in chain (17386 verified/17386 total) Peers: 7 (1 incoming)
2013-07-13 05:00:57.012000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:00:57.013000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-13 05:00:57.013000 Pool: 1265GH/s Stale rate: 16.5% Expected time to block: 1.0 days
2013-07-13 05:01:00.271000 Peer sent entire transaction 18814d7840c29a424b82ee706a297b7db7f658c58e178486762de4611752e9f7 that was already received
2013-07-13 05:01:03.062000 P2Pool: 17370 shares in chain (17374 verified/17374 total) Peers: 7 (1 incoming)
2013-07-13 05:01:03.062000 Local: 107MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-21%) Expected time to share: 20.6 hours
2013-07-13 05:01:03.062000 Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficiency: ??? Current payout: 0.0000 BTC
2013-07-13 05:01:03.062000 Pool: 1265GH/s Stale rate: 16.5% Expected time to block: 1.0 days[/quote]
Jump to: