Quote from: Richy_T on April 24, 2013, 01:32:45 AM

Quote from: forrestv on April 22, 2013, 11:52:07 PM

Quote from: Richy_T on April 22, 2013, 11:33:02 PM

What is the definitive way to see when a non orphaned block has been generated by p2pool?

Quote from: forrestv on June 17, 2011, 11:14:22 AM

List of all blocks found: http://blockexplorer.com/address/1Kz5QaUPDtKrj5SqW5tFkn7WZh8LmQaQi4

Anyone know what's up with blocks 219190 and 219192 (and probably others) in there? I'm wanting to do some screen scraping and while I can handle that, it's meaning a lot more data is being pulled back than needs to be.

They appear to be transactions where forrestv consolidated a zillion small inputs into a single larger output (to make them easier to spend in the future).

FYI, if you are writing code to find p2pool blocks, I found that it was much easier to get data from blockchain.info' API in json format than to try to screen scrape the HTML from blockexplorer.

p2pool.info's logic for finding p2pool blocks is:

1. Looks at every new block as it is found and examines the generation transaction and see if a) it has the donation address, b) has the weird script at the end, and c) has at least 25 outputs (this filters out p2pool forks that have only a few people mining on them)

2. Every once in a while looks at all of the transactions for the donation address looking for generation transactions that it doesn't already know about (because they came in way late and are probably orphans.