I am just curious of qubitcoin, having no qubitcoins. darkcoin is anonymous, but qubitcoin is not.
The official faucet has been dry for months now. Does anyone know who the designated contact is for the group of investors that has undertaken to keep the faucet supplied? (Nothing shrieks "failed coin" quite as loudly as a long since dried-up “official” faucet that's still being advertised.)
I do not know more underrated coins, coin has been neglected by the major devs, then scored an ambitious creator - he wanted the bad luck came from crimea, disappeared without a trace started to stick to military intervention. Fashion PoS scam it came in ..
The coin is clean, practically extracted, and dropped a long time ago by botnets. What more do we need?
A couple of responses:
I'm afraid that I don't share your positive opinion of krecu, his personal insecurity arising from his lack of technical depth* basically killed off any chance of holding practical technical discussions about improving the quality of the codebase:
February 08, 2014, 03:04:14 PM: https://bitcointalk.org/index.php?topic=411065.msg5018074#msg5018074
Dear community!!!
- q2c.cc and other UP!
- github updated! QubitCoin 0.8.4 (dear linux user recompile you daemon)
- I've been thinking whether we need KimotoGravityWell? As a result, after the 120960 block diff calculates KimotoGravityWell
- adding DNSSeed - now we do not need a list of nodes
Unfortunately the addition of the DNSSeeds has created a situation which is the exact opposite to that which was intended. None of the DNSSeed IP addresses are responding so publishing the results of getpeerinfo on a regular basis is now
absolutely vital for new users or anyone starting from wallet.dat because otherwise it's “No block source available”.
On that note ....
62.210.125.140
67.207.208.166
188.226.149.55
46.165.208.136
148.251.11.18
121.65.58.165
188.2.20.76
2.85.190.142
You should check for yourself whether they resolve for you although “added by mine-pool.net for test only” sort of gives the game away.
https://github.com/qubitcoin/QubitCoin/blob/master/src/net.cpp#L1194 // DNS seeds
// Each pair gives a source name and a seed name.
// The first name is used as information source for addrman.
// The second name should resolve to a list of seed addresses.
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}
};
One positive aspect of this is that the community is now aware of the issue and at least the investors have an opportunity to club together and sort out the funding of the domain registration/renewals and at least a couple of nodes hosting the DNSSeeds.
I find myself at a loss to suggest who you might approach to take responsibility for implementation and maintenance or how you're going to reimburse them for shouldering that responsibility. A bounty is a one-off and has always been an inappropriate means of funding a long-term commitment that has an inherent repeating fiat component such as hosting charges or coin maintenance.
Then again, Qubitcoin isn't the only altcoin suffering a mid-life crisis, perhaps it might be worthwhile to look at other altcoin communities to see if they have developed any viable solutions; f'rinstance, it's not just the PPCoin folks that get a weekly report from the dev.
And that leads me to my response to “What more do we need?” - you'll be relieved to learn that this response is more concise - the investors need to create a core team of people prepared to take responsibility for ensuring the robustness and reliability of the coin's underpinning logistics. I suggest you (collectively) look into reviving the Qubitcoin Foundation and shaping it into something that can provide some effective support.
Cheers,
Graham
* A common but trivially easy-to-spot error was introduced into the code and committed to the repository:
https://github.com/qubitcoin/QubitCoin/commit/2855a8eeee0a69d47158ec51c7b27a41089e331c#diff-a459a939be4fe065dd5f64ab60bb30d0R134Edit: refreshed getpeerinfo result