I'm curious did you see this same issue when you upgraded your pool from v0.3.24 to v0.8.6? It should have occurred then too, right?
BIP30 is for preventing duplicate transactions so I assume it wouldn't be an issue with every single block generated. Are you seeing 'tried to overwrite transaction' errors on every block?
Also, I believe the majority of pool hasing power for iXcoin is still using v0.3.24. How do we get the rest of the pools migrated to v0.8.6 or v0.9.x without causing a fork? The start date in v0.8.6 is already in the past. Or is this even a fork issue?
I didn't see it in 0.8.6 and it's not causing the block to be rejected. Possibly it's something to do with the testing setup I've done - I'll check and ensure the transactions aren't being propagated multiple times. I'll confirm here in a day or so when I can retest.
I thought the other pools were on 0.8.6? It's been a while since it's been done and mmpool has been using it since confirming it could merge mine blocks successfully.
Edit: Friction clarified whether 0.8.6 was deployed. mmpool runs it but I have no issue with modifying the BIP 16/30 start dates.
The biggest issue seems to be the transactions not appearing in listtransactions. I'll do more testing as well and will experiment with sending a portion of the pools hashrate to the 0.9.x client at some point.