development updateIt is going to be possibly up to a month until we have a majority consensus on what way to go with merging the chains.
I am going to give a time frame up to that long (a month) to get all the updates done and done right. (I'm redoing the core code to be up to date with the litecoin code. and fork our changes in (diff adjustment filter, auxpow (so we can merged mine dogecoin and CCO), the ability to go merged mining as a child chain (get mined like dogecoin, but not enabled in the case we would need to rapidly fork))
multi level alert keys are being tested now for completion in the updated release (so far so good, and hopefully we can push this code upstream to litecoin and bitcoin). The reason to do this is so each active developer has their own key, this allows the end user to know who sent out the key and what level their key is. It limits the chances of a hacker getting alert keys because it is harder to get multiple keys. This means hacking a low level dev's key does not do much more than cause a bit of a headache as a high level alert key can cancel alerts that are not life or death.
The update-release-candidate will be a hardfork and it's after that we will start pushing exchanges/merchant adoption hardcore. Hopefully by then we have come to a positive solution on chain merger ideas.
I believe that we will be doing our reprocity through slow distribution so as to not flood the market with about 20% of all coins at once.
If an exchange wants to adopt cco now, they can, but please give me weeks notice so I can at least do a rapid deployment of the alert key function and 144-tap Parks and McClellan diff filter.
Finally synced tnx ,
Any more details on how the merger will work ?
wait for instructions.
So what's the status of CCoin? I still have a lot of coins left.
My CCoin wallet V1.0.0.0 isn't syncing but it's been some months since last time I used it.
It's alive and actively in development.
for CCO, try these addnodes in your ccoin.conf
addnode=128.199.189.238
addnode=192.81.212.236
addnode=50.137.162.155
addnode=162.216.18.15
addnode=104.28.24.13
addnode=31.207.2.106
addnode=95.96.130.18
addnode=62.210.122.161
A copy of the CCO (CCoin) Blockchain can be found at one of the belowUSA (EAST)
http://freicoin.us/blockchain/cco_ccoin_blockchain-1410497079_compressed.zipCzech Republic (EUROPE)
http://31.207.2.106/blockchain/cco_ccoin_blockchain-1410497079_compressed.zipSingapore (SE Asia/Pacific Islands) -
http://128.199.189.238/cco_ccoin_blockchain-1410497079_compressed.zipPlease see my quotes below for more information/discussion/ideas
'
Hi
Some of us who just buy interesting coins do not have a clue how to follow these instructions even if we were to exchange coins for CCO because tech talk makes us dizzy.Would you not condsider taking over C-Coin/C-Pay and integrating your coin into it as it is a very good concept in principle.
The coin works faster than any other coin I have used so far and the wallet functions perfectly.
If not then can you do a VERY SIMPLE instruction on how to change our coins for your coin as I am not technical minded.Also due to CCO having more coins than CCN will would we be getting a ratio based swap of more CCO per unit of CCN as there are less CCN coins in total.
Thank you
Any reciprocity on the CCO will be able to be done with a script I will write so all that will be required is for you to turn on your CCN client and run the script I'll make and then paste the output. (I will make sure it is open source so anyone can verify it is not a trojan).
As far as continuing development of the CCN chain, I will not be continuing development on the CCN chain nor client.
I will be adding in features in the CCN chain as they are MIT licensed and the community wishes to have these features (the idea of c-pay etc).
I believe proportional reciprocity will be used, but again as I said there needs to be general consensus in the community. Also please note that the block for reciprocity has already been marked. That means that whoever had the coin at the time of the blockmark will have to run the script to get the cco coins.
What needs to be discussed thoroughly is do we raise the coincap to include those coins from CCN in to CCO and refactor from there, or do we adjust the distribution period and/or blockreward per block. Remember that CCoin (CCO) is not on an exchange *quite yet* because i would rather have all the kinks worked out in a final solution
confirmation timeS:
this chain has coin time of 1 minute which should keep the confirmation time fast. The addition of a 144-tap Parks and McClellan filter should give the ability to have the difficulty adjust upwords/downwards every 9 blocks (approx 9 minutes) and adjust over the last 144 (or 1/10th of a day) so at max the chain difficulty should return to normal within 1 days period and as such the blocktime should be averaging 1440 blocks per day (or 1 block per minute). Going at a rate much lower than one minute causes too many orphaned blocks and causes delays in transaction time and frustration towards miners.
If all else fails (and the CCN community rejects any possible outcome), the CCN blockchain has not been destroyed and no coins are required to be converted/handed in to ANYONE. But we're going to need to actually distinguish chains as the CCO chain (CCoin) did come first. (aka c-coin should rebrand by putting something in like naming it CoolCoin or something).
I appreciate people contacting me, and I'm glad we're getting some discussion going on. Please let me know if i answered your questions thoroughly or not.