Merged mined SHA256 coins all need the same thing as a basis that they all have in common: a copy of bitcoin with the merged mining as a secondary chain patches applied.
maybe possibly NaMeCoin might be too different from bitcoin to base on that, but all the others, even DeVCoin, can update relatively simply, the kind of cut and paste / search and replace hacks the spamcoin makers do to make each day's daily dose of new spamcoins.
So basically they have all been waiting for "mergecoin",
https://github.com/knotwork/Mergecoin which is simply the latest bitcoin with the merged mining as a secondary chain patches applied.
unfortunately those patchs do not apply cleanly to recent bitcoin versions, plus when i was part-way through applying them bitcoin itself updated again in response to some threat or security hole or whatever, so now the bitcoin it is based on is itself already out of date.
The patches I manually managed to get to apply were the easy ones though. It won't be much to re-apply those to an even newer copy of bitcoin.
Where the process has stalled so far is where the change to leveldb instead of Berkeley DB took place and i don't know what past that as I was looking at the rejected chunks one at a time.
i have only worked with much older versions of Bitcoin before so someone more familiar with recent versions can probably apply those parts much easier than I could, plus I have backlogged way too many things to be able to get back to that for qutie a while.
But once it is done, any scamcoin cut and paste kidde can update all the merged-mined coins from that, incuding updating all the Bitcoin clones such as Bytecoin and Terracoin into merged mined coins by similarly cloning them from it.
-MarkM-
