I believe the
MC2 guys are working on incorporating something like this into their coin.
This looks interesting, the whitepaper is promising.
I don't see any actual product here, seems like just a bunch of ideas without any progress.
There's also a relatively new project called
NEX which seems to be some sort of fork of Nxt.
This looks like just a barely tweaked version of Nextcoin, I don't think they will have any significant feature if Nxt doesn't have it.
it seems like they are working on an efficient blockchain pruning algorithm, which is completely different to the mini-blockchain scheme.
You mean they are working on dropping the old transactions with used outputs instead of maintaining the balance tree?
I don't know much at all about Ethereum but it seems to be the complete opposite of the mini-blockchain scheme, like I mentioned in the video.
Ok, I have to admit that I haven't watched the entire video, having read and understood your wiki already. But then it is not clear what exactly the mini-blockchain scheme covers in your interpretation. I thought the main idea is to be able to drop the old blocks by maintaining a hash-tree of the relevant, up-to-date data. Anything above that (scripting or other app layers) is just icing on the cake. I am not sure why you would be against such implementations?
And your Polymium proposal sounds very much similar to Etherum with its claim to support "user-defined applications" so I don't see how you are going to be able to incorporate the mini-blockchain scheme into such a design. I would appreciate an explanation for how you believe it could be possible.
Dropping the scripting layer and replacing it with a hard-wired coin script pretty much results in your scheme. Actually the script I mostly use for testing implements a very similar coin, so making that script the only valid one makes the system behave very-very similar to what you describe. (though I only started researching the already published suggestions after more-or-less coming up with the basics, but we pretty much arrived to the same conclusions in the main points) So instead of the rigid user-balance tree, the tree can store almost any kind of data, but it's managed very similarly. (This is also true for ethereum, the differences between that and my scheme start after this part)