I don't really like to abandon stuff I've been supporting for a while, until officially DEAD.. like dead dead, lol..
You never know.. I jumped off the PND train for octocoin, had a good pool going on and everything, but shut it all down to get my servers setup for octo.. Mistake.
Mistake? Nah, you're being too hard on yourself. The amount of space between the endpoints of the "quitter" vs "obsessed" scale depends on the framing of the question. How close was the call at the time? Hindsight's a wonderful thing, gets even more penetrating as one ages but it does become more lenient as the broader picture comes into play :-) Thank you, I'm indebted to you for indulging my nosiness. Cheers, Graham |
|
|
|
Once Q2C reaches a block reward for 1 Q2C, does it remain at this rate indefinitely? Not indefinitely. The code provides for a 60s block target and a 1 Q2C block reward for another 13 years, then it hits the buffers. On which date will Qubit reach 1 Q2C reward per block?
Around August 31st, see https://bitcointalk.org/index.php?topic=411065.msg6326353#msg6326353Cheers Graham |
|
|
|
the coin related to politics？
This coin is for dancing. Not for buying weapons. "there is a machineguns" - Youssef make his famous machine-gun dance? Vido pls. Cheers, Graham. |
|
|
|
Does that break anything? I've noticed problems with the wallets just getting stuck from time to time..
No, it does't actually break anything in this instance because all the other references to THREAD_ADDEDCONNECTIONS have been similarly mangled into THREAD_ADDTESLAONNECTIONS. It's an error in terms of it being an unintended change but it's not actually damaging. Not mining much these days, I'll hit a few blocks a day just for fun and to keep the chain alive, though.
I'm helping to care for a couple of orphaned coins, too. But that's because I'm an empiricist, what's your motivation? (If you'll forgive me for being nosy.) Cheers, Graham |
|
|
|
Worst supported coin launch eva
Definitely a candidate for "Hapless altcoin dev of the Year": https://github.com/TeslaX3/TeslaX3/blob/master/src/net.h#L107/** Thread types */
enum threadId
{
THREAD_SOCKETHANDLER,
THREAD_OPENCONNECTIONS,
THREAD_MESSAGEHANDLER,
THREAD_MINER,
THREAD_RPCLISTENER,
THREAD_UPNP,
THREAD_DNSSEED,
THREAD_ADDTESLAONNECTIONS,
THREAD_DUMPADDRESS,
THREAD_RPCHANDLER,
THREAD_MAX
};
Such a delicate touch with regex: "s/EDC/TESLA/", sigh. Cheers, Graham |
|
|
|
... we do also need a proper developer.
You might (collectively) want to have a go at thrashing out an operational definition of the otherwise-rather-vague "proper developer". In the meantime, I'll point to some independent work I've been doing which happens to include Fuguecoin. My overarching interest is in understanding the pressures (for and against) improved transparency; one of my analysis techniques is to disassemble an original monolithic commit (of rebranding changes, parameter changes and assorted tweaks) into separate commits, one for the rebranding and one for the parameterisation and tweaks. I find this technique helps me to get a clearer understanding of the core “genetics” of the clone. Aaaanyway, I have a github repos containing a Bitcoin 0.8.6 update of Fuguecoin in a separate branch: This is probably the main interest: https://github.com/gjhiggins/fuguecoin/commit/70cb651e53929d43ecaa920127c443870f8d2736it's all the changes to the original, minus the rebranding. (I'll add the remaining checkpoint a little later, after some sleep). For comparison, this is the original lump'n'dump: https://github.com/fuguecoin/fuguecoin/commit/7aab885ee994017fe2ae3144a2f6e9cbb130d556I used the updated code as a springboard for an experimental sub-branch in which I integrated BountyCoin's rather nice dynamic difficulty plot. https://github.com/gjhiggins/fuguecoin/tree/bonusThere's clearly a small amount of polishing required to embed the feature fully and seamlessly but it's triv.  Admittedly, it's pretty but I'm asking myself whether it might actually be a waste of resources and screen real estate - I have a hard time convincing myself that it'll be of much interest to shibes, f'rinstance. In terms of thinking about attracting more non-miners to the coin, there are other experiments to try. Kris Borodiansky has added some nice tab-based services to Bellacoin and Mike Zuo is going great guns with a few solid months of continual upgrades to his BLAKE2B-based AllAgesCoin, adding tabbed functionality to the wallet (chat, forum, various markets, gambling). Adding HTTP-provided services to wallet tabs is sorta running against the decentralisation grain but I think there is room for some creativity and inventiveness in opening up the functionality of the wallet. HTH, Cheers, Graham |
|
|
|
... Love Coin is based on MintCoin.
Fwiw, I can confirm that lovecoin is a clone of mintcoin including the centralised synchronised checkpointing but with a heavily-modded PoS. Codebase transparency can be improved by brutally suppressing the deltas that implement the branding/livery. This vandalism enables the changes to the engine to be more easily perceived, examined and assessed. I built myself a little workbench, allows me to fossick at leisure: litecoin + (mintcoin + lovecoin) https://bitbucket.org/gjhiggins/zenlovecoin/commits/branch/lovecoinlitecoin + mintcoin + lovecoin (for completeness): https://bitbucket.org/gjhiggins/zenlovecoin/commits/branch/zenlovecoinThe git diff is mainly a useful one-page summary. For the actual fossicking, I use meld [1]. [1] http://meldmerge.org/HTH Cheers, Graham |
|
|
|
I'm not the developer of this coin, but I think it deserves an update.
I hope you'll forgive a couple of technical queries: 1. What criteria did you use to arrive at the conclusion that the coin "deserves an update"? 2. With regards to adding a checkpoint, could you explain a bit more about the purpose of this proposed addition? Cheers, Graham |
|
|
|
FYI A little self-contained halving calendar in Python, checked with doctest. The dates refer to the START of each step. The next per-block reward reduction (from 128 to 64 Q2C) will happen this coming Sunday - 27th. April 2014. The per-block reward will drop to 32 Q2C on 18th. May and to 16 Q2C on 8th. June. >>> from datetime import datetime, timedelta, date
>>> launchdate = datetime(2014, 1, 12)
>>> launchdate.isoformat()
'2014-01-12T00:00:00'
>>> halvener = timedelta(21)
>>> print(halvener)
21 days, 0:00:00
>>> ncoins = 0
>>> blockreward = 2048
>>> halving_every = 60480
>>> cnt = 0
>>> while blockreward > 1:
... ncoins_this_step = blockreward * 60480
... print((launchdate + (halvener * cnt)).date().isoformat(), blockreward, ncoins_this_step)
... blockreward = max(0, int(blockreward / 2))
... ncoins += ncoins_this_step
... cnt += 1
2014-01-12 2048 123863040
2014-02-02 1024 61931520
2014-02-23 512 30965760
2014-03-16 256 15482880
2014-04-06 128 7741440
2014-04-27 64 3870720
2014-05-18 32 1935360
2014-06-08 16 967680
2014-06-29 8 483840
2014-07-20 4 241920
2014-08-10 2 120960
>>> ncoins
247605120
After the completion of the reducing steps, a 1 Q2C per-block reward pertains (with a target of 1 block per minute) for another 13 years. Y'all might want to think about switching to an ASIC-friendly algo at some point, for when the per-block reward reduces to 1. HTH Cheers, Graham |
|
|
|
A list with active pools i know ...
Useful list, thanks. Ever-curious, I followed the links ... these are each pool's own reported hash rate (at time of posting) and, where given, number of workers: http://q2c.sytes.net:9372 - 5.98MH/s ??
http://qbt.mine-pool.net/ - 10.1MH/s ??
http://q2c.ext-pool.net/ - 1.13 Mh/s ??
http://q2c.mine-coin.de/static/ - 1.13MH/s ??
https://cpu-pool.net/qubit/ - 109.119 MH/s 36
https://www.mine-pool.net/qubit/ - 71.298 MH/s 55
http://67.207.208.166:9372 - 5.29MH/s ??
It's very limited in scope and the accuracy is highly dubious but I suspect that it's broadly indicative overall. Cheers, Graham |
|
|
|
This coin and this entire thread are a huge embarrassment to crypto.
That seems a bit excessive, wasn't the damage was already done a long time before? It's a bit arbitrary to choose to point an accusatory finger at this particular dev when the originators of Shitcoin, Fuckcoin, Fellatiocoin, RealStackCoin and the like are far more deserving targets for your vituperation. The DamaCoin dev is clearly signed up for the long haul and, with the altcoin dev community currently in such disarray, that is almost enough justification by itself to place the coin on this week's "must buy" list. I agree that the continued existence of DamaCoin and the dozens of other small community altcoins poses a bit of a mystery. For my part, I find the more rewarding challenge is in working out where my imagination is letting me down and causing me to fail to understand. (It's a line from a B-movie but the principle is sound - "If you don't challenge your prejudices, they will ultimately come to challenge you.") Cheers, Graham. Disclosure, I have 1m+ DamaCoin in my wallet but I'm afraid I'm not a supporter per se, the coins are slated for a public faucet I'm working on, along with wallets of 1m MIM and 1m whatever-else-I-can-lay-my-hands-on-coin --- which I believe is launching next month :-) |
|
|
|
Great News!!!
We will have at least 1 exchange on launch! AllCrypt.com has committed to add LOVEcoin to its exchange at launch!
To celebrate this; we will share some LOVE with everyone who has posted above this. Love Never Fails!
Dunno if it matters to you but the existing Lovecoin is already listed as LOVE, albeit 0 volume: http://www.cryptocoincharts.info/v2/coins/show/lovethe coin isn't extinct, it's still garnering 14/15 Mh/s: http://love.szbpool.com/HTH, Cheers, Graham |
|
|
|
There is no reason why someone cannot make an explorer for Hirocoin.
On that subject, I'm curious about the general opinion on the merits of a breakdown by algo, e.g. http://myriad.theblockexplorer.com/Does the detail convey any especially useful information or is it mainly providing reassurance that the coin is behaving as expected? Cheers, Graham |
|
|
|
diff still 0.00024414, will it ever change  No it won't. At least not until the value of nTargetSpacing is increased from its current setting of 1 second: https://github.com/albocoin/albocoin/blob/master/src/main.cpp#L907At that setting, the difficulty is permanently capped at the default bnProofOfWorkLimit of 1/12^2, i.e. 0.00024414 Fwiw, AlboCoin is a clone of Dogecoin-1.4, with all that implies. Cheers, Graham. |
|
|
|
If you're feeling generous, later arrival here.
XHYdzGXNVcivMTSz7NzhDL3crKs9ic882M
Just so happens to be the right time and the right place, you're in luck. Cheers, Graham. |
|
|
|
Linux adventurers invited to play with a v2 xxlcoin testnet ...
Watch out, this might be a trick to steal wallets or install malicious code. My mistake, thanks for explaining. Please consider the invitation withdrawn. Cheers, Graham |
|
|
|
Linux adventurers invited to play with a v2 xxlcoin testnet.I've set up a couple of nodes to form the basis of a testnet playground for trialling a new version of the XXLcoin wallet adapted from the recent dogecoin-1.5 release. The current XXLcoin wallet is a clone of the rather elderly code of dogecoin-1.4. The new dogecoin-1.5 release uses the faster, more robust leveldb and incorporates a host of improvements through dogecoin's own adaptation of the upstream, updated litecoin codebase. Source code is available on github: https://github.com/gjhiggins/XXLcoinI've successfully compiled and run both xxlcoin-qt and xxcoind on Ubuntu 13.10 and xxlcoind on Ubuntu 11.04. I'm running it with the following config as ~/.xxlcoin/xxlcointestnet.conf: rpcuser=userid
rpcpassword=userpass
testnet=1
rpcport=44555
port=44556
server=1
addnode=5.9.56.229:44556
addnode=85.10.194.50:44556
and/or from shell: ./xxlcoind -printtoconsole -debug -conf=xxlcointestnet.conf All seems to be working. Both nodes are successfully mining (in a desultory fashion), as is my 2kh/s laptop(!) and the mined blocks are maturing as expected. Transactions are being processed, getting confirmed etc. Linux only as yet, sorry for the inconvenience. Do make a backup of your wallet first. In fact ... Your eyes are weary from staring at the screen. You feel sleepy. Notice how restful it is to watch the cursor blink. Close your eyes. You wonder whether you've made a backup of your wallet recently. You smile serenely as you realise that it doesn't matter because you're going to make a backup of your wallet as soon as you wake, which will be in 3 ... 2 ... 1 <snap>. Cheers, Graham.
|
|
|
|
I would like to ask everyone to also register at ducpay.com. This is a Bitcoin forum and there are many different Ducats communities at the moment. Hopefully we can unite them all at a single place. About the logo, I have saved it but would like a few more suggestions before making a final choice. I'll shoehorn this in here, shoulda been a response to Shadow_Runner's post: What do you think about this simple version?
I'm not sure about more details or elements. IMHO coin must look simple and clear.
A solid start (your posting history is a credit to your dedication and talent). A skeumorphic approach using a realistic-looking coin is the obvious door #1 for the start of any design investigation ... but as you note: coin must look simple and clear To do that I think you must move away from the realism, losing the detail (which would inevitably be indistinct at typical icon sizes) and working more towards a symbol-like approach (at least purely to have an alternative, something to contrast with the skeumorphic approach). I know it's a tough task but the end result could be worth it. To have the kind of impact that's expected from a logo/icon/symbol (it plays all three roles) the visual appearance should aim to be distinct from the bulk of the 1001 other wannabe altlitebitcoins, be implemented in svg and should be recognisable even when condensed into a favicon. I don't know about the ru edition but the en.wikipedia entry http://en.wikipedia.org/wiki/Ducat offers some stimulating background context for feeding the design muse, e.g. "a gold or silver coin used as a **trade coin** in Europe from the later medieval centuries until as late as the 20th century." It occurs to me that a skeumorphic approach has one inarguable advantage -- it directly renders the item, there's no symbol processing required. This might confer a cross-cultural advantage, free of linguistic concerns. If you pursue the realistic strand further, there may be some mileage in browsing the designs created by some of the modern mints, e.g. http://www.muenzeoesterreich.at/ |
|
|
|
|
Show Posts
