Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 510. (Read 2591928 times)

And that I tried, but it only listed my previous transactions not the last one...
I have rebooted the system now and it shows me Current payout 0.0000 BTC! But my 0.03 BTC is nowhere to be found.
-Now I am just curious, but I can't see my IP on the http://p2pool-nodes.info/  ,before i could without a problem, and now I am nowhere to be found on that page.
I am using p2pool 13.1 - latest available version, this is the current output:

2013-07-16 12:54:24.291000 New work for worker! Difficulty: 0.999985 Share difficulty: 6777.639055 Total block value: 25.412776 BTC including 593 transactions
2013-07-16 12:54:24.320000 Peer sent entire transaction 4d2aa76d8457299c27e15625805b07fdf383b69bbfac9433b024132ab6c58bf3 that was already received
2013-07-16 12:54:24.493000 Peer sent entire transaction 4d2aa76d8457299c27e15625805b07fdf383b69bbfac9433b024132ab6c58bf3 that was already received
2013-07-16 12:54:25.486000 Peer sent entire transaction 4d2aa76d8457299c27e15625805b07fdf383b69bbfac9433b024132ab6c58bf3 that was already received
2013-07-16 12:54:25.954000 Peer sent entire transaction 4d2aa76d8457299c27e15625805b07fdf383b69bbfac9433b024132ab6c58bf3 that was already received
2013-07-16 12:54:27.061000 P2Pool: 21830 shares in chain (21853 verified/21853 total) Peers: 6 (0 incoming)
2013-07-16 12:54:27.061000  Local: 830MH/s in last 10.0 minutes Local dead on arrival: ~0.9% (0-5%) Expected time to share: 9.7 hours
2013-07-16 12:54:27.062000  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0000 BTC
2013-07-16 12:54:27.062000  Pool: 1359GH/s Stale rate: 15.3% Expected time to block: 23.0 hours
2013-07-16 12:54:33.423000 Peer sent entire transaction 4d2aa76d8457299c27e15625805b07fdf383b69bbfac9433b024132ab6c58bf3 that was already received
2013-07-16 12:54:35.306000 Peer sent entire transaction 4c172b9429fd107437a4d1f6dd78c8690b90a805d7b593c838fcb93088c3fdf7 that was already received

If you have specified the -a switch on the command line, your reward would have been paid to that address, if you have not specified the -a switch, then try:


Because p2pool be default will create a new account in your wallet called p2pool.

2013-07-16 10:56:46.087000  Pool: 1296GH/s Stale rate: 17.4% Expected time to block: 1.0 days
2013-07-16 10:56:46.600000 RECV forget_tx 203441d11900e188125735a7212358256b7d81765643ce2a105b90759e351a08c44cc8029f3f2cb bdcfb9261b2ef1b41fffa4ba20b83b2fe43a794623d6d9f7081b724b703
43ddd929435cbb9c22d6ae3f6f63c48c1650211e12da3022180a95d669d066...
2013-07-16 10:56:46.600000 > Error handling message: (see RECV line)
2013-07-16 10:56:46.601000 > Traceback (most recent call last):
2013-07-16 10:56:46.601000 >   File "twisted\internet\tcp.pyc", line 209, in _dataReceived
2013-07-16 10:56:46.602000 >
2013-07-16 10:56:46.602000 >   File "p2pool\p2p.pyc", line 144, in new_dataReceived
2013-07-16 10:56:46.602000 >
2013-07-16 10:56:46.603000 >   File "p2pool\util\p2protocol.pyc", line 27, in dataReceived
2013-07-16 10:56:46.603000 >
2013-07-16 10:56:46.603000 >   File "p2pool\util\datachunker.pyc", line 40, in _DataChunker
2013-07-16 10:56:46.603000 >
2013-07-16 10:56:46.603000 > --- ---
2013-07-16 10:56:46.603000 >   File "p2pool\util\p2protocol.pyc", line 55, in dataReceiver
2013-07-16 10:56:46.603000 >
2013-07-16 10:56:46.604000 >   File "p2pool\p2p.pyc", line 89, in packetReceived
2013-07-16 10:56:46.604000 >
2013-07-16 10:56:46.604000 >   File "p2pool\util\p2protocol.pyc", line 69, in packetReceived
2013-07-16 10:56:46.604000 >
2013-07-16 10:56:46.604000 >   File "p2pool\p2p.pyc", line 412, in handle_forget_tx
2013-07-16 10:56:46.604000 >
2013-07-16 10:56:46.605000 > exceptions.KeyError: 88667633989808334172075315019499562851243103342415615089331615202778526335284L
2013-07-16 10:56:46.621000 Peer sent entire transaction 36e8ec20c2ce10531174901cd61dd480c6847f8355fa49723b76bb165a0325bb that was already received
2013-07-16 10:56:46.657000 Lost peer 213.208.177.234:9333 -
2013-07-16 10:56:46.658000     Connection was aborted locally, using
2013-07-16 10:56:46.658000     L{twisted.internet.interfaces.ITCPTransport.abortConnection}.
2013-07-16 10:56:46.658000
2013-07-16 10:56:46.659000     @since: 11.1
2013-07-16 10:56:46.659000     .
2013-07-16 10:56:46.885000 Peer sent entire transaction bc01757e5bd9b40be1cbe868a954053a52ff39d370255d18d3871ab7a8cfa621 that was already received
2013-07-16 10:56:47.199000 Outgoing connection to peer 5.135.187.37:9333 established. p2pool version: 1300 '13.0-dirty'
2013-07-16 10:56:47.308000 Sending 1 shares to 5.135.187.37:9333
2013-07-16 10:56:47.369000 Peer sent entire transaction 36e8ec20c2ce10531174901cd61dd480c6847f8355fa49723b76bb165a0325bb that was already received
2013-07-16 10:56:49.101000 P2Pool: 18188 shares in chain (18192 verified/18209 total) Peers: 7 (0 incoming)
2013-07-16 10:56:49.102000  Local: 959MH/s in last 2.0 minutes Local dead on arrival: ~0.0% (0-13%) Expected time to share: 3.9 hours
2013-07-16 10:56:49.103000  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0365 BTC
2013-07-16 10:56:49.103000  Pool: 1296GH/s Stale rate: 17.4% Expected time to block: 1.0 days
2013-07-16 10:56:49.377000 Outgoing connection to peer 108.161.134.32:9333 established. p2pool version: 1300 '13.1'
2013-07-16 10:56:49.858000 Sending 1 shares to 108.161.134.32:9333
2013-07-16 10:56:49.859000 Peer sent entire transaction 9578db6386d5bc4533e797dbb1face2b82d0e44e4ebb03072487eac40bf19749 that was already received
2013-07-16 10:56:50.092000 Outgoing connection to peer 207.112.104.15:9333 established. p2pool version: 1300 '13.1'
2013-07-16 10:56:50.201000 Sending 1 shares to 207.112.104.15:9333
2013-07-16 10:56:50.621000 Peer sent entire transaction 36e8ec20c2ce10531174901cd61dd480c6847f8355fa49723b76bb165a0325bb that was already received
2013-07-16 10:56:50.658000 Peer sent entire transaction 035065ae847689c50bccd9f903586f203ce4095374d375b81b2b318767f77276 that was already received
2013-07-16 10:56:50.817000 Outgoing connection to peer 128.72.25.64:9333 established. p2pool version: 1300 '13.1'
2013-07-16 10:56:50.926000 Sending 1 shares to 128.72.25.64:9333
2013-07-16 10:56:52.106000 P2Pool: 18188 shares in chain (18192 verified/18209 total) Peers: 10 (0 incoming)
2013-07-16 10:56:52.106000  Local: 936MH/s in last 2.1 minutes Local dead on arrival: ~0.0% (0-13%) Expected time to share: 4.0 hours
2013-07-16 10:56:52.107000  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0365 BTC
2013-07-16 10:56:52.107000  Pool: 1296GH/s Stale rate: 17.4% Expected time to block: 1.0 days
2013-07-16 10:56:52.997000 Lost peer 87.106.130.46:9333 - Connection to the other side was lost in a non-clean fashion.
2013-07-16 10:56:53.259000 Peer sent entire transaction 943242e290722ac57fbc8d6ddb9d040b7c74b4d695e8a3c48d16d5ba33d8f16c that was already received
2013-07-16 10:56:53.284000 Peer sent entire transaction 9578db6386d5bc4533e797dbb1face2b82d0e44e4ebb03072487eac40bf19749 that was already received
2013-07-16 10:56:53.562000 Lost peer 62.217.124.203:9333 - Connection to the other side was lost in a non-clean fashion.
2013-07-16 10:56:53.568000 Peer sent entire transaction 9578db6386d5bc4533e797dbb1face2b82d0e44e4ebb03072487eac40bf19749 that was already received
2013-07-16 10:56:54.109000 Lost peer 134.76.63.170:9333 - Connection to the other side was lost in a non-clean fashion.
2013-07-16 10:56:54.109000 > in download_shares:
2013-07-16 10:56:54.110000 > Traceback (most recent call last):
2013-07-16 10:56:54.110000 > Failure: twisted.internet.error.ConnectionLost: Connection to the other side was lost in a non-clean fashion.
2013-07-16 10:56:54.110000 Requesting parent share 1d00d59f from 207.112.104.15:9333
2013-07-16 10:56:55.111000 P2Pool: 18188 shares in chain (18192 verified/18209 total) Peers: 7 (0 incoming)
2013-07-16 10:56:55.111000  Local: 948MH/s in last 2.1 minutes Local dead on arrival: ~0.0% (0-13%) Expected time to share: 3.9 hours
2013-07-16 10:56:55.112000  Shares: 0 (0 orphan, 0 dead) Stale rate: Efficiency: Current payout: 0.0365 BTC
2013-07-16 10:56:55.112000  Pool: 1296GH/s Stale rate: 17.4% Expected time to block: 1.0 days
2013-07-16 10:56:55.475000 Lost peer 78.155.217.76:9333 - Connection to the other side was lost in a non-clean fashion.
2013-07-16 10:56:55.475000 Outgoing connection to peer 168.7.116.243:9333 established. p2pool version: 1300 '13.1-65-g712fc88'
2013-07-16 10:56:55.671000 Sending 1 shares to 168.7.116.243:9333
2013-07-16 10:56:55.770000 Outgoing connection to peer 212.109.128.148:9333 established. p2pool version: 1300 '13.1-dirty'
2013-07-16 10:56:55.878000 Sending 1 shares to 212.109.128.148:9333

I have restarted the p2pool now, but everything is the same as before, cgminer is working as usual at ~800-900MH/s but i cannot see my payment from the last round anywhere!!!!

2013-07-16 03:39:45.269723 Outgoing connection to peer yyy:9333 established. p2pool version: 1100 '11.2-2-g77e7e2a'
2013-07-16 03:39:45.293332 Sending 1 shares to yyy:9333
2013-07-16 03:39:45.588460 Peer sent entire transaction 5cec85ad41343616556270deb9cf077b2778d09e7a7fa89399878b268a04b859 that was already received
2013-07-16 03:39:46.976918 P2Pool: 17361 shares in chain (17365 verified/17365 total) Peers: 52 (5 incoming)
2013-07-16 03:39:46.977012  Local: 3092MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-3%) Expected time to share: 3.9 hours
2013-07-16 03:39:46.977042  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~115.8% (23-116%) Current payout: 0.0476 BTC
2013-07-16 03:39:46.977085  Pool: 1430GH/s Stale rate: 13.7% Expected time to block: 21.8 hours
2013-07-16 03:39:47.896146 Peer sent entire transaction 3a1ddd2765944793edeb4dcd2a7be61685eaff0dd856808495f1feec18b5cfd1 that was already received
2013-07-16 03:39:47.929178 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:49.044352 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:50.181537 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:51.003735 Lost peer yyy:9333 - Connection was closed cleanly.
2013-07-16 03:39:51.193368 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:51.979040 P2Pool: 17361 shares in chain (17365 verified/17369 total) Peers: 51 (5 incoming)
2013-07-16 03:39:51.979116  Local: 3092MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-3%) Expected time to share: 3.9 hours
2013-07-16 03:39:51.979142  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~115.8% (23-116%) Current payout: 0.0476 BTC
2013-07-16 03:39:51.979185  Pool: 1430GH/s Stale rate: 13.7% Expected time to block: 21.8 hours
2013-07-16 03:39:52.250956 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:52.330319 Outgoing connection to peer xxx:9333 established. p2pool version: 1300 '13.1'
2013-07-16 03:39:53.253498 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:54.302421 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:55.350654 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:56.113690 Peer sent entire transaction 1db1ea7ae3fbc593ed7ec8870f9c8eb1e288187ebe06733a04711863b1496c9c that was already received
2013-07-16 03:39:56.353611 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:56.980966 P2Pool: 17361 shares in chain (17365 verified/17369 total) Peers: 52 (5 incoming)
2013-07-16 03:39:56.981065  Local: 3113MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-3%) Expected time to share: 3.8 hours
2013-07-16 03:39:56.981103  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~115.8% (23-116%) Current payout: 0.0476 BTC
2013-07-16 03:39:56.981148  Pool: 1430GH/s Stale rate: 13.7% Expected time to block: 21.8 hours
2013-07-16 03:39:57.499440 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:58.566415 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:59.616476 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:39:59.918335 Peer sent entire transaction 94c173ddf90264783b365ffc3c53dab4460adf003e561c96cebdc16ac5c1fd82 that was already received
2013-07-16 03:40:00.756978 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:02.020405 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:03.151937 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:04.282765 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:05.831979 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:06.943620 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:07.963221 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:08.241483 Peer sent entire transaction 8d4f2a7d7e3e4de991457d64d04c3cca0978854a9a0e77fac447d138d32b15d2 that was already received
2013-07-16 03:40:08.666502 Peer sent entire transaction 8d4f2a7d7e3e4de991457d64d04c3cca0978854a9a0e77fac447d138d32b15d2 that was already received
2013-07-16 03:40:09.059578 Requesting parent share fe187110 from xxx:10333
2013-07-16 03:40:10.190767 Requesting parent share fe187110 from xxx:9333
2013-07-16 03:40:11.309127 Requesting parent share fe187110 from xxx:10333
2013-07-16 03:40:11.998290 P2Pool: 17361 shares in chain (17365 verified/17369 total) Peers: 52 (5 incoming)
2013-07-16 03:40:11.998374  Local: 3092MH/s in last 10.0 minutes Local dead on arrival: ~0.0% (0-3%) Expected time to share: 3.9 hours
2013-07-16 03:40:11.998399  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~115.8% (23-116%) Current payout: 0.0476 BTC
2013-07-16 03:40:11.998434  Pool: 1430GH/s Stale rate: 13.7% Expected time to block: 21.8 hours

2013-07-16 03:46:55.207707 Skipping from block 43c3ddc118875cfd31e2a952fbde35a592b00e1dad2f44aba9 to block 61eddb9d93ce3a4d81b254949333e19e01a2e36591c80e077d!

^^ is when it finally stopped.  It's not a huge deal, except maybe if some of the peers I'm connected to are bandwidth starved, i.e.

http://nogleg.com:9332/static/graphs.html?Day

the 'Traffic Rate' graph


maybe you're on the p2pool fork that's at like 60ghash or w/e?

This is output of listtransactions

10:46:20

[
]

 

you have to wait 120 blocks, in bitcoind listtransactions it shows up as immature

I didn't got the payout

What is happening?!!?

sometimes I'll get an old version connect to me, and it'll request a parent share from it... then my client begins to request parent shares from these other IPs over and over.

has this happened to anyone else? 

i guess some code needs to be added to block v11?

3x share time = 3x share difficulty = shares last 3x longer in the share chain =
same payout per share, they are 3x harder to find, and "live" 3x longer

up until the limit of shares living for only 3 blocks are 3 days, whichever is shorter

jalapeno seems to be performing much better, 97% efficiency with <10% DOA right now. share time has jumped a bunch though, so sample size is still pretty low. is this just because the pool hashrate has gone up so much?

But cgminer don't show any accepted shares?! Only Rejected...

This is HARMLESS.
Share is counted anyway.

avalon still not working :-(

I use stock p2pool 13.1 windows executable and connect to it with username+200. all work is discarded in cgminer 3.3.1. P2pool don't get any share back.

If I use cgminer with --fix-protocol I get:

How long to 13.2?

Nice side-effect of hard-forking the P2Pool chain with a larger share interval: I noticed that the amount of network traffic as been significantly reduced at the time of the fork, more specifically the p2p-in amount (the p2p-out seems to be stable for me).

Note that may be relative to my observations: I use 8 incoming and 4 outgoing connections, my bitcoind configuration includes more transactions than average (aggressive settings as recommended in the guide in my signature) which may explain why I have a higher and more constant p2p-out across the fork (my node needs to forward these transactions to neighbors).

My efficiency as been reduced (edit: seems ~104% instead of the previous ~108% average) but this was the expected outcome of the fork (everybody should converge near 100% efficiency).

Ah, of course. If the shares are three times as hard to find, they will also be worth three times as much. P2Pool doesn't need to keep track of individual miners contributions at all. Thanks.

BFL jallepeno, flashed with a custom version 1.2.5 firmware. Used to have ~85% efficiency and 20% DOA. Now down to 6.5% DOA and~96.5% (63-111%) efficiency).

2013-07-15 03:52:31.495832  Local: 7135MH/s in last 10.0 minutes Local dead on arrival: ~6.5% (4-9%) Expected time to share: 1.2 hours
2013-07-15 03:52:31.496095  Shares: 12 (1 orphan, 1 dead) Stale rate: ~16.7% (4-45%) Efficiency: ~96.5% (63-111%) Current payout: 0.1248 BTC
2013-07-15 03:52:31.496307  Pool: 1418GH/s Stale rate: 13.7% Expected time to block: 22.0 hours



How it works: you will only get credit in the blocks that you get shares in.

If your node doesn't report any shares during a block, you won't get credit and other nodes won't know your are mining.

Yes it will even out. It will even out because when you do get a block, you will get exactly the compensation for the blocks you missed.

Example (made up numbers for demonstration)

before you would get .1 BTC per share, and find a share every 12 hours.

now you will get .3 BTC per share, and find a share every 36 hours.

BTC/hour is the same in both cases.

How does that work? If your node doesn't report any shares during a block, how does the other p2pool nodes know that you're mining? Will it really even out?

Share difficulty   9120 !!!
I hope it will get lower in next 48hrs as palnned. 9k is "bit" insane.

As others have already pointed out, I went back through my scrollback and saw when the fork happened.  It was at about 15:33 (in my US/Pacific timezone, so that's 22:33 UTC) on 14 July.  Nice!

I also noticed a disruption in network traffic.  My node lost 3 connections, and then they were almost immediately replaced by new connections elsewhere.  I am guessing this is P2Pool rejecting the obsolete nodes (below the fork's version cutoff) and kicking them out of the pool?

To see something interesting, look at your P2Pool graphs (on your localhost).

* In the "Desired version" graph, the little amount of red at the bottom has faded away, it's all blue now.  I'm guessing red was obsolete nodes (lower version)?

* In the "Pool rate" graph, there are less DOA/Orphan shares now, which is a good thing.  The pool is more green.  Still not perfect, but a big improvement.

* In the "Traffic rate" graph, there's a huge change.  There was a sudden spike near when the changeover happened, but that was a one-time thing.  Network traffic has nicely gone down a large amount.  It's about 1/3 what it was before, to reflect the new, slower, pace of share generation/synchronization.

Interestingly, the expected time for my node to find a single share, is now longer than the expected time for P2Pool to find a Bitcoin block!  Previously, it was the other way around.  Guess that means that my node will fall out of blocks entirely (0 shares/block) but that's the price to be paid for finding blocks more often, so in the long term it should even out.

I'm glad the changeover went smoothly!  If it were me, I would have been really nervous when it happened, crossing my fingers, especially since such a dramatic change to a distributed network is a tough thing to fully test in advance...!

Josh

forrestv said 13.2 is coming soon which will be necessary for Avalon mining now that p2pool BTC is past the fork.  Keep an eye on #p2pool for news.