Algorithm: SHA256
Which one? SHA1-256, SHA2-256 or SHA3-256? Cheers Graham |
|
|
|
Kudos to you working on all this!
@gjhiggins: yeah man, awesome wallet development, keep up the good work. I'll take a closer look. Thanks for the kind words but 'sno big deal, I'll give you a summary preview: some eye candy, plus a nothing-special, slightly buggy implementation of a primitive IRC terminal that no-one would choose over an actual IRC messaging app. The fact that the trading tab is limited to Bittrex cuts across the principle of decentralisation and a cool appraisal leads me to conclude that it hardly justifies the effort of including it, (I was really just checking its ease-of-use). And, as I suspected, the encrypted in-wallet messaging uses the block chain so a hard fork will be required. Is the argument for in-wallet encrypted messaging sufficiently compelling to justify the cost of a hard fork and a permanent inflation of the block chain? Cheers Graham |
|
|
|
I'll go ALL IN when spreadcoin gets its encrypted in-wallet messaging system. I WANT IT SO MUCH!
Oh? I'd be interested in your use case, i.e. “why?” fwiw, I'm playing around with an experimental Spreadcoin wallet with some additions: gussied-up icons, Bellacoin's diff history chart, Banksycoin's in-wallet IRC and [Talk|Chat]coin's encrypted messaging (the latter working only on testnet thus far). As with the in-wallet block explorer, the in-wallet chat is accessed via menu (the penultimate item: "Chat Window")  and presented in a separate window:  leading to the (by now fairly standard) in-wallet IRC messaging:  I originally submitted an exploratory PR, adding Bella's difficulty chart to the overview page, Mr Spread thought it'd be better placed on the mining page, here's the candidate:  Alert readers will have noted the appearance of a “Trade” option, again adapted from an existing in-wallet trading implementation. It's fairly primitive, limited to Bittrex and I haven't had chance to check its functioning as yet but now that SPR is listed on BIttrex, it seems to be working largely as expected:  Finally, an adoption of the Talkcoin/Chatcoin encrypted in-wallet messaging --- very early days for this, I've only just decanted the code and it only works on the testnet atm:  It's important to note that these are merely “suck it and see” experiments with no particular ambition to be included in an “official” release (whatever that might be in a p2p context), largely because so many of these nice ideas ultimately prove to be more trouble than they're worth and there's no substitute for actually getting your hands dirty and having a go at finding out. Neither the Trade tab nor the in-wallet encrypted messaging is yet fit to be seen in public so they remain unpublished for the time being ... but gussied-up icons, a diffplot and an IRC chat window are basically just cosmetic (a fork is not required) so if you fancy joining in with the experiment, you can check out and compile the cpuminer1.2.trial branch: https://github.com/gjhiggins/spreadcoin/tree/cpuminer1.2.trialCheers Graham Edit: not last, penultimate |
|
|
|
I had to resync, but now I am stuck at block 111988 ... the block explorer is on block 205177+, so there must be a way ...
14:58:53

getpeerinfo
14:58:53

[
{
"addr" : "107.181.250.217:41682",
"services" : "00000001",
"lastsend" : 1420642706,
"lastrecv" : 1420642706,
"conntime" : 1420642546,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 205220,
"banscore" : 0
},
{
"addr" : "188.226.131.93:41682",
"services" : "00000001",
"lastsend" : 1420642705,
"lastrecv" : 1420642705,
"conntime" : 1420642547,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 205220,
"banscore" : 0
},
{
"addr" : "37.187.100.75:41682",
"services" : "00000001",
"lastsend" : 1420642705,
"lastrecv" : 1420642705,
"conntime" : 1420642549,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 205220,
"banscore" : 0
},
{
"addr" : "104.131.114.226:41682",
"services" : "00000001",
"lastsend" : 1420642705,
"lastrecv" : 1420642705,
"conntime" : 1420642555,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 205220,
"banscore" : 0
},
{
"addr" : "5.9.81.9:41682",
"services" : "00000001",
"lastsend" : 1420642705,
"lastrecv" : 1420642705,
"conntime" : 1420642555,
"version" : 60003,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"height" : 205220,
"banscore" : 0
}
]
HTH Cheers Graham |
|
|
|
Sorry to be the bearer of bad news but the CHC ticker is already in use by an exchange-listed coin (Chaincoin). There is a list of symbols -> names: https://minkiz.co/coin/symbol/and one for names -> symbols: http://minkiz.co/coin/name/HTH Cheers Graham Edit: CHCcoin is incorrectly listed as also using the CHC ticker, it is actually CHCC. An update is scheduled for later today. |
|
|
|
if you wanted to make that kind of list you should have named it that way.
You named it LIST of SHA256 COINS.
Profitable, dead or whatever doesn't matter then right?
I still think you should add those other 2 atta2k15 told u about.
Or change the subject of this topic...?
Alternatively, here's a comprehensive list of altcoins sorted by hashing algo, derived from the DOACC metadata collection: https://minkiz.co/coin/algoCheers Graham |
|
|
|
Our goal is to decentralize the Singularity
You can lose the “Brain-Engineering” white paper, it's tinfoil hat grade and you'd be horribly mistaken if you believe that it has a positive effect. In essence, the coin aims to support the funding of AI research yet is based on an appeal to the popular but sadly doomed hope of the appearance of a prophetsingularity that will, as if by magic, solve all the currently-blocking AI problems. This fundamental contradiction between ends and means is the root of an incoherence that will prove ultimately fatal to the coin; the cracks are already beginning to show: This project is in its early days - all feedback is welcome.
If your smarty pants friends have some specific smart criticism - we'd love to hear it.
Cheers Graham |
|
|
|
By modifying the blockchain ... we plan create a ... archive of time stamped, attributable and contextualised plain-text and encrypted data.
ISTM that “attributable” and “contextualised” will present you with a stiff challenge in terms of operational definition and subsequent implementation. Elsewhere there are similarly-undefined terms such as “notarise”, “scientific methodology”, “courtroom objectivity”, “monitored and evaluated for integrity”, “appropriate and accountable manner”, “smart conflict resolution incentives”, etc, etc. All these nebulous terms will have to be nailed down to actual operational definitions in order to gain the precision and coherence necessary for addressing transparency issues. And, at least until you've made a preliminary pass over these domain issues, it'll be nigh-impossible to create a reliable roadmap. I have form on this. I'm exploring some ideas in the related area of transparency data published by the UK Parliament: https://owl-o-parl.org. It's currently in temporary suspension, pending the accumulation of enough cryptocurrency to set up a faucet labelled: "EARN REAL INTERNET MONEY JUST FOR CHECKING A FEW FACTS ABOUT PARLIAMENT". (The transparency reporting is essentially trustworthy, the facts don't need checking. The faucet is primarily intended as a means of bribing people to expose themselves to facts about Parliament. Research from psychology suggests that voters' reported negative perceptions of MPs are only weakly held and can collapse on simple exposure to facts. Given the mess that UK politics is in, I reckon it's at least worth trying.)Cheers Graham |
|
|
|
According to our records, the final total of altcoin launches for 2014 is 1667 (including parodies, failures, etc). The graph now contains some coins launched in 2015, requiring the query for a 2014 total to be date-limited fore and aft: PREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT (COUNT(?node) AS ?coins) {
?node doacc:incept ?yearmo
FILTER(?yearmo > '2013-12' && ?yearmo < '2015-01' )
}
^^^^^ results as clickable URLCheers Graham |
|
|
|
If you position the mouse cursor over the little blue ticket icon, a pop-up dialog will give you a precise calculation
Those calculations have been fixed in the newest client.
I think you must be running an old version of the client.
Ah, many thanks. I wasn't aware that I was behind the curve. Updated.  Cheers Graham |
|
|
|
if i have only 50 clams its very hard to stake now in my own wallet? is it better to move to just-dice to stake?
If you position the mouse cursor over the little blue ticket icon, a pop-up dialog will give you a precise calculation, e.g.:  >>> 626513 / 365
1716.4739726027397
So I shan't be holding my breath  Cheers Graham |
|
|
|
it'd be good to know which ones are ... listed on exchanges
It's not perfect information and it's too long to reproduce here but there's a list of SHA2-256 coins and their status here: https://minkiz.co/coin/algo It's just a fancy presentation of the DOACC ( https://github.com/DOACC) dataset, readily queryable on https://minkiz.co/sparql from which you can construct your own lists by posing SPARQL queries along the lines of this example: 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 ?label ?incept ?expiration WHERE
{
?ps rdf:type doacc:PoWscheme .
?ps skos:prefLabel "SHA2-256"@en .
?pt rdf:type doacc:Protocol .
?pt skos:prefLabel "bitcoin"@en .
?node doacc:protocol ?pt .
?node doacc:pow ?ps .
?node skos:prefLabel ?label .
?node doacc:incept ?incept .
?node doacc:expiration ?expiration .
}
ORDER BY ?expiration ?incept ?label
(for convenience, a prepared link to the results) Cheers Graham |
|
|
|
I've tried reading the READMEs but they don't seem to provide much information.
Try the unix-specific build notes in /doc, e.g. https://github.com/neoscoin/NEOS/blob/master/doc/build-unix.mdThey always pop up extremely obscure libraries that are missing:
The dependencies are usually listed in the unix-build doc, they are conveniently listed as a one-liner in the article: How To Clone Scrypt Based Altcoins for Fun and Profit, i.e. they should be satisfiable with: $ sudo apt-get install build-essential libboost-all-dev libcurl4-openssl-dev libdb5.1-dev libdb5.1++-dev git qt-sdk libminiupnpc-dev
If you experience problems with using the above to satisfy the dependencies then you might be better advised to install Vagrant, set up an Ubuntu 14.04 VM and work off've that. I tried to do the following:
./make vTorrent-client.pro
$ qmake-qt4 vTorrent-client.pro
$ make
BTW, this is what the README.md looks like for HYPER's wallet:  that's likely just a large, flashing, red, warning sign of a classic CBA * developer, try the unix-build doc: https://github.com/HYPERcrypto/Hyper/blob/master/doc/build-unix.txtCheers Graham * Can't Be Arsed |
|
|
|
I don't wish to introduce a spurious sense of accuracy.
But I do feel compelled to update the graphic (done) to correct a transcription error in which Fuelcoin2's ”FC2” trading symbol has become confused with Firecoin2's “FC2” trading symbol. (I'm not entirely convinced that the FuelCoin2 FC2 symbol isn't just a bit of wishful thinking by those concerned --- the FuelCoin2 github repos source for src/qt/bitcoinunits.cpp is empty, as are many others in the repos.) Cheers Graham |
|
|
|
I shall leave the Paycoin entry as is, if that's alright by you, as I don't wish to introduce a spurious sense of accuracy. In order to reflect the ad hoc nature of the archive.org polling cycle I used a “first convenient coinmarketcap.com index page from 2014-MM stashed in archive.org” selection algo. In consequence, it obviously it raises the question: if a randomly-chosen day isn't considered accurately representative, then what's the “proper” strategy to take, assuming we have a complete record? And obviously, I need to put more effort into bending the gnutls technology to my will. For the interim, here's an accessible version: http://chrome.bel-epa.com/share/top40.htmlSolstice salutations. Cheers Graham |
|
|
|
Chrome tells me not to click though.
Firefox here. It keeps throwing up a "connection is untrusted" message.
I cant click also, just post it on here
The BEL-EPA Certificate Authority Root cert isn't in the browser's list of pre-approved (commercial) CAs. A (randomly-chosen) SSL cert checking service reports everything pretty much as expected: http://www.networking4all.com/en/support/tools/site+check/report/?fqdn=minkiz.co&protocol=httpshttp-over-ssl is rapidly becoming a matter of basic communications privacy rather than anything to do with “trust”. The site uses mod_gnutls' Server Name Indication to enable https connections to a small number of web apps running off've a single machine/IP address. A self-signed CA cert avoids the charges imposed by the pre-approved commercial jackals certificate authorities such as GoDaddy. The connection will be trusted if I pay for a GoDaddy-signed cert but that's a definition of “trusted” that sticks in my craw. Cheers Graham |
|
|
|
did not get very far with abe.... it runs and all but not able to read anything
NameError: global name 'sifcoin_hash' is not defined
it's running now on a node I made but returns nothing obviously, i now understnad what Graham meant when he said it may be impossible since difining sifcoin_hash is not so straightforward as in other proof of work coins..... I will think it over if i come up with something clever will let you know....
You musta missed the bit: All that's required is: pip install sifcoin-hashAbe should then be able to read the Sifcoin blockchain. Cheers Graham |
|
|
|
2014 top 40 coinmarketcap listings month by monthCourtesy of coinmarketcap.com and archive.org (arbitrarily grabbed from archive.org, parsed and rendered): https://minkiz.co/coin/infographics/cPoster (nearly all coins, assets mostly excluded):  ^^^^ click to see the larger picture (interactive, names as tooltips) Solstice felicitations. Cheers Graham
|
|
|
|
Updated at 21st December 2014 (happy solstice!), the new total is shown in red below ... The total thus far for 2014 is 1572 1648 (including parodies, failed launches etc. and not limited merely to btctalk ANNs) according to a count of the coins listed in the DOACC metadata collection and obtained via a SPARQL query posed of Minkiz' SPARQL endpoint, accessible on: https://minkiz.co/sparqlPREFIX doacc: <http://purl.org/net/bel-epa/doacc#>
SELECT (COUNT(?node) AS ?coins) {
?node doacc:incept ?yearmo
FILTER(?yearmo > '2013-12')
}
You'll probably want to update to the latest count prior to publishing your summary. For convenience, here's the query as a clickable URLCheers Graham |
|
|
|
The most protocol advancements were through Proof of Stake Coins which also introduced POS 2.0, sending using minimal CoinAge, Stake for Charity, use of int64_t and levelDB for efficiency improvements, Quick-sync among many other smaller changes.
Is the bolditalicised part ^^^^ a description of the components that differentiate "POS 2.0" from "POS 1.0" or an unrelated list of added features/changes? I've seen the term "POS 2.0" used but I've yet to encounter a definition. Cheers Graham |
|
|
|
|
Show Posts
