A helpful sortable column would be "Date Established". I am always curious at the amount of time a coin has been alive. It'd probably be too much work to track down all the dates but it would help me sort the oldest, mature coins from the brand new coins just getting started.
Like a "founded" column or 1st block date. Just someway to STR coins by maturity.
+1
for the 'circa' column, simply 4 characters, month and year -- 1114 would be November 2014
Yep that would work!
Yep, I have all that in
DOACC (see sig) and in RDF to boot.
I ensured that each DOACC entry has an “incept date” of YYYY-MM. Yes, it
was a lot of work but I saw it as essential to DOACC. And, once completed, it's then well worth maintaining, at least from a disciplinary perspective if not a financial one.
It allows me to publish the altcoin launch graphs/graphics on Minkiz front page (
http://minkiz.co/). Another, less compelling, example of where I use it is in
Minki’s version of the bitcointalk
Sleepers list. The details are a bit rough'n'ready atm, still in “ninja launch” mode.
If Gliss is interested, we could use DOACC to backfill a “founded” column for all the altcoins currently listed at coinmarketcap (AIUI, assets have their own release date calendar courtesy of the asset issue mechanism), merely by posing an appropriate SPARQL query of the the DOACC RDF graph, along the lines:
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?node ?label ?symbol ?incept WHERE
{
?node skos:prefLabel ?label .
?node doacc:symbol ?symbol .
?node doacc:incept ?incept.
}
LIMIT 25
The only hiccough is a few differences in trading symbols, apparently inherited from the regrettable practice of major exchanges deciding to ignore the actual symbol specified in the bitcoinunits.cpp code.
For example, see Silkcoin, referenced as “SILK” on the exchanges --- and consequently in the coinmarketcap stats (
http://coinmarketcap.com/currencies/silkcoin/) --- which, if everybody had their druthers, is actually “SC” in the wallet code (
https://github.com/shnurf/silkcoin/blob/master/src/qt/bitcoinunits.cpp#L38).
For DOACC, I chose to go by the verifiable fact of what's actually specified in the C++ code.
For my occasional use of cross-referencing DOACC data with coinmarketcap data, I use a map (Python dictionary) of coinmarketcap symbols -> DOACC symbols. We'd turn the dictionary mapping into a separate graph of RDF statements and either use it to augment a copy of the main DOACC graph or act as a source for a federated query - both of which are fairly trivial to do.
btw, I'd say that your instincts are correct; given the calendarial flexibility of “ninja” launches, YYYY-MM is about as precise as you can sensibly get / need to be.
Cheers
Graham
