Hey Graham I couldn't help but notice
https://minkiz.co in your personal text area.
What is that website all about? It seems confusing.
I'm pleased you asked that question
It's still very much in development but it's intended as an experiment in self-funding art. Banksy has Dismaland, we have Minkiz.
Unfortunately, I managed to nuke the CSS framework and several exhibits on the live server via an ill-conceived upgrade so am a bit adrift in terms of explaining what it’s all about. Anyways, atm I'm slowly revising the CSS framework usage but have been interrupted by events.
The different coin lists and charts are rendered from metadata directly obtained from DOACC's semweb RDF graph (but see below), they're just an HTML rendering of the metadata. ACME is a nearly-finished RPC-based block explorer implemented in Python with an RDF back-end that allows me to just spool the blockchain and tx into an RDF graph if I wish. The Linked Open Data explorer and SPARQL query facility are just public convenience access points for those who, for various reasons, don’t find it convenient to work with their own local copy of the DOACC RDF graph.
The Foundry is a complex piece, its overt aspect is rather a tongue-in-cheek swipe at the shallow models underlying “algo frenzy” by purporting to offer click'n'drool coin cloning. In doing so, it highlights just how little the difference can be between one altcoin and another. The web forms presenting the parameters draw from the DOACC metadata collection, so (at least for those coins that are fairly straightforward clones) you could, in theory, take the “economic profile” of a coin as rendered by the form and impose it on a fresh codebase to reproduce the coin --- the correct genesis block hash would be re-generated, it'd effectively be a seamless upgrade.
Of course, to be able to do that, you'd need to have the C++ sources available in template form so that replacement of parameter values is properly controlled. Well, the insider joke is ... I
do have those templates (for 0.8, Core 0.9, 0.10 and, recently, 0.11 versions). The Foundry does actually work and, when allowed to do so, generates perfectly-functioning 0.11 altcoins of nearly all the algos offered.
I’m also minded to work up a full UI, give the user a choice of diff smoothing modifier (KGW, DGW, etc), reward schedule, etc. The list isn't endless, it models the few choices that devs are usually capable of offering but I believe I can also offer a range of GUI enhancement add-ons such as a block explorer, IRC tab, etc.
And that does include 0.11 versions, e.g. this from a current side-project that includes Mr Spread's enhanced blockchain browser, the bog-standard Bittrex trading tab re-purposed for use with Bleutrade (using the new financial charts from the recently-upgraded qcustomplot library) and a couple of “network health” charts. (Not shown is the “cryptlane” in-wallet market for which only the UI is functional because at this point I don't wish to muck about with extending the blockchain until I've got a better understanding of the implications for block size):
I anticipate that the more ambitious services that are currently being planned/implemented will result in users having raised expectations about the range of functionality and support available in a contemporaneous wallet but the vanilla 0.11 GUI is still something of a misplaced exercise in utilitarianism.
As an aside ... the DOACC data is overdue an update, I have data for another coupla hundred recently-launched alts to add but again, I got interrupted by events - I discovered that a static GH pages installation would actually do what I had in mind for DOACC's documentation, so I followed CLAMs lead and developed an open source version:
https://github.com/DOACC/DOACC.github.io which uses JS to illustrate what can (trivially) be done with the RDF graph. It renders reasonably well even if it does hammer the browser:
http://DOACC.github.ioshould come over as a little less haphazardly organised than Minkiz
HTH
Cheers
Graham
