@cryptovore: That's awesome! I fully support that. I unfortunately can't help developing (I had even to google what a VM does in the cryptocurrency space), but if you need someone to test it later, I'm in.

@gjhiggins: A little question ... I have installed a Fuseki instance to provide the Slimcoin RDF block chain, mainly for my own web2web tests, for now, but also as an block explorer API. A couple of weeks ago you mentioned a Python blocknotify script you have written that "translates" the block JSON structure from the Slimcoin client into the RDF structure used in your CCY ontology. Can this script be downloaded or could you upload it publicly so I can use it? (I could write a similar script but why invent the wheel two times ...) Is your CCY ontology "stable" or are you still working on it?

@muf18: Regarding your pessimism on usage: I think that only can grow in a gradual way. We're just starting a bit of marketing, have now a pretty stable client and a website, but that wasn't so half a year ago. My hopes for web2web and similar technologies lie in bringing uncensorable web sites. I see a high potential for authoritarian countries, because w2w is so simple to use and doesn't require an installation (like ZeroNet, Maidsafe, IPFS etc. does), and we could get a first mover advantage if we're the first cryptocurrency that is using that technology on a larger scale and promoting it.

For a very simple example, we could hash regularly an updated Wikipedia snapshot into the Slimcoin chain and distribute the snapshot via torrent for our Chinese and Turkish friends where Wikipedia is blocked or restricted. Accessing that snapshot via a Slimcoin address would be much easier than having to search an updated snapshot via Google every couple of weeks.

Regarding increasing the OP_RETURN field to 1 MB, I have thought a little bit about it. My preliminary stance is:
- one single OP_RETURN transaction should not be able to fill a whole block, so the maximum I would allow are about 500 kB per transaction. That would be more than enough for long, compressed text files, such as descriptions of inventions, property records, etc. I would be more happy with 100 kB maximum that also should be enough for most use cases.
- and even then, I would only support such a high limit if you can prove (with at least a "rudimentary" market study) that there is demand for it. I was a long time active in the NXT community where they can load up to 40 kB (see here) of arbitrary data into a transaction. But this feature is barely used. And you said Datacoin also has only a 2 GB blockchain (simliar to Slimcoin's), so demand to store data seems not very high. So I remain skeptic, and cryptovore seems to have the same opinion.
- As I said, I have no problem of allowing OP_RETURN data transactions up to 1 kB, as long as the 1 MB block size limit is not touched.