Peer sent entire transaction *hex* that was already received about p2pool

[forrestv]

It's due to latency. Multiple peers want you to have a transaction that they're now mining but you don't have yet, so they all send it to you at the same time. This could be solved by adding a small delay before forwarding a transaction at the cost of increased latency should they find a share or block... I'll think about it.

[Rav3nPL]

Sample log only from 10 mins:
http://pastebin.com/WmVZTfGu
It is alot of wasted bandwidth.
Maybe do it this way:

• share received -> check for txes inside, do I have all?
• yes -> noop
• no -> ask 1 peer for it (preferably peer that send share?), wait 10 sec for response, check again bitcoind and ask another peer if need.

Maybe all this "duplicates" are because bitcoind is gathering txes "in mean time" while we wait for data from peers?