No I wrote that they got the initial boost for being the first to trying micro-tipping, but that micro-tipping is fundamentally flawed as a paradigm, thus as the initial hype fades and everyone who has tried micro-tipping now realizes it is just a one-time delusion that can't be repeated.
Thank you for sharing your assessment. To be brutally frank, it dodges the main question and it's too uninformed an explanation to be useful (I don't consider pundits’ opinions to be authoritative) but thank you for making the effort. It has to be obvious that an “initial boost” cannot be currently sustaining the strong performance two years down the road so we're right back where we started. But that's just my peccadillo, staying focused on the awkward questions and trying to understand what the answers might mean. Cheers Graham |
|
|
|
Appears that Dogecoin's marketing strategy has no long-term legs ...
I can understand how it might appear so to observers outside the domain. You're opting for the “coincidence” explanation, then? Cheers Graham |
|
|
|
marketing competence has been lax at best.
Read “non-existent, with one notable exception” as I've yet to encounter anyone who appears to share an appreciation of the details of Jackson Palmer's input to the design of Dogecoin. I suspect this lack of appreciation is leading people to ascribe to sheer coincidence the fact that out of over 2500 altcoins launched, Dogecoin is the only coin with an inarguably vibrant community and is also the only coin where a senior marketing professional was involved in the creation. It isn't coincidence. Cheers Graham |
|
|
|
One of the more specific research goals of the genesisExtractor is to see if the coinURI format remains collision-free.
(no 2 coins receive the same coinURI)
It looks like the format is fine, but can we really say by just having looked at 50 coins?
I got the impression that solid mathematical proof will be required for a solution to be deemed acceptable for this particular problem in this particular domain. You will want to consider the issue of duplicate pchMessageStart character arrays (“magicbytes” in your terminology), some of which have already appeared in the posted results on the Spreadcoin forum:
f9beb4d9495fab29 - bitcoind8333;
f9beb4d9495fab29 - omnicore-qt8333;
fbc0b6db4e8eaab9 - feathercoin-qt9336;
fbc0b6db4e8eaab9 - litecoind9333;
I can assure you there are many other instances. Net result, half the data in the proposed magicbytes+datestamp referent is profoundly unreliable and so is unfortunately and inconveniently inappropriate for the intended purpose of contributing to a unique identifier, even a domain-limited one. That's a bummer but I think it would be unwise to try and ignore the implications. Also, I'd be hugely grateful if you could avoid (ab)using the term “coinURI” after I mentioned its prior use in the already-published open source CCY cryptocurrency ontology. I'd much prefer to avoid the sowing of unnecessary potential confusion. TIA. Cheers Graham |
|
|
|
All in all, this is just a casual work, and I appreciate any help to keep it current.
I maintain an off-board list of exchanges which I'm gradually building out: https://minkiz.co/exchangeThe main data is published as Open Source in RDF: https://github.com/DOACC/dat/cryptocurrencyexchanges.ntThis allows people to create their own lists using a straightforward SPARQL query: PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX foaf: <http://daml.umbc.edu/ontologies/cobra/0.4/foaf/>
PREFIX cce: <http://purl.org/net/bel-epa/cce#>
SELECT ?label ?url
FROM <https://raw.githubusercontent.com/DOACC/individuals/master/cryptocurrencyexchanges.nt>
WHERE {
?node a cce:CryptocurrencyExchange .
?node skos:prefLabel ?label .
?node foaf:page ?url .
?node cce:extant true .
} ORDER BY ?label
Here's a clickable url that re-posts the query to the Minkiz SPARQL endpoint and forwards to the results which can simply be copied and pasted or processed further, e.g. trivially reformatted in editor as BBcode, copy'n'pasted (Note Panamanian 1Ex.Trade debut): The data's in a Github repository in (recently) N3 format - coupla sample entries to show it's not rocket surgery: cce:D0627ab78-bce8-49d0-803c-598559b89987 a cce:CryptocurrencyExchange ;
foaf:page <https://www.mercadobitcoin.com.br> ;
dc:title "Mercado Bitcoin"@en ;
cce:api "listing"@en ;
cce:countryprofile geo:Brazil ;
cce:extant true ;
cce:fiat true ;
geo:codeISO2 "BR"^^xsd:string ;
skos:prefLabel "Mercado Bitcoin"@en .
cce:Dff55cae5-a4bb-4ec3-a460-f71bfa7e72c0 a cce:CryptocurrencyExchange ;
foaf:page <https://www.cryptsy.com> ;
dc:title "Cryptsy"@en ;
cce:api "listing"@en ;
cce:countryprofile geo:United_States_of_America ;
cce:extant false ;
geo:codeISO2 "US"^^xsd:string ;
skos:prefLabel "Cryptsy"@en .
Pull requests, issues, collaborators welcome. Cheers Graham |
|
|
|
Another view (excluding the overwhelming heavyweights), last 24 hrs BTC vol (> 1) for CN-based exchanges (red) vs Rest of World (blue)  (for 2016, despite the thread title) Cheers Graham |
|
|
|
But if you were to add spreadcoin's coinURIs to your DOACC then we could reuse ALL your data within the blockexplorer.  That’s neither desirable nor necessary. The “giant database” over-simplification is doing you a disservice. DOACC is expressed as an RDF graph and the effect you describe can be achieved quite straightforwardly by creating a graph of Spreadcoin referents linked to DOACC's referents, such as the one I created from the postings to the Spreadcoin forum thread and dropped onto pastebin. SPARQL trivially enables querying the union of the graphs. Minki (a savvy lass) provides a SPARQL endpoint configured to use the DOACC dataset as default graph. If the Spreadcoin reference is : <http://purl.org/net/bel-epa/ccy#C9aeefa4f-c5e8-4056-8b8c-99da124ad07a> then the query would be: PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
PREFIX ccy: <http://purl.org/net/bel-epa/ccy#>
PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT ?doaccuri ?label ?symbol ?algo
FROM <http://pastebin.com/raw/UQZdHtiP>
WHERE {
ccy:C9aeefa4f-c5e8-4056-8b8c-99da124ad07a ccy:cryptocurrency ?doaccuri .
?doaccuri skos:prefLabel ?label .
?doaccuri doacc:symbol ?symbol .
?doaccuri doacc:pow ?ps .
?ps skos:prefLabel ?algo .
FILTER LANGMATCHES(LANG(?label), "EN")
}
Here's a clickable version of the SPARQL query URL that performs the search and forwards to the results page. As regards terminology, the CCY ontology uses the term “coinURI” to model the coin payment URIs, e.g. bitcoin:12A1MyfXbW6RhdRAZEqofac5jCQQjwEPBu?amount=1.2&message=Payment&label=Satoshi&extra=other-param
Cheers Graham |
|
|
|
So the difference between your project and mine is:
Yours is a giant database regarding the "Description of a Cryptocurrency".
While the "altcoin taxonomy" project is about giving coins a unique collision-free identifier (coinURI), derived simply by reading its blockchain.
The goal is to tie the "blockchain of a coin" to the "design of a coin" (what is in DOACC) with the use of those coinURIs.
I thought you might be able to re-use the DOACC coinURIs but I was mistaken. Cheers Graham |
|
|
|
I'm currently working on a semi-automated characterisation of coin features.
Cool list. I think it could be perfect, if we had a topic to compare features and how they are used in alt-coins Something like this?: https://bitcointalk.org/index.php?topic=675821.msg13484427#msg13484427(and the three following posts) Here's the current feature set, including the “anon” features, rendered in N3. The next step is to hack up some code to inspect and report on repository content and ultimately derive a feature set from the data, mostly satisfying BitcoinNational's requirement. @prefix dc: <http://purl.org/dc/elements/1.1/> .
@prefix doacc: <http://purl.org/net/bel-epa/doacc#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@prefix foaf: <http://daml.umbc.edu/ontologies/cobra/0.4/foaf/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
doacc:Dcbd6cd89-dd4b-4350-9827-2a7c6a073df9 a doacc:CryptocurrencyFeature ;
dc:description "Zerocoin was initially proposed as an extension to add true cryptographic anonymity ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "zerocoin"@en .
doacc:D524d6200-09b3-4607-a47b-e02a8e72db85 a doacc:CryptocurrencyFeature ;
dc:description "Anonymous facility"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "anon"@en .
doacc:D38b9e224-7490-4424-8182-74ec5dd76fa5 a doacc:CryptocurrencyFeature ;
dc:description "Encrypted messaging"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "encrypted messaging"@en .
doacc:Ddfe4de7a-d688-4ca5-8743-4c03f2861b16 a doacc:CryptocurrencyFeature ;
dc:description "Encrypted chat"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "encrypted chat"@en .
doacc:Dfe415608-22ec-4abb-8453-179b83ae51bc a doacc:CryptocurrencyFeature ;
dc:description "Tor is free software and an open network that helps you defend against traffic analysis..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
owl:sameAs <http://dbpedia.org/resource/Tor> ;
skos:prefLabel "tor"@en .
doacc:Ddcdd9f05-b977-4911-8c4e-f0d0049aa462 a doacc:CryptocurrencyFeature ;
dc:description "I2P is an anonymous network, exposing a simple layer that applications can use to anonymously..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
owl:sameAs <http://dbpedia.org/resource/I2P> ;
skos:prefLabel "i2p"@en .
doacc:D490f13de-0400-47dd-8e6a-d39cff3d4ddb a doacc:CryptocurrencyFeature ;
dc:description "Anonymous chat"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "anon chat"@en .
doacc:D8350d907-10c6-4f36-835c-5af6147ce1b7 a doacc:CryptocurrencyFeature ;
dc:description "Stealth addresses"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "stealth addresses"@en .
doacc:D8350d907-10c6-4f36-835c-5af6147ce1b7 a doacc:CryptocurrencyFeature ;
dc:description "Multi-platform anonymous cryptographic SMS transaction sending technology..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "stealthtext"@en .
doacc:D8350d907-10c6-4f36-835c-5af6147ce1b7 a doacc:CryptocurrencyFeature ;
dc:description "Cryptograhic blockchain analysis resistance and obfuscation technology on the..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "stealthsend"@en .
doacc:Dbb59764d-fc10-4407-a11c-80f6156dee34 a doacc:CryptocurrencyFeature ;
dc:description "Blockchain inscription, 24-character limit"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "char[24]"@en .
doacc:D00a7c073-3ccf-403b-bcdb-e0c3887b32e8 a doacc:CryptocurrencyFeature ;
dc:description "Uses Cloak implementation"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "cloak"@en .
doacc:D89b123e6-e8a7-49b0-b760-a1b1f0de74d4 a doacc:CryptocurrencyFeature ;
dc:description "Aspiring to anonymous faeatures"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "aim"@en .
doacc:D428b68ae-3b9b-419f-a71f-902ef78a2cc5 a doacc:CryptocurrencyFeature ;
dc:description "The CoinJoin-inspired dark* performs mixing with selected “masternodes” ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "dark"@en .
doacc:Dcfd6eb63-0bb6-4725-b727-83347f6817cb a doacc:CryptocurrencyFeature ;
dc:description "Uses CryptoNote protocol"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
owl:sameAs <http://dbpedia.org/resource/CryptoNote> ;
skos:prefLabel "cryptonote"@en .
doacc:Ddfa006a5-3143-414f-bc76-6ff67b7583ac a doacc:CryptocurrencyFeature ;
dc:description "TCP network connections are secured using the Elliptic Curve Cryptography (ECC) ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "secured protocol"@en .
doacc:Dc638bc03-b495-48cb-9171-e7fb034d802c a doacc:CryptocurrencyFeature ;
dc:description "SuperSend Trustless is an advanced p2p completely decentralized anonymous system..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "super"@en .
doacc:Dc638bc03-b495-48cb-9171-e7fb034d802c a doacc:CryptocurrencyFeature ;
dc:description "Cryptonite"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "nite"@en .
doacc:Da3efdd95-7c34-4dba-b3f4-4446849d058d a doacc:CryptocurrencyFeature ;
dc:description "Teleport is a set of blockchain technologies built on top of Bitcoin Dark (BTCD), ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "teleport"@en .
doacc:Dbb26104b-12fc-4a53-82f1-d94d8c4b8d51 a doacc:CryptocurrencyFeature ;
dc:description "CoinJoin is an anonymization method for bitcoin transactions proposed by Gregory Maxwell..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
foaf:page <https://en.wikipedia.org/wiki/CoinJoin> ;
skos:prefLabel "coinjoin"@en .
doacc:D6e937391-180e-4a30-b1aa-f54fbc102e65 a doacc:CryptocurrencyFeature ;
dc:description "Burst transaction is a built-in algorithm that allows the user to divide a transaction ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
foaf:page <https://en.wikipedia.org/wiki/CoinJoin> ;
skos:prefLabel "bursttx"@en .
doacc:D9f29ed28-1353-468b-af7a-fe2b70f208c3 a doacc:CryptocurrencyFeature ;
dc:description "A multi-signature address is an address that is associated with more than one ECDSA ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
foaf:page <https://en.wikipedia.org/wiki/Multisignature> ;
skos:prefLabel "multisig"@en .
doacc:D7f4471a2-9f19-4b3a-b584-35c3cc62f5f6 a doacc:CryptocurrencyFeature ;
dc:description "Zero-Knowledge Proof: In cryptography, a zero-knowledge proof or zero-knowledge protocol ..."@en ;
rdfs:comment "Zero-Knowledge Proof is a very new, very speculative field with few if any academic research ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
owl:sameAs <http://dbpedia.org/resource/Zero-knowledge_proof> ;
skos:prefLabel "zkp"@en .
doacc:D6893e506-b166-4d9d-b28e-fa205a60fc0e a doacc:CryptocurrencyFeature ;
dc:description "In cryptography, a ring signature is a type of digital signature that can be performed by any ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
owl:sameAs <http://dbpedia.org/resource/Ring_signature> ;
skos:prefLabel "ring signature"@en .
doacc:D6ad4f544-b664-41fb-befa-20a1edfc3ec2 a doacc:CryptocurrencyFeature ;
dc:description "SonicVortex V2.0 is a way to hide encrypted transactions by steganography. You take a picture, ..."@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "vortex"@en .
doacc:D2d587f6d-d082-419c-b680-6c53a354e396 a doacc:CryptocurrencyFeature ;
dc:description "Confidential transactions are a feature of the Elements experimental client"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "confidential tx"@en .
doacc:D5210d1ba-e7ea-4c86-b67b-e4eefb7858d9 a doacc:CryptocurrencyFeature ;
dc:description "Uses Counterparty implementation"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "counterparty"@en .
doacc:Dac65a7cb-5937-458b-9ce1-921ec2616f8e a doacc:CryptocurrencyFeature ;
dc:description "Uses Dash implementation"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "dash"@en .
doacc:Db21b3cfc-e7e1-41bc-961e-15ba0832da9f a doacc:CryptocurrencyFeature ;
dc:description "Anonymised transactions via sending through a delegate mixer"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "delegate"@en .
doacc:Dd25e8125-d697-4215-8df2-32a3fea8249d a doacc:CryptocurrencyFeature ;
dc:description "Transactions anonymised via sending through a mixer"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "mixer"@en .
doacc:D70c14962-85f9-489d-ae8b-621d3a3785d4 a doacc:CryptocurrencyFeature ;
dc:description "Multiple signatures"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "multisig"@en .
doacc:D960aec4c-e103-46ea-9d53-81a2e3d3c2ac a doacc:CryptocurrencyFeature ;
dc:description "Uses NXT implementation"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "nxt"@en .
doacc:D09ed8154-2708-4c8a-b347-4b9b15df117a a doacc:CryptocurrencyFeature ;
dc:description "Secure messaging"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "secure messaging"@en .
doacc:Dd707fd92-3224-4b45-9b2e-1df0ce9a74bb a doacc:CryptocurrencyFeature ;
dc:description "Uses Shadow implementation"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "shadow"@en .
doacc:D10cb5f38-ea01-4116-937c-af5e913bd3b5 a doacc:CryptocurrencyFeature ;
dc:description "Shadowchat"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "shadowchat"@en .
doacc:Df212fa7d-cb96-4a6e-bf27-f7da007c834c a doacc:CryptocurrencyFeature ;
dc:description "Stealth messaging"@en ;
rdfs:isDefinedBy <http://purl.org/net/bel-epa/doacc> ;
skos:prefLabel "stealth messaging"@en .
is an altcoin catalogue expressed in RDF and the features described above can be combined with the DOACC altcoin metadata and is amenable to SPARQL querying so people can generate their own permutations of lists. For each altcoin, DOACC attempts to record: - name - the name of the coin
- ticker - the stock ticker
- protocol - the network protocol
- protectionscheme - how the chain is protected
- incept - YYYY-MM of announcement
- date_founded - the date that the coin was announced
- block_time - the block time in seconds
- powscheme - the hashing scheme
- block_reward - the block reward
- reward_modifier - the reward halving/modification scheme
- premine - the amount of any premine
- total_coins - the total number of coins
- retarget_time - the block target time
- website - the coin’s web site
- source - the location of the source code
- posscheme - the type of PoS scheme used
- confirmations - the number of confirmations recommended
- maturation - the maturation time of newly-minted blocks
- distributionscheme - the scheme by which the coin was distributed
But the older data is often much more sparse. I have an experimental version of the graph that cross-references each coinmarketcap.com-listed coin with the corresponding marketcap, volume, price etc in the coinmarketcap.com listings so I can also use those values as filters. Cheers Graham Edit: truncated the dc:description string, for sanity |
|
|
|
some body can get a work link on a CPU miner please
Wallet GUI should work, as should vanilla RPC as [set|get]generate commands remain enabled in the Chaincoin Core upgrade: $ ./chaincoind setgenerate true 2
$ ./chaincoind getmininginfo
{
"blocks" : 651954,
"currentblocksize" : 27299,
"currentblocktx" : 1,
"difficulty" : 0.07937460,
"errors" : "",
"genproclimit" : 2,
"networkhashps" : 3906285,
"pooledtx" : 1,
"testnet" : false,
"generate" : true,
"hashespersec" : 21868
}
Seems to be working okay according to the debug log. If you'll forgive me, I'll skip waiting for the 1/42 hash ratio to pay off. Cheers Graham |
|
|
|
Temporary url of the rendered above table with links (c.f. chain icon) to the full DOACC metadata entry for the coin --- which includes the repos URL for those who prefer to DYOR. https://minkiz.co/dashboard/anoncoinsCheers Graham |
|
|
|
I'm currently working on a semi-automated characterisation of coin features. As “anon” is programmatically challenging and the characterisation is significant in the domain, a bit of hand-stitching is tolerable. Here's what I have thus far ... | name_symbol_as_bctlink, | blockchain_state, | incept_YYYY-M, | “anon”_features. | | Acecoin (ACE) | foundered | 2014-07 | tor | | Aeon (AEON) | listed | 2014-06 | cryptonote | | Anoncoin (ANC) | listed | 2013-06 | i2p, tor | | ASAPcoin (ASAP) | foundered | 2014-07 | cryptonote | | Bata (BTA) | listed | 2015-05 | i2p, tor | | BitBlockcoin (BBL) | foundered | 2014-06 | dark | | Boolberry (BBR) | listed | 2014-04 | cryptonote | | Bytecoin (BCN) | listed | 2014-03 | cryptonote | | Masoncoin (BROS) | unlaunched | 2014-08 | coinjoin | | BitsharesX (BTSX) | listed | 2014-02 | confidential tx, stealth addresses | | Burnercoin2 (BURN) | foundered | 2014-07 | tor | | ECash (CASH) | foundered | 2015-02 | dark | | Cloak (CLOAK) | listed | 2014-05 | cloak | | CannabisDarkcoin (CND) | foundered | 2014-04 | secure messaging | | Concealcoin (CNL) | listed | 2014-07 | bursttx | | CryptoNotecoin (CNN) | unlaunched | 2014-07 | cryptonote | | Crypto (CTO) | listed | 2015-04 | stealth addresses | | Darkcoin (DARK) | listed | 2015-03 | dark | | DarkScrypt (DASC) | unlaunched | 2015-04 | dark | | Dash (DASH) | listed | 2014-01 | dash | | DarkBit (DB) | foundered | 2015-05 | secure messaging | | DarkCrave (DCC) | foundered | 2015-05 | secure messaging | | DarkCypher (DCYP) | listed | 2015-10 | secure messaging, anon chat, stealth addresses, char[24] | | Darknetmarketcoin (DNM) | foundered | 2014-07 | cloak | | DarkNetCoin (DNC) | listed | 2014-10 | cryptonote | | DogeCoinDark (DOGED) | listed | 2014-10 | i2p, tor | | Darkpay (DRKPY) | unlaunched | 2015-05 | teleport | | Droidz (DRZ) | listed | 2015-04 | dark | | DarkShibe (DSB) | listed | 2014-10 | stealth messaging | | Dashcoin (DSH) | listed | 2014-07 | cryptonote | | DarkCash (DSK) | foundered | 2015-10 | dark, shadowchat | | Ethancoin (ETHAN) | foundered | 2014-07 | dark | | Fantomcoin (FCN) | listed | 2014-05 | cryptonote | | Fibrecoin (FIBRE) | listed | 2014-08 | tor, dark | | Flaxcoin (FLAX) | listed | 2015-06 | dark | | Fusecoin (FUSE) | foundered | 2014-07 | mixer | | HansaCoin (HANSA) | foundered | 2015-01 | stealth addresses, stealth messaging | | ICash (ICASH) | listed | 2015-03 | dark | | Infinium-8coin (INF8) | foundered | 2014-07 | cryptonote | | Joincoin (J) | listed | 2014-08 | tor | | Jadecoin (JADE) | foundered | 2014-08 | tor | | LittleDarkcoin (LTD) | unlaunched | 2014-10 | dark | | Mammothcoin (MAMM) | foundered | 2014-06 | super | | MultiCoin (MC) | defunct | 2014-07 | multisig | | MillenniumCoin (MIL) | listed | 2015-03 | delegate | | Moneta (MONET) | listed | 2015-10 | zerocoin | | MountCoin (MNT) | defunct | 2014-06 | cryptonote | | Navajocoin (NAV) | listed | 2014-07 | delegate | | NTXcoin (NTX) | listed | 2014-05 | nxt | | NextCoin (NXT) | listed | 2013-11 | nxt | | RobotSexNickelscoin (RSN) | defunct | 2014-07 | tor | | Redwire (RW) | defunct | 2014-07 | tor, nite | | Razor (RZR) | listed | 2014-06 | tor | | ShadowCash (SDC) | listed | 2014-07 | shadow | | QuietCoin (SHH) | foundered | 2014-08 | cloak | | Singularity (SING) | foundered | 2014-06 | tor | | Sling (SLING) | listed | 2015-04 | dark | | Soundbit (SND) | inactive | 2014-07 | dark | | Solecoin (SOLE) | listed | 2014-08 | aim | | SonicScrewdrivercoin (SSD) | listed | 2014-08 | tor, stealth messaging, vortex | | Supercoin (SUPER) | listed | 2014-05 | super | | FedoraCoin (TIPS) | listed | 2013-12 | mixer | | Tomatocoin (TMT) | foundered | 2014-06 | dark | | Transfercoin (TX) | listed | 2015-08 | tor, dark | | Venturecoin (VENT) | foundered | 2014-07 | tor | | Vanillacoin (VNL) | listed | 2014-12 | secured protocol | | Vertcoin (VTC) | listed | 2013-01 | stealth addresses | | Anonymouscoin (XAC) | foundered | 2014-05 | aim | | BitMocoin (XBM) | foundered | 2014-08 | stealth, mixer | | Counterparty (XCP) | listed | 2014-02 | counterparty | | duckNote (XDN) | listed | 2014-05 | cryptonote | | Monero (XMR) | listed | 2014-04 | cryptonote | | Stealthcoin (XST) | listed | 2014-07 | tor, stealthsend, stealthtext | | Zerovert (ZER) | foundered | 2014-11 | zerocoin |
Cheers Graham |
|
|
|
Technical features
i'm willing to do a bounty to research the major coins to get wallet and core details data, then convert it into nice visual reps like the above
Treading this same path for my own porpoises. Too many issues need to be resolved for a hand-executed version to be both i) useful and ii) maintainable, it does need to be automated and that will require conceptual rigour --- which is where the utility lies. My approach is to iteratively refine a set of string matches until the desired data is accurately and reliably read out of the source code repository. Step 1 is to sieve coinmarketcap.com's list of currencies for bitcoin-protocol PoW coins. Step 2 is to backfill any missing source code repositories. Currently working on the back-filling. The posting limitations inhibit coherent reporting of detail. See subsequent posts for details Edit: An html-formatted table is available, will load directly into LibreOffice Calc: https://minkiz.co/library/poschar.htmlIf this content is viewed as inappropriate for the thread, speak up and I'll migrate it to another. Personally, I can just about make an argument for it being smart-related because of the rigour it demands. If anyone feels like contributing some reconciliations, pick a rank range and advertise it, so that work isn't duplicated (I'm working my down from the top). All that's needed is the tracked-down github url paired with the minkiz url of the coin so I can just spool them into the db. It'll get written into the open-source DOACC RDF graph ultimately, to act as a public resource. At the moment, the list includes only those alts that are listed on an exchange polled by coinmarketcap.com. I guess there will be “major” PoW coins that aren't listed on an exchange but I suspect that they're few in number. Suggestions on a postcard, please ... Cheers Graham |
|
|
|
I just saw that Ybcoin ... hard to find information about the coin ... Any useful information ...?
Not much, I'm afraid: https://minkiz.co/coin/254/incept - 2013-06
protocol - bitcoin
symbol - YBC
protectionscheme - pos
thread - 243046.0
website - http://www.ybcoin.org/
total_coins - 200000000
premine - 0
powscheme - scrypt-j
name - YbCoin
expiration - listed
posscheme - interest
date_founded - 2013-06-26
distributionscheme - pow
source - https://github.com/ybcoin/ybcoin
description - YAC Clone, multi-hash based cryptocoin with dynamic re-targeting,
25 coins per block, and 200 million total coins. Yuan Bao Coin - YuanBaoCoin
Abbreviation: YBC Algorithm: SCRYPT Date Founded: 6/26/2013. Novacoin-based.
Cheers Graham |
|
|
|
|
Show Posts
