Can give more info ? I not good at reading code
For blocks chained before 76800, the 5-algo-chain qubit (function “Hash5” in the code) is used for producing the hashes. For blocks chained after 76800, a different hashing algorithm is to be used. Its name is “Hash3” reflecting the fact that it is a 3-algo-chain of LUFFA, CubeHash and ECHO, staying with the 512-bit output format. I've been giving the name “trisha” to 3-chain algos because I CBA to invent a name for each possible variation of a chain of 3 NIST algos.
For a chart showing the full range of PoW algos used so far that we know of in any alcoin we've recorded (pop. 1345) that weren't actually scams or just massive misunderstandings of the term “algorithm” <inhales with a gasp>, see:
http://minkiz.co/ (I'm about to add another 100 or so recent launches but I assume most people are up to date with the latest cryptobabble inventions).
The data for the chart is drawn from the DOACC dataset (see sig) and there is some (as yet
very limited) additional detail on the algos. The domain changes so rapidly that trying to follow it with web pages is just too punishing, so I'm necessarily reduced to providing a less immediately-helpful general presentation, i.e. a Linked Open Data explorer (think of it like an extended blockchain+transaction explorer) and a SPARQL endpoint.
Details will help ... The SPARQL endpoint is merely a query answering service available at a URL, ready to accept SPARQL queries via http. There's a form that provides a basic web interface:
http://minkiz.co/sparqlIf the following is pasted into the form ...
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?node ?p ?o WHERE {
?node rdf:type doacc:PoWscheme .
?node skos:prefLabel "trisha"@en .
?node ?p ?o .
}
and the Submit button clicked, the back-end RDF graph will be pattern-matched for all things of
type PoWscheme with a
SKOS preferred label[1] bound to the (
XSD-compliant) string
“trisha”@en. The
@en suffix distinguishes the string from other locale-specific values --- sorry, there's no bounty for a Chinese translation
But if you're minded to contribute, your compatriots will benefit. Apologies for the almost randomly-scattered links, my aim is to provide supportive links to the supporting foundations.
For convenience, here's a
query URL that resolves to the results page for that query (it's a GET, no POSTing required).
The unique URI for the node that satisfies the above pattern match is:
http://purl.org/net/bel-epa/doacc#D6accad6e-ce01-4819-b603-161e901e2cd1And the corresponding Linked Open Data (LOD) explorer page for that node is:
http://minkiz.co/page/PoWscheme/D6accad6e-ce01-4819-b603-161e901e2cd1(The reason I mention that specific page is that it demonstrates one of the advantages of LOD, the page also shows which altcoins have that node (i.e. the URI) bound to their powscheme relation. In this instance, Futurecoin, Metiscoin and Tjcoin also use a trisha3 hashing algo. The really neat thing about LOD is that this kind of dense information weaving just drops out naturally from the graph.)This is all fully Open Source. You can grab the graph, the ontologies and even the coin logos from the DOACC github repos and you can run your own Linked Open Data explorer by cloning rdflib-web (
https://github.com/RDFLib/rdflib-web, gromgull's Flask-based Python app) and feeding the DOACC graph to it.
(The rationale for this change, assuming a rationale is published, will make a fine entry in the book of Folkore Combiners.)
Cheers
Graham
[1] Props to the British Museum for using semantic web technology for handling the complexities of their catalogue
