I have covered the PoS resource usage problem on the slimco.in website in
the Proof of Stake guide. (Graham, correct me if there's something wrong)
Nothing wrong that I can see, looks good. Maybe an idea to include a reference to AizenSou’s post on the old thread:
https://bitcointalksearch.org/topic/m.7716530 Fwiw, amongst other things, I'm working my way through all 250-odd pp of the old thread with an aim of collating the technical comments into a coherent whole.
On another matter, I'm pleased to report a significant amount of progress (admittedly the result of a significant amount of effort).
The Slimcoin-specific version of ACME is close to achieving deployment status, it now displays all Slimcoin tx (inc the
genesis transaction) and inscriptions:
spin-off material: a PR for the website: the anatomy of the Slimcoin genesis block
Front page
Latest transactions
Geoip-location map of countries hosting Slimcoin nodes (canned, from copy'n'pasta of server-hosted client's response)
And the one that took up most of the effort ... a list of inscriptions on mainnet:
Those following along closely at home will note the inclusion of the SPARQL raw response and draw their conclusions accordingly - the blockchain has been mapped into RDF (
Apache Jena + Fuseki) and is available for the resolution of SPARQL queries.
I have a
blocknotify script in Python that updates the RDF graph with freshly-minted blocks+tx as they occur. Initially, I ran it in “catchup” mode, dumped the blockchain as ntriples and read it into Jena's TDB using the command-line utility.
Fuseki has happily been hosting the Slimcoin RDF blockchain for a week or so and I've been firing assorted SPARQL queries at it --- it's doing okay thus far.
Of course, the *real* firework display is yet to begin. Now that we have an RDF model of the blockchain, inscriptions can be
signature hashes of RDF graphs. This means that you will be able to inscribe the signature of an arbitrary RDF graph and the metadata contained in the graph can be retrieved and used to decorate/accompany the inscription with appropriate metadata content such as the title, author, date, price, thumbnail, snippet, contract id, actually *anything* that you can express in RDF, which is pretty much anything at all.
Cheers
Graham