Hm {
"version" : "v8.6.7.5",
"protocolversion" : 70069,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 0,
"moneysupply" : 0.00000000,
"connections" : 4,
"proxy" : "",
"ip" : "83.104.61.47",
"difficulty" : 0.00000006,
"testnet" : false,
"keypoololdest" : 1406481579,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
ah, that's better

{
"version" : "v8.6.7.5",
"protocolversion" : 70069,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 99,
"moneysupply" : 90098.00000000,
"connections" : 10,
"proxy" : "",
"ip" : "83.104.61.47",
"difficulty" : 1.29439068,
"testnet" : false,
"keypoololdest" : 1406481579,
"keypoolsize" : 105,
"paytxfee" : 0.00000000,
"errors" : ""
}
|
|
|
|
Would people here like me to hard fork Qubitcoin so it will be merged mined on Myriadcoin's PolyMYR Pool so Qubitcoin has all the qubit security of myriad
That's a generous offer, well worth taking up, it offers a more secure future for Q2C investors than going it alone on hashrate. “It means that while you mine Myriad your hashing power will also be used by the pool to simultaneously mine other coins that support merged mining, thus securing all the blockchains at once using the same hashing power and increasing your profits as a Myriad miner without circumventing any hashrate away from Myriad.”
http://myriadplatform.org/polymyr/Merged mining with Myriad can significantly boost QubitCoin's future prospects and perhaps even recover the recent price rise. If I were holding this coin, I'd recommend to the community that they grab the opportunity so promptly and energetically that they risk snatching Ahmed's arm off. But it's not my call. I hold only a handful of Q2C for testing the mainnet wallet, I have no skin in the game. I don't mine the coin because I have no GPU. As I mentioned, I use an i3 laptop so can only look on interestedly from the arts and humanities balcony and lend a hand when things seem to have gotten stuck. Cheers, Graham |
|
|
|
He gave a zip from megaupload. He's holding 5% of the premine. The only thing he's waiting for is an exchange add his coin.
I'll confine my observations to the code ... The zip archive contains a .git folder, including .git/config: [core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
[remote "origin"]
url = https://github.com/bluew1nter/godcoin.git
fetch = +refs/heads/*:refs/remotes/origin/*
[branch "master"]
remote = origin
merge = refs/heads/master
I checked and it is a fork of GodCoin, with a larger premine. Here's the results (excl. binaries and locale files) of diff -uNr godcoin/src achilles/src: http://pastebin.com/uHPmmJsYand the key part: int64 static GetBlockValue(int nBits, int nHeight, int64 nFees)
{
int64 nSubsidy = 0;
if(nHeight==1)
{
nSubsidy = 1100000*COIN;
}
else if(nHeight>2)
{
nSubsidy = 80 *COIN;
}
return nSubsidy + nFees;
}
HTH Cheers, Graham (The “zencoin” references are from my brand-normalisation facility which replaces a coin's branding with Zencoin (ZENZ) throughout, allowing comparisons (between now-Zencoins) to reveal just the functional differences.) |
|
|
|
What is hetzner box?
Just the server we're currently renting from hetnzer.de: http://www.hetzner.de. It sometimes reports more connections that the client here @homeADSL. FWIW Dept: I've found Hetzner's server auction to be a useful resource when I'm looking for a short- to medium-term project workbench.Cheers, Graham |
|
|
|
Couldn't get much out of that Perl Monks link, srry  That's odd, these seem quite pertinent to me, I was hoping not to have copy and paste them explicitly. “I came across this thread when Googling on "(8)Exec format error:". This probably not the answer to the question asked... However, I've just had this problem and it turned out that I'd started my script with a newline and not #!/usr/bin/perl (ie I'd opened emacs hit return, then paged down to the bit of code I was working on). so the script worked as 'perl foo.pl' but not via apache Hope this helps someone.” “I had the same issue, Thank You for the wisdom to solve my issue in such a timely manner. May happiness find you on your travels.”
“I tried what you monks said, but it didn't quite work out for me. Until I discovered that some stupid editor inserted the utf-8 byte order mark without asking and thus mangled my shebang into #!/usr/bin/perl I had to change the encoding to remove the mark, and now everything works fine  ” “If you are using Notepad++ as your editor and you are using unicode, be sure to have it set to "Encode n UTF-8 without BOM".
Otherwise, you get that leading character,”
As regard FCGI config, here's the content of my modules-enabled/fastcgi.conf. I've found that sometimes I need one approach, sometimes another. I apologise for not sanitising it first but I'm pressed for time. Only the first two are currently active, I switched to using supervisor-controlled waitressing via ProxyPass, which I found a lot more straightforward. <IfModule mod_fastcgi.c>
AddHandler fastcgi-script .fcgi
FastCgiWrapper /usr/lib/apache2/suexec
FastCgiIpcDir /var/lib/apache2/fastcgi
# ==== www.higginsandmacfarlane.com ===========================================
# FastCgiServer /www/hmc/handmcom/handm.fcgi -port 9004 -processes 4
# FastCgiServer /www/hmc/handmcom/handm.fcgi -socket /var/lib/apache2/fastcgi/handmcom.socket -processes 1
# ==== www.higginsandmacfarlane.net ==========================================
FastCgiExternalServer /www/hmn/handmnet/handmnet.fcgi -socket /var/lib/apache2/fastcgi/handmnet.socket
# -user httpd -group httpd
# FastCgiExternalServer /www/hmn/handmnet/handmnet.fcgi -host 127.0.0.1:9006
# FastCgiServer /www/hmn/handmnet/handmnet.fcgi -socket /tmp/handmnet.socket -processes 1
# FastCgiServer /www/hmn/handmnet/handmnet.fcgi -port 9006 -processes 1
# ==== alpha.bel-epa.com ======================================================
FastCgiExternalServer /www/wm/waukmates/waukmates.fcgi -socket /var/lib/apache2/fastcgi/waukmates.socket
# -user httpd -group httpd
# FastCgiExternalServer /www/wm/waukmates/waukmates.fcgi -host 127.0.0.1:9008
# FastCgiServer /www/wm/waukmates/waukmates.fcgi -socket /www/wm/waukmates/waukmates.socket -processes 1
# FastCgiServer /www/wm/waukmates/waukmates.fcgi -port 9008 -processes 1
# ==== beta.bel-epa.com ======================================================
# FastCgiExternalServer /www/probsdev/probs/pyramid.fcgi -socket /www/probsdev/probs/pyramid.socket -user httpd -group httpd
# FastExternalCgiServer /www/probsdev/probs/pyramid.fcgi -host 127.0.0.1:9009
# FastCgiServer /www/probsdev/probs/pyramid.fcgi -socket /www/probsdev/probs/pyramid.socket -processes 1
# FastCgiServer /www/probsdev/probs/pyramid.fcgi -port 9007 -processes 1
# ==== gamma.bel-epa.com ======================================================
# FastCgiExternalServer /www/ukpp/ukpp/ukppsw.fcgi -socket /var/lib/apache2/fastcgi/ukpp.socket -user httpd -group httpd
and the contents of abe.fcgi? As you can tell from the Perl Monk inclusions, I'm looking for the source of the format error - Apache's trying to execute the Python code in abe.fcgi and if you've got a Windows-formatted file on a Linux system, then that could cause the error you're seeing. Or it might be something else. Cheers Graham Edit: added comment on fcgi config content |
|
|
|
The client automatically splits coins if they're staking too fast.
Thanks for that analysis. I haven't enquired deeply into the mechanics, meandthemissus are playing this with a totally straight bat, simply keeping the wallet open to allow staking. She's delighted that she now has 10 clams and I'm pleased to have 20. From a our adopted naive perspective, CLAMs is functioning exactly as expected. In fact, it's been so painless we're beginning to wonder whether that's it or whether we're missing something. Not that it'd be a problem for either of us if the answer was “Nope, that's it.” but I guess others who don't have the benefit of our technical familiarity might find some reassurance useful. FWIW. “They also serve, those who only hold and stake” with apologies to the shade of John Milton.Cheers, Graham |
|
|
|
What's the point push dead coin? This source code may isn't original. Nothing personal, but better to leave this coin dead.
I have 5 ELITE not even sent to exchange, so I can live with that.
You need to learn from mistakes or you will always do same mistakes. Here it's about hidden premine, I want to know where I need next time to check for avoid scam like this. Someone spotted where is the scam in code ? It's a hasty fork of SUMCoin. And it looks like this could be a candidate: https://github.com/dimecoinco/elitecoin/blob/master/src/main.cpp#L1567I'll work up a HOW-TO and post it a bit later. Cheers, Graham |
|
|
|
clues?
Yes, some pastebinned clues would be useful, the Apache fcgi config for one and the contents of abe.fcgi for another. You could also try out some of the suggestions mooted by the Perl Monks in the top results of this search. Cheers, Graham Edit: credit Perl MonksEdit: Edit |
|
|
|
[I also believe that the next progressive phase in the alt coins will need to be a consolidation, where developers concentrate on the coins that have (in their view) better potential in adoption. What factors will drive that is still unclear.
I believe I have a handle on something eminently suitable for QubitCoin but I only have vague notions of how that specific solution might relate to a broader consolidating movement. Cheers Graham |
|
|
|
I need some working nodes.
visible from our hetzner box: addnode=62.210.125.140:7788
addnode=188.226.149.55:7788
addnode=148.251.11.18:7788
addnode=188.2.20.76:7788
addnode=199.233.239.54:34278
addnode=37.187.154.81:40405
addnode=148.251.44.176:57301
addnode=50.197.11.193:56056
addnode=50.197.11.193:56738
addnode=208.84.132.253:43050
addnode=88.190.22.60:35927
addnode=88.190.43.122:33732
addnode=62.210.178.237:52142
addnode=198.245.62.191:53738
addnode=93.87.13.1:51246
addnode=77.247.181.165:30506
addnode=198.245.62.190:60784
addnode=85.10.194.50:37564
addnode=[2a01:4f8:201:7011::2]:7788
addnode=[2607:5300:60:2be::1]:58484
Cheers Graham |
|
|
|
I mean bittalk account QubitCoin starting this topic, someone has to a password, why would it not convey, if only inhibits the development of a medal
I believe the standard modus operandi is simply to start a new thread and terminate the old thread with a large, throbbing "We've all moved here" link to the new thread. gjhiggins is one of the few people who would like to push forward q2c truck. I am one of the few q2c endorse him as a new official independent developer
Thank you for the endorsement, I genuinely appreciate it ... but I see what you did there ... both QubitCoin devs have disappeared in mysterious circumstances, you're not catching me quite so easily  Hello, if anyone from the old q2c team member still alive?
Good question. Any of them turned up yet on the Sr Members’ “ Altcoin Bagholders Support Group” thread? Actually, I'll broaden the scope. I have an offer-by-PM "What is the cost for DNSSeed hosting? I am willing to pay for it if it's not a big amount." and it brings some inexorable logic with it. A DNSSeed is a hard-coded domain name (?!) or dotted quad (I should think so), whose function is simply to point to at least one known, (approved?) running node (I hate it already). This can be performed perfectly well by a common-or-garden DNS entry, hosting per se is unnecessary. Current qubitcoin code: static const char *strMainNetDNSSeed[][2] = {
// added by mine-pool.net for test only :)
{"s-seed.mine-pool.net", "s-seed.mine-pool.net"}, // test static dns seeds
{"q2c-seed.mine-pool.net", "q2c-seed.mine-pool.net"}, // test dynamic dns seeds
{NULL, NULL}
};
Can't say the same for the known nodes, though, they need to be commercially hosted and AFAICT that involves fiat, not altcoin. There are some important changes that should be made to the codebase, changes that should have been made before the coin was launched but, for whatever reason were overlooked. In amongst those changes could be new DNSSeeds if we can sort out some means of funding the basic operational logistics of the coin. MOAR debate pls. Cheers Graham |
|
|
|
|
Really nice to see a conversation sparking up.
That's solid evidence of a community. Perhaps one of its most important aspects is that it makes people feel more comfortable about joining in.
Being able to chip in to an ongoing conversation provides a more attractive means of engaging socially than having to stick one's head above the parapet with a “is this coin dead?” opening conversational gambit.
I positively encourage people to make “me too” or even “+1” posts.
In this medium, they play the role of conversational markers such as nods, eye contact and affirmatory utterances such as "uh-huh" and "yeah, right" that indicate the participants are attending to and following the discourse.
Impoverished as they are by this medium of expression, these markers are nevertheless a vital part of any broad-scale discussion/convo/yakking.
A discussion that is covering the ground has one additional beneficial side-effect, it acts to keep my posts short and forces me to be more concise. If I spend too long constructing the argumentation for my contribution, the discussion will have moved on, rendering my effort less relevant.
See?
Cheers
Graham
|
|
|
|
Who actually can have access to your account qubitcoin?
If I understand your question correctly: anyone with a github account who wishes to be a member of the org. github accounts are free. I think the next step is to regain confidence in the exchanges, first of all you need to go back back to bittrex;]
There's more than one school of thought. I'll quote someone else, from another thread: If you wanted a coin to have any long term value, you'd keep it off exchanges, and focus entirely on building infrastructure to use the coin directly for purchasing goods and services.
During my survey of the domain, I recall encountering some coin devs who declared that they were following this policy, I need to check on the progress. It's not clear to me yet whether QubitCoin is positioned as mainly an investment vehicle or a goods-and-services coin. I suspect the economic parameters point to it being an investor's coin, in which case the above strategy is unlikely to be effective. There are plenty of examples of strategies for a technical coin, Feathercoin and Vertcoin both have strong programs. Also, I intend to apply a bit of statistical analysis to the collection of metadata (basic data on 1357 altcoins) that I built during my survey (published as Linked Open Data under the DOACC umbrella), that should allow me a better view of where QubitCoin is positioned on the various dimensions and provide the basis for a comparative profile. Cheers Graham |
|
|
|
Currently there is only about 1000 alt coins
Sort of. According to our count (of “mooted” coins, not necessarily launched or even completed development) the total has now reached 1400+. Currently reads 1357 in total, another 4 dozen to add imminently. The complete list and the metadata we collected is published using semweb tech: DOACC https://github.com/DOACCThere's a softer, more immediately-accessible arty presentation: * “All teh coinz”: with logos, all on one page: http://minkiz.co/coin/* “To-day we had the naming of parts”: names & symbols, alphabetically organised, in tabs for easy navigation http://minkiz.co/coin/name/* “A Clash of Cymbals”: symbols & names, alphabetically organised, in tabs for easy navigation http://minkiz.co/coin/symbol/and ... more pertinent to this thread: * “Foundry”: Bitcoin Core templates in the algo of your choice - a variety of hashing solutions (i.e. a list) http://minkiz.co/foundryI was able to make use of this detailed background to work out some potential optimisations for QubitCoin’s hashing algos and wrote a technical post about it which contains a lists of hashing algo and links to listing and benchmark sites: https://bitcointalk.org/index.php?topic=411065.msg7887013#msg7887013Question is, how many of the existing algos have not yet been used in altcoins? The Hash Function Zoo is a good place to fossick for hashing algos: http://ehash.iaik.tugraz.at/wiki/The_Hash_Function_ZooCheers, Graham |
|
|
|
Yes, I do stand corrected
Solid work. My respect for you has just shot up immeasurably. I've made my point, I'll rest my case. Cheers Graham |
|
|
|
I didn't know about it, always it is useful to expand the knowledge,
and to learn something new , thanks
My rationale was jokingly favourable, actually your initial assessment was quite correct, all the examples are oversights. I'm confident that the one you spotted will be corrected shortly. Cheers Graham |
|
|
|
I brought this up earlier in this thread and stated my definition, and asked how others define a scam or shitcoin, but don't think anyone did.
A scamcoin to me is a coin where the dev promises features and doesn't come close, when a dev bails on a coin, when a dev runs an ipo and doesn't deliver coins at all, when there is a hidden premine, or a giant premine and the dev dumps... and things like that.
The difficulty is that there are no established, agreed operational criteria and I suspect there never will be - relative merit is a total can of worms. From an epistemological perspective, the issue is that the definition is ostensive, i.e. based on a shifting, partially-agreed set of instances that form the set. All very contentious and guaranteed to keep you occupied in endless hours of fruitless, often acrimonious, debate. One particular difficulty is the lack of a common vocabulary or terminology - there are very few terms used with precision, it's all couched in informal language - scam, shit, crap, etc. and there is a regrettable tendency to use a very broad brush. If you can't produce an agreed operational definition of your target, you've no business planning an attack. Random altcoin terrorism beckons. I found I needed to survey the domain in order to support the development of an ontology that would give me a better idea of the landscape (typically, I have to go looking before I find stuff). We're made the catalogue available as Linked Open Data: DOACC Description of a Cryptocurrency an OWL ontology, rendered here in RDF/XML: https://github.com/DOACC/doaccIndividuals: https://github.com/DOACC/individualsImages https://github.com/DOACC/imprintBecause, yes it is a difficult problem and people are starting to recognise the impact of the repercussions and consequences. The ontology and associated RDF graph will support the further development of the ontology, which I hope will point the way towards the mid-level categories that are currently so obviously missing from the vocabulary e.g. “PoS scheme”, what's one of those when it's at home? I'll tell you what it translates to: “Use the source, Luke”. Naturally, maintaining the currency of the catalogue is a resource sink and we're hoping to sustain both it and ourselves by piggybacking some artwork sales on it, hence Minkiz (see sig, enough spam for one msg) "data" section which presents the above in a Linked Open Data browser (conceptually akin to a block explorer) and, tentatively (until we assess the impact on machine resources) a SPARQL endpoint, allowing the data to be publicly interrogated. We'll get there eventually. Cheers Graham |
|
|
|
Will you publish the source code?
It's not strictly necessary, all the relevant code is Open Source - qubit_hash for the Python-C interface library and a fork of Abe that includes a general “QubitChain” class suitable for use with qubit-using coins such as the Cassubian Detk, Deepcoin and, allegedly, other new coins currently in development. Details: qubit-hash: https://github.com/qubitcoin-project/qubit-hash - Python interface to C sources of sph lib Abe: https://github.com/qubitcoin-project/bitcoin-abe - (fork of) Abe, Python web app, with a QubitChain class Commanding Abe to read the blockchain into the db: python -m Abe.abe --config abe-dcn.conf --commit-bytes 100000 --no-serve
and, for the information required to create a suitable abe-dcn.conf ....
$ grep 'pchMessageStart\[4]\' Deepcoin/src/main.cpp
unsigned char pchMessageStart[4] = { 0xae, 0xbf, 0xc0, 0xd1 };
$ grep -e 'PUBKEY_ADDRESS =' Deepcoin/src/base58.h
PUBKEY_ADDRESS = 30, // Deepcoin addresses start with D
resulting, eventually in .... datadir += [
{
"dirname": "/home/vagrant/.deepcoin",
"chain": "DeepCoin",
"policy": "QubitChain",
"code3": "DCN",
"loader": "blkfile",
"address_version": "\u001d",
"magic": "\u00ae\u00bf\u00c0\u00d1",
"conf": "deepcoin.conf",
"datadir_rpcport": "22872",
}
]
That said, I'm still trying to figure out why I can't seem to persuade Abe to synch Deepcoin completely up to date, which is why I haven't previously advertised the URL - http://minkiz.co/abe/chain/DeepCoinGetting it working is only part of the process, there's stuff like process monitoring and disaster recovery to consider, reflecting Abe's new importance as facilitator of exchange listings. My view is that a coin should have several block explorers - they can act as nodes, bringing some much-needed decentralisation to the otherwise centrally-oriented DNSSeed and checkpoint nodes, known to cause problems: The issue was with the checkpoint node being off-line and hitching onto an incorrect fork, where then it forced all other nodes to go to that fork since it is the checkpoint node. That incorrect fork was not caused by block propagation delays either, it was caused by the creation of PoS blocks. Since it has been off-line, the staked coins on it accumulated coinage. When the node came back on-line, it created a few PoS blocks immediately, before it synced up, causing a fork. Since it was the checkpoint node, the network was forced to that chain.
There's a thread for another coin that basically tells the story of when the dev of that particular coin hadn't commissioned enough resources to support the coin's single DNSSeed node, it got effectively DDOSd on launch, just like Mooncoin did, running on deacon boogie's home ADSL connection. I've concluded that for a variety of well-supported reasons, a handful of explorers is a Good Thing(tm) to strive after as it tends to enhance stability of coin operations in the face of adverse conditions. Cheers Graham |
|
|
|
|
Show Posts
