jc12345 suggests …
I would still recommend that the work on 0.10+ should continue and that the differentiating factor of vcoin is its closeness to Bitcoin providing traceability to the Bitcoin core and compatibility with Bitcoin value added services, but with enhanced specs like the quicker block time and so on.
Just too keep folks in the loop, I PM’d jc12345 with thanks for the comment, insights, kind words and indicated that I shared the above viewpoint.
Ever keen not to shut off opportunities to contribute hash to the rate, I decanted the 0.8 getwork code into a separate branch, haven’t had time even to assess the amount of effort likely to be involved in re-integrating the approach to the 0.11 structure (assuming that the 0.11 structure isn’t now basically inimical to the principles underpinning the getwork approach).
I have strong reasons to believe that the folks who have developed a fancy for following the monthly P&D Sheeplechase Trophy will take a while to cotton on to the fact that newly-launched 0.8.x clones are basically using obsolete code and represent a poor offer to put before P&D punters, let alone any hypothetical genuine investors.
Anyway, in lieu of anything coherent w.r.t. to progress, this is my current reading/working focus:
https://bitcointalk.org/index.php?topic=623147.0 <- CLAMS’ OP_RETURN ClamSpeech feature
https://bitcointalk.org/index.php?topic=1102062 <- Trent Russell’s Multisig Derivatives
https://bitcointalk.org/index.php?topic=1078338.0 <- Discussions of approximations of a decentralised exchange
https://bitcointalk.org/index.php?topic=1085436.0;all <- Compact Confidential Transactions for Bitcoin
https://bitcointalk.org/index.php?topic=322828.msg11383992#msg11383992 <- a Skeincoin-based OP_RETURN service
https://bitcointalk.org/index.php?topic=1070124.msg11452127#msg11452127 <- Synergy’s OP_RETURN service
https://github.com/viacoin/viacoin/pull/23 <- ViaCoin’s OP_CHECKLOCKTIMEVERIFY implementation.
https://github.com/ElementsProject/elements/commits/checklocktimeverify <- Elements’ OP_CHECKLOCKTIMEVERIFY implementation
I dunno, if this stuff really was as good as it’s made out to be, I’d have thought there’d be a lot more fuss over it.