..
I'm not objecting but is it better if we have an hashpower criteria, e.g. if the pool hash reach 20g, then it's ok for the 24 shares bounty. So not every pool who has deploy the same code can apply this bounty.
The reason for the bounty is to see if Sidhujag's Daemon makes devcoin blocks that the old clients accept. We just need a single block for that. If it does, then we can make Sidhujag's the official client and archive the old one.
You really think its half the amount of work to test a pool than it is to develop the source? So does this mean he would have to dive into the source to figure out whats wrong if that os the case? Seems most of the hard work is in the code since that would be the problem and not the setup of a generic p2pool.
Calm down man, I think it's more hard work developing wallet than testing it, but having mining pool is also important.
I think I'd like to propose bounty of 12 shares every round for sidhujag, after his wallet made official and as long as he continuously maintain it.