Bitcoin Forum

Update to v1.2 or later is recommended as a precaution, as this is compiled using OpenSSL 1.0.1g. Earlier versions of OpenSSL are vulnerable to the "Heartbleed" exploit. See below for download link.


First launched in July 2013, became sick due to a bug in January 2014, now revived in April 2014! The original dev has abandoned this coin so I have taken over to give it a new lease on life.

Original Specs:

- PoW+PoS hybrid
- 60 seconds per block
- Difficulty retargets every block
- PoW blocks:
  + 50 coins standard reward (1426 blocks/day)
  + bonus blocks of 4400 (1 block/day), 900 (3 blocks/day), 400 (10 blocks/day)
  + 1440 total PoW & PoS blocks per day

But things aren't so easy in the real world:

This coin is hard to mine. From the above specs, it sounds like there will be an average of (4400 x 1) + (900 x 3) + (400 x 10) + (50 x 1426) = 82400 CDC per day. But because this coin is so PoS heavy, it is actually a lot harder to mine. As well as PoS eating into the 1440 blocks per day allocation (a PoS block may only mint 0.01 or even 0.00) it also causes a lot of orphans. In one horrible day late last year almost every PoW block was orphaned; a total of about 250 CDC was minted over the entire 24 hours - less than 1% of the expected total!

So give this slightly unusual coin a try. Mining can be frustrating, but if you stick with it, you never know what could happen. Remember that big 4400 block is worth a whopping 88 standard blocks. :)

Please see below to ensure you are on the correct chain.

Where to download:

Download Cloudcoin v1.3.2 from Dropbox:

Windows GUI client: https://www.dropbox.com/s/x56jcuek6pye0r4/cloudcoin-qt.exe

Windows commandline daemon: https://www.dropbox.com/s/egp9vqnnrntj5t2/cloudcoind.exe

Source code: https://github.com/almightyruler/cloudcoin

Cloudcoin v1.1, v1.2 and v1.3.x are fully compatible with the files generated by the original v1.0/0.7.2 client. Just copy cloudcoin-qt.exe and/or cloudcoind.exe over the existing file.

How to ensure you are on the correct chain:

1. If you have never used CDC, installing and starting the new client will get you onto the correct chain.

2. If you have used CDC previously, but have not started the client since before January 2014, installing and starting the new client will get you onto the correct chain.

3. If you have used CDC more recently, and your block count is around 228xxx you will need to start over with the database. Install the new client, delete the following Cloudcoin files (blk0001.dat, blkindex.dat, and all of the database/ folder), then start the new client to sync onto the correct chain.

Warning: do not solo mine while your client is syncing! If your miner happens to find a block in the middle of a sync, you may start your own fork away from the main chain.

You should not need to use addnode= in cloudcoin.conf, but if you do run into syncing issues, the following peers are currently on the correct chain:



Block explorers:

https://www.cryptopia.co.nz/BlockExplorer?coin=CDC
http://www.almightycoins.org/explorer/cloudcoin


Pools:

http://mining.coreco.in/getting_started
http://cloudcoin.weminealtcoins.com/

Exchanges:

https://www.cryptopia.co.nz/Exchange?market=CDC_BTC  (other currencies such as LTC, DOGE, DOT etc also available)
https://bter.com/trade/cdc_btc

Happy mining!

github?

Is this the official launch? Looks like this was launched before.

It's a relaunch. The dev abandoned the coin and the network stalled due to a bug. I have revived it.

https://www.virustotal.com/en/file/0f9ffb4e3c492952d4edc693ff8a117b968fe93485d964e3d09d2f84e22bf19e/analysis/1396530738/

I'm assuming the 1 positive out of the 51 different client checks is a false positive. This EXE was cross compiled using Gitian on a Linux system. The files included in the source will allow anyone with Gitian and a 386-lucid VM to replicate this compile.

needs github+logo+marketing  :D

then full steam ahead into the clouds and to the moon ;D

4400 block found by a lucky miner a few minutes ago. At current rates, that one block is worth around 0.075 BTC.

Working on getting the source on github now.

+1

Have you contacted bter? They are still on the old blockchain.

what does Cloudcoin pay in PoS%? I know alot of coins suffered the negative timestamp bug that caused blockchains to lockup, they were cloned from the CDC source code. Does this new client resolve the issue? Can we also get coin-control as well, its pretty much a must with PoS/PoW hybrid coins. I am glad to see people reviving old blockchains instead of spamming new ones.

So far POS seems to be working fine on the new blockchain, no issues like the old one.

Yes, I've contacted bter with a link to the new client's source. Hopefully they can get it set up soon.


Looks like PoS pays a nominal amount around 1% p/a.

The negative retarget bug has been fixed and will apply from block 291253. I did it as a future fork to minimise disruption in the event that we get hit with the bug again before everyone has a chance to update. Note that even after this block it's not necessarily a hard fork; original v1.0 clients on the correct chain will still work just fine, UNLESS/UNTIL there's a neg retarget. If that happens, v1.1 clients will continue to work, while v1.0 clients will break again.

As far as coin control, I know we discussed that in the GRW thread, but that looks to be a fair bit more complex - maybe something for the future. This release was about fixing the serious negative retarget bug, plus minimising the messing around needed to get onto the correct chain.

why are you reviving this scamcoin?

Because it still has community support, including an exchange. Once I figured out how to get around the negative retarget bug and get mining working again, without a client update needed, it seemed natural to continue, reviving it properly with a new client release.

I know its history wasn't so great - large premine, original developer using fake accounts as shills to generate interest - but I'm sure we can move past that. It's not dead just yet.

dont forget the dev was a scammer he conned me out of around 0.5 BTC (he got  the cosmoscoin/realcoin/richcoin/galaxycoin/diamondcoin dev make it through me and he ran with my middle man fee. )

I sympathise with you losing money because of him, but we're moving forward now. He has nothing to do with CDC any more.

Would anyone be interested if I were to spin up a pool for this?

yes need a pool please

Syncing blockchain now
Pool is ready.
Will be up after ensuring stratum is stable :)

Now once bter gets the new client running all will be good...

bter admin has acknowledged my email (human reply, not just the help desk autoresponder). Hopefully he will re-enable deposits soon. I'll give him another poke if nothing has happened in a couple of days.

Pool sounds good. Not sure if it will end up with a bunch of orphans like solo miners do, or whether having a good amount of aggregate hash power will get around that.

Some stats for the past 24 hours:

Total blocks generated: 1284
PoS blocks generated: 514 (40% of total)
PoW blocks generated: 772 (60% of total)
400 CDC bonus blocks: 9
900 CDC bonus blocks: 3
4400 CDC bonus blocks: 0
Total PoW minted: 44300 CDC

Not a bad day, fairly high percentage of PoW blocks, with about 53% of the "calculated" average daily mint (which assumes 100% PoW blocks).

Once people mine a bit and start minting PoS blocks (about 9.5 days after PoW) it's going to become a lot more difficult to find PoW blocks, so get mining now. :)

http://forthelulz.no-ip.info/cdcpool/public/index.php?page=gettingstarted

sorry for the late reply
forums are being difficult for some reason
pool is up

can not connect to pool

fixed :)
Left external firewall up on that port, sorry 'bout that

need some help in the pool anyone

Once my rentals are up I will be adding one of my boxes as well

i put in my payout info and the coins are still in the pool is there a problem with the pool payouts

working pool?

nice an almost new coin with a old blockchain (I might be able to get in, in a couple of days)

The pool is still up and running just fine. We had over 20Mh/s (more than 1/3 of the network hashrate at the time) before it seems like everyone just up and disappeared.
Received a query earlier about payouts though. TWO FACTOR AUTH IS ENABLED. This means you will have to go to your account settings, enter your pin, follow the email link, and then handle your payouts.
If anyone has immediate questions please feel free to email me, or contact me in the forums, at any time. The contact form on the pool goes straight to my work email

2hours waiting the email cnofirmation, not on spam folder, just didnt received it

two-factor disabled for the time being, thanks for the update

so is it ok if i stay on the pool forthelulz.no-ip.info and when i try to add workers it comes up a blank white page and when i try the localhost is saids pool slowdown or credentials invalid

Just an update for everyone.
Been working with acckiller to make sure that all issues with the pool are resolved.
Have one or two more things I need to verify, and just waiting on the MPOS devs to pitch in their 2-cents before I go ahead and kick things off again.
Sorry for the delays everyone!

i have 5 connections but wallet won't finish downloading blocks.

forthelulz.no-ip.info/cdcpool/public is BACK UP
Sorry about all that downtime. I had to enable .5% fees though due to an issue with transaction fees not applying. I do apologize for that, but I want to assure everyone that it will rise NO HIGHER indefinitely.

My wallet is synced. I have uploaded the blockchain here (http://www.filedropper.com/cloudcoin)

Why not start with a new blockchain?? Whats the point of continuing the old one?

Has your wallet synced yet? What block # are you at? It's possible that your client is only communicating with peers on the older chain.

If you close down and restart the client it should force a connect to the two seed nodes on the new chain. During testing (multiple syncs from scratch) I had to do this a couple of times.

Let me know if this works.

For those of you who haven't made it our way yet, and are still doing that solo-mining thing...


COME JOIN US FOR THE LULZ AT:
http://forthelulz.no-ip.info/cdcpool/public


WE HAVE COOKIES

what your node I want to add it to my client. I am stuck with 2073 blocks to go. Have 3 connections.

216.105.71.69
It's only going to last for a few days.
Moving over to a static IP this week, thus the no-ip domain.

What block are you stuck on?

Did you try quitting and restarting? That should work, unless your client has banned the seed nodes, or they've banned your client.

Let me know your IP (PM if you like) and I'll have a look.

For anyone having issues syncing: here's the current list of synced nodes. (See OP for a more current list if you are reading this msg at a later date.)

Reward System: Full Stratum/Vardiff system with PPLNS
Server Location: Europe / America
Pro Hardware: Connections: 10 gigabit network hypervisor/storage. Direct connection to AIMX, MSX
Storage: Fast ZFS based environment with SSD cache and 32 disks.
CPU: Xeon 64bit / 16 powerful CPU cores
Ram: 128 GB RAM.

Security:
Two different geo-locations Hot wallets (primary and instant back-up).
Offline secured cold Wallet.
Automated back-ups and warning system for operators.
Ddos protecion.

The bter can not recharge ah, what reason is this, is that they do not have to upgrade the wallet or they deliberately semi closed prepaid? :-\

I have contacted bter again to find out when they will be updating the client.

Stuck on block 278763 using new nodes.... just happened too.

Hi dev, i'm mined CDC at http://forthelulz.no-ip.info/cdcpool/public/index.php?page=dashboard&clp=1 and i have 5000+ CDC in this pool, but i can't cashout to my wallet.
Today, i checked account balance and i have 0 CDC.
Pls tell me where's my coins?

http://forthelulz.no-ip.info/cdcpool/public/index.php?page=dashboard&clp=1 is scam pool?

i have had no problem with the pool send docjeff a pm abouit it he can handle it

Someone trying to revive a coin they have been mining alone for a long time? Hmmm

Where my coin. Auto payout not work. I make a manual request payout more 3000 CDC, pool not pay.
Today i login. My transactions was clear and no see any coin.

Another question.

1. Why my coin coming my wallet and confirmations more 500 coinfirms. After 3 hourse all CDC on my wallet return 0 confirm.?
2. Many many  my coin on your pool unconfirm yet? It become orphan??? and nothing.
3. Where is my coin?

DEV, PAY BACK MY COINS FOR ME
i'm mined for 2 day with 14MH/s (wasted my energy), and i mined alot of orphans, but 5000+ CDC confirm must back to my wallet. Pay back for me.

? The OP mentioned that PoW/PoS fighting makes this coin hard to mine... chain reversals equals orphans. Are you saying you've netted zero? Were you solo or pool mining?

edit: I see you seem to be talking about pool mining. You'll need to take that up with the pool operator.

http://cdc.okaypool.com GOOD POOL

I am stuck on block 277928 with 3 connections. I solo mined for days on 4 connections. then I noticed that the pools were mining at a higher diff and taking longer to find blocks. Now I can't sync the client. I hope i am not on a forked chain I mined 100k plus CDC already.

I'm mined at:
http://forthelulz.no-ip.info/cdcpool/public

My account is: namnguyen
worker is: namnguyen.1

Where`s my coin?

Edit: i tried contact to pool operator, but they don't answer.

I'm afraid you may be on a private forked chain, with your own low diff - it's unlikely you'd be able to mine roughly half of the entire money supply over that 4 day period. :( Current block on the two seed nodes is 280798. Both pools are on the same chain & block.

edit: I'm preparing a pastebin with a list of block numbers, diff, hash etc so we can figure out if/where you forked.

sounds good. thanks.

I did specifically mention in the OP that CDC can be frustrating and difficult to mine, because minting (and maturing) PoW blocks can be erratic. The reason is that CDC gives PoS blocks a huge amount of weight (trust), so a single PoS block can override a chain of one or more newly minted PoW blocks. This does not affect transactions, but it does affect mining.

It's not so much a bug as a design flaw, and CDC isn't the only coin that suffers. To 'fix' it would require some pretty drastic changes, like disabling PoS completely, or going PoS only.

On the plus side, it should make the coin more valuable, because it is difficult to mine.

I'm mined at:
http://forthelulz.no-ip.info/cdcpool/public

My account is: nigttran


Where`s my coin?

My coin mined at http://forthelulz.no-ip.info to my wallet become orphan ( 0 confirmations) after several hours. What's happen?

I'll bump the confirmation limit up.
Orphans are a product of the network, nothing to do with my pool. If you were mislead into thinking you had extra coins because of it I apologize, but that's part of what happens sometimes.
However I'm showing you having mined several thousand CDC, much of which is still sitting in the pool wallet. I would request you take a look at things on the pool, and get back to me with the status of what is specifically out of place.

From TheSerapher himself:
https://github.com/MPOS/php-mpos/issues/767
"And again to avoid confusion: orphan blocks will always create credit transactions! They are not available to the user as a balance unless confirmation limits are off and blocks get confirmed, users pay out and then a block still becomes orphan"

Confirmations are now 120.

Yes. I mined several CDC from your pool and payed and over 200 confirmations on my wallet. But many many transactions become 0 confirm.

Example: First then all transactions was confimations over 200.

"Status: 0/unconfirmed
Date: 4/6/2014 16:26
From: unknown
To: BsM96vCgSNTjmK54zT8U5Pfjd3eWP1gWzk (own address)
Credit: 1032.818347 CDC
Net amount: +1032.818347 CDC
Transaction ID: a922832860298121313b8a5aff7d0473f9b291410d7b638097fc37fa943142c7
"
and
"Status: 0/unconfirmed
Date: 4/6/2014 17:00
From: unknown
To: BsM96vCgSNTjmK54zT8U5Pfjd3eWP1gWzk (own address)
Credit: 1112.601872 CDC
Net amount: +1112.601872 CDC
Transaction ID: bfe8f622303659aacd73eff8b02c03cbc46730eee5ea347bc0426b3dabc5d83e"

and

"Status: 0/unconfirmed
Date: 4/6/2014 17:53
From: unknown
To: BsM96vCgSNTjmK54zT8U5Pfjd3eWP1gWzk (own address)
Credit: 1013.311012 CDC
Net amount: +1013.311012 CDC
Transaction ID: 712910e38f600836737deb094bd44950b9004e95502a3f90c04ef85be3cd8fc5
"

Where is my coins? and some remain coins on your pool when classic interface (now you have new pool interface)

Orphaned blocks are blocks rejected by the network. Any payouts credited to you on a block BEFORE it was properly confirmed / orphaned will ALSO be orphaned, as explained above by TheSerapher's issue thread.

So in short, those SPECIFIC coins you are referring to never existed. They were simply a number that got assigned to you until the network rejected them, in which case they're declared invalid and never existed.

I have INCREASED THE CONFIRMATION COUNT BEFORE PAYOUTS ARE CREDITED TO YOUR ACCOUNT AND THIS WILL NOT HAPPEN AGAIN

http://bitcoin.stackexchange.com/questions/5859/what-are-orphaned-and-stale-blocks
This explains, briefly, the concept of an orphaned block. Once again, it's a product of the network, not the pool. The pool only allowed you to think you had coins when in fact they weren't properly confirmed YET at the time of crediting.

The big problem is that we have so few peers right now. It's painful...


Please let me know if there is any pool-related problem I can address for you.

As for coins held previously, very few were mined at that point in time due to database issues. I performed the upgrade to fix these issues.
I am still holding a small amount of what's left, if you can provide me an address I will offer you 500CDC as compensation for these issues.

Thank for Explanation

My address: BsM96vCgSNTjmK54zT8U5Pfjd3eWP1gWzk

Thank you

Sent.

This exact same message was sent to me in a PM a few minutes ago, but from a different name. How many accounts do you have?

I let bter know of the relaunch at the time I started this thread, and emailed again yesterday offering a bounty. I'm not sure what else you want me to do.

So, what time to open up bter?

Why hasn't open recharge?

If the bter will not open?

If there are other trading platform?

v1.2 has been released. This an emergency release to ensure the client is compiled with a version of OpenSSL that is not vulnerable to the "Heartbleed" exploit.

If you do not use SSL (encrypted) RPC this exploit is probably never going to affect you, but I have released this version just to be safe.

Updating is not required, but is recommended.

Download v1.2 from:

https://www.dropbox.com/sh/j9lbyaghxpg3d8y/5RaXM9uWWX

- cloudcoin-qt.exe (Windows QT Client)
- cloudcoind.exe (Windows Daemon)
- cloudcoin-1.2-src.zip (Source code for compiling on *nix)

Nice  ;)

http://cdc.okaypool.com   upgrade v1.2

IPO for this?

? The coin was launched 9-10 months ago. There is no IPO.

CDC communication
CDC 交流
QQ GROUP 99876324
QQ 群 99876324

root@3022idc:~# cloudcoind getpeerinfo
[
    {
        "addr" : "98.126.98.138:12344",
        "services" : "00000001",
        "lastsend" : 1397117626,
        "lastrecv" : 1397117595,
        "conntime" : 1397117041,
        "version" : 60006,
        "subver" : "/Satoshi:1.1.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 282913,
        "banscore" : 0
    },
    {
        "addr" : "110.228.199.95:4164",
        "services" : "00000001",
        "lastsend" : 1397117620,
        "lastrecv" : 1397117596,
        "conntime" : 1397117041,
        "version" : 60006,
        "subver" : "/Satoshi:1.1.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 282913,
        "banscore" : 0
    },
    {
        "addr" : "203.20.114.252:12344",
        "services" : "00000001",
        "lastsend" : 1397117716,
        "lastrecv" : 1397117737,
        "conntime" : 1397117046,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 282913,
        "banscore" : 0
    },
    {
        "addr" : "192.241.136.114:12344",
        "services" : "00000001",
        "lastsend" : 1397117619,
        "lastrecv" : 1397117688,
        "conntime" : 1397117059,
        "version" : 60006,
        "subver" : "/Satoshi:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 228892,
        "banscore" : 0
    },
    {
        "addr" : "88.198.25.25:53227",
        "services" : "00000001",
        "lastsend" : 1397117685,
        "lastrecv" : 1397117685,
        "conntime" : 1397117089,
        "version" : 60006,
        "subver" : "/Satoshi:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 228892,
        "banscore" : 0
    },
    {
        "addr" : "192.99.44.51:12344",
        "services" : "00000001",
        "lastsend" : 1397117619,
        "lastrecv" : 1397117595,
        "conntime" : 1397117093,
        "version" : 60006,
        "subver" : "/Satoshi:1.1.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 282914,
        "banscore" : 0
    },
    {
        "addr" : "24.210.41.92:58368",
        "services" : "00000001",
        "lastsend" : 1397117723,
        "lastrecv" : 1397117723,
        "conntime" : 1397117128,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 282117,
        "banscore" : 0
    },
    {
        "addr" : "107.170.49.232:53995",
        "services" : "00000001",
        "lastsend" : 1397117619,
        "lastrecv" : 1397117595,
        "conntime" : 1397117315,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 282916,
        "banscore" : 0
    },
    {
        "addr" : "85.17.81.169:12344",
        "services" : "00000001",
        "lastsend" : 1397117621,
        "lastrecv" : 1397117595,
        "conntime" : 1397117455,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 282918,
        "banscore" : 0
    },
    {
        "addr" : "192.241.136.248:46524",
        "services" : "00000001",
        "lastsend" : 1397117620,
        "lastrecv" : 1397117698,
        "conntime" : 1397117535,
        "version" : 60006,
        "subver" : "/Satoshi:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 228893,
        "banscore" : 0
    },
    {
        "addr" : "203.20.114.194:3373",
        "services" : "00000001",
        "lastsend" : 1397117627,
        "lastrecv" : 1397117599,
        "conntime" : 1397117596,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 282768,
        "banscore" : 0
    },
    {
        "addr" : "89.28.89.80:58338",
        "services" : "00000001",
        "lastsend" : 1397117626,
        "lastrecv" : 1397117625,
        "conntime" : 1397117623,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 282290,
        "banscore" : 0
    },
    {
        "addr" : "77.186.164.150:58729",
        "services" : "00000001",
        "lastsend" : 1397117627,
        "lastrecv" : 1397117626,
        "conntime" : 1397117624,
        "version" : 60006,
        "subver" : "/Satoshi:1.2.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 282837,
        "banscore" : 0
    }
]
root@3022idc:~#


startingheight  are not the same, the subver is not the same, this is the reason why all Orphan block?


http://cdc.okaypool.com/index.php?page=statistics&action=blocks

root@3037idc:~# eccoind getpeerinfo
[
    {
        "addr" : "78.43.108.45:19118",
        "services" : "00000001",
        "lastsend" : 1397118088,
        "lastrecv" : 1397118082,
        "conntime" : 1397094586,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62972,
        "banscore" : 0
    },
    {
        "addr" : "107.15.231.157:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397094593,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62974,
        "banscore" : 0
    },
    {
        "addr" : "70.162.30.163:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118083,
        "conntime" : 1397094594,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62974,
        "banscore" : 0
    },
    {
        "addr" : "173.16.9.27:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397094595,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62974,
        "banscore" : 0
    },
    {
        "addr" : "96.245.129.81:19118",
        "services" : "00000001",
        "lastsend" : 1397118082,
        "lastrecv" : 1397118085,
        "conntime" : 1397094596,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62974,
        "banscore" : 0
    },
    {
        "addr" : "192.241.215.76:19118",
        "services" : "00000001",
        "lastsend" : 1397118091,
        "lastrecv" : 1397118083,
        "conntime" : 1397094652,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62978,
        "banscore" : 0
    },
    {
        "addr" : "37.187.9.53:33842",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397094695,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 62978,
        "banscore" : 0
    },
    {
        "addr" : "84.245.47.75:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118087,
        "conntime" : 1397094758,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 62984,
        "banscore" : 0
    },
    {
        "addr" : "79.213.248.68:53827",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118090,
        "conntime" : 1397096917,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63029,
        "banscore" : 0
    },
    {
        "addr" : "184.163.251.183:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397096978,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 63029,
        "banscore" : 0
    },
    {
        "addr" : "23.94.15.121:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118083,
        "conntime" : 1397097813,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 63046,
        "banscore" : 0
    },
    {
        "addr" : "209.73.144.178:19118",
        "services" : "00000001",
        "lastsend" : 1397118089,
        "lastrecv" : 1397118083,
        "conntime" : 1397097971,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 63046,
        "banscore" : 0
    },
    {
        "addr" : "84.41.18.58:52167",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397098181,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63054,
        "banscore" : 0
    },
    {
        "addr" : "93.19.81.199:19118",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397099383,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 63075,
        "banscore" : 0
    },
    {
        "addr" : "60.189.45.145:63080",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397099518,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63077,
        "banscore" : 0
    },
    {
        "addr" : "182.200.119.178:49245",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397099600,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63077,
        "banscore" : 0
    },
    {
        "addr" : "23.253.125.185:56726",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118088,
        "conntime" : 1397101255,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63118,
        "banscore" : 0
    },
    {
        "addr" : "31.163.250.118:52745",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118083,
        "conntime" : 1397101444,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63118,
        "banscore" : 0
    },
    {
        "addr" : "75.87.251.216:19118",
        "services" : "00000001",
        "lastsend" : 1397118067,
        "lastrecv" : 1397118083,
        "conntime" : 1397101482,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : false,
        "releasetime" : 0,
        "startingheight" : 63118,
        "banscore" : 0
    },
    {
        "addr" : "93.86.195.52:58423",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118087,
        "conntime" : 1397101948,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63118,
        "banscore" : 0
    },
    {
        "addr" : "68.2.242.20:63431",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118083,
        "conntime" : 1397103611,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 62019,
        "banscore" : 0
    },
    {
        "addr" : "107.2.250.115:62446",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397107360,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63235,
        "banscore" : 0
    },
    {
        "addr" : "24.237.35.104:56832",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397107808,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63244,
        "banscore" : 0
    },
    {
        "addr" : "75.181.156.208:55238",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118086,
        "conntime" : 1397108337,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63250,
        "banscore" : 0
    },
    {
        "addr" : "218.7.9.76:54135",
        "services" : "00000001",
        "lastsend" : 1397118088,
        "lastrecv" : 1397118083,
        "conntime" : 1397108637,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63260,
        "banscore" : 0
    },
    {
        "addr" : "192.199.63.165:63926",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397110652,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63305,
        "banscore" : 0
    },
    {
        "addr" : "108.9.73.36:63867",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118083,
        "conntime" : 1397113083,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63236,
        "banscore" : 0
    },
    {
        "addr" : "208.84.132.254:50750",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397114024,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63377,
        "banscore" : 0
    },
    {
        "addr" : "60.28.62.203:40225",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397114462,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63379,
        "banscore" : 0
    },
    {
        "addr" : "83.46.75.84:53780",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397115157,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 61978,
        "banscore" : 0
    },
    {
        "addr" : "180.111.8.11:42200",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118085,
        "conntime" : 1397116711,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63320,
        "banscore" : 0
    },
    {
        "addr" : "137.135.61.33:2840",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397117484,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63434,
        "banscore" : 0
    },
    {
        "addr" : "37.128.1.132:3744",
        "services" : "00000001",
        "lastsend" : 1397118085,
        "lastrecv" : 1397118084,
        "conntime" : 1397118063,
        "version" : 60006,
        "subver" : "/ECCoin:0.7.2/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 63445,
        "banscore" : 0
    }
]
root@3037idc:~#




This is the normal situation of other Wallet

There are two forks of CDC. That's why there are different starting heights.

228898+ is the old chain which is stuck (PoS only, no PoW). Only older clients v1.0 (/Satoshi:0.7.2/) will be on this chain, but newer clients can use it to partially sync.

282957+ is the newer chain, which all clients can use: v1.0 (original), v1.1, v1.2.

CDC is hard to mine because PoS fights with PoW; a single PoS block can orphan the end of the chain that contains PoW blocks. Mostly this is just one or two blocks, but sometimes it can be 10+ blocks that are orphaned and replaced with the PoS block. CDC is not the only coin which is PoS heavy. :)

Do you have the 2 seed nodes? I redownloaded the blockchain and lost 180k and now stuck at 282136. Not sure I could have been on a private fork since I have been running the client using only the new blockchain since you posted it...

Have you tried quitting and restarting? I've found in my testing that sometimes the client seems to become fixated with peers on the older chain, which means the sync will never advance. Seems it's a bit like pot luck when starting up; occasionally it takes a few tries. (Deleting peers.dat may also help - it will re-add the two seed nodes at next startup). As more v1.0 clients upgrade to the new version (and others join for the first time with v1.1/v1.2) this should become less of an issue. It is annoying - if it does continue I can always add code which will deliberately ignore the older clients. I'm trying not to segregate the network (since v1.0 clients can still use the newer chain) but it may have to come to that.

lol

I deleted everything but my wallet.dat. Downloaded the blockchain again. It seems that I only mined 9000 CDC on the official chain. So lame I thought I had over 100k CDC. ohh well at least I am fully synced now.

    {
        "addr" : "203.20.114.252:63341",
        "services" : "00000001",
        "lastsend" : 1397209465,
        "lastrecv" : 1397209458,
        "conntime" : 1397209449,
        "version" : 60006,
        "subver" : "/Satoshi:1.3.0/",
        "inbound" : true,
        "releasetime" : 0,
        "startingheight" : 284185,
        "banscore" : 0
    },


V1.3?

Ask the author to publish

Now the node cannot update, the node in front of all the old nodes provide

That's my node. Have to test new code somehow. :)


Sorry, I don't understand this...

Good news! I have heard back from bter, and they are currently updating the daemon. Hopefully deposits will be re-enabled soon.

Trading is still possible if you want to buy CDC, or sell CDC you have previously deposited to bter. I have a few open buy orders in the book right now myself :)

Release version 1.3 Please

1.3 is not going to be released any time soon, it is simply a future version number used on a dev/testing node. At this point there is really no difference to 1.2 (although there are some planned changes soon, to get away from the old v1.0 chain)

1.2 is the current release.

Something is WRONG with CDC. I think there are multiple forks. Because wallet syncs for 5 mins, then it shows "out of sync", then it is 50 blocks behind and so on....No deposits showed on bter .  Which one is the official chain??

No kidding, I lost another 50K. Someone has re-written the blockchain again. That's 230k lost due to this shit....

I have 7 connections on my client. I hope I am on the right chain.

I fucking doubt it. Weeks mining down the fucking tubes...

Someone is throwing over 170 MHs at it...

1.3 Can be released as a development version

1.2 is a can not use version

There are two issues with CDC that I'm going to address in this reply. I'm going to key out some possible solutions in the hope of provoking further discussion.

As mentioned previously, CDC places a lot of (I would say almost extreme) weight on PoS blocks. Around 10 hours ago I saw a massive 286 block correction on the official nodes. Someone generating PoS blocks managed to override/reverse nearly 3 hours worth of blocks minted on the network. Within a few seconds the height dropped from 284909 to 284623, and 14325.14 CDC disappeared from the money supply. That sort of thing is unprecedented AFAIK, and to be honest I didn't think it was even possible to correct that large a number of blocks or time period.

Problem 1: Chain can be influenced by someone holding a large balance who locks (or keeps closed) their wallet, then unlocks it. PoS blocks can be generated very fast by a client, sometimes every few seconds. The huge reversal was started by a client that generated 33 PoS blocks in 4 minutes. In addition, they seem to have started minting PoS at a lower height than the rest of the network, so their fork extended from a lower point in the chain, which is why the network reversal was ultimately so large.

A possible solution is to limit the allowable correction to a maximum number of blocks so such massive reversals are impossible. The limit does need to be chosen carefully, because if it's too small it will cause everyone to continue on their own private fork if there's some issue that causes them to be more than X blocks ahead (their client will refuse to snap back to the main chain)

Problem 2: Miners are sometimes dropping off the main chain, and need to resync. This has happened to me also. I've been struggling to understand why, and the reason hit me 30 mins ago: the client refuses to allow you to mine until you have at least one peer connected, but it doesn't actually care about whether that peer is properly synced. I think what is happening is that the first peer a client is connecting to is on the old chain, so the client starts allowing PoS and PoW mining, which has the potential to create a private fork once you start minting blocks. It won't happen every time, but there's enough peers sitting on the old chain that it's likely to happen at some point.

example:

1. new chain is at height 100
2. old chain is at height 20
3. your client is at height 75 when you start it
4. your client connects to peer on old chain, client permits mining even though new and old chain will never exchange/agree upon minted blocks
5. if you mint a block before connecting to a peer on the new chain, it will be minted at height 76 instead of height 101; you're now on a private fork

I think that segregating the network to ignore the old chain will fix the second problem, and will actually go some way to fixing the first (remember the client that did the huge reversal started minting PoS at a lower height). I am working on that code change right now.

Where are you getting that figure from? If it's the "networkhashps" value in getmininginfo, that won't be correct, because it doesn't account for PoS blocks being generated separately to the PoW network.

it was from getmininginfo and difficulty was up to 1.7 or thereabouts...

how can anyone deposit in to bter it saids cdc coin disabled when the fck are they goin to enable deposits again

When solving the forking problem, when to release the new version?

Deposit addresses on bter starting with "B" : BwZqNy6JxvbJhgf..................
WTF?

Cloudcoin v1.3 released

This release will deliberately ban peers on the wrong chain. This should improve network stability and reduce the chance of forking.

Updating is strongly recommended, especially if you are mining.

Download from:

https://www.dropbox.com/sh/9ex30gqpw78s15k/f-AYOkjBql

That's normal. :) Do 'getnewaddress' a few times in the debug console and you'll see that CDC addresses start with both B and C.

It looks like there are still nodes which are not on the correct chain, so if you happen to sync via them you'll end up stuck on their fork. It's a real gamble right now.

Starting the client with an empty database and the following options should get you synced to the official chain:

-listen=0 -connect=85.17.81.169 -connect=107.170.49.232

This will ONLY connect to these two IPs, and will also disable inbound connections. Once you are synced you will need to restart the client as normal. (I would delete peers.dat before you restart.)

Your deposits to bter are not showing because they are also having some issues syncing. I will send the same advice to the admin.

http://cdc.okaypool.com   Back online

http://ww2.sinaimg.cn/bmiddle/a7e6241btw1efcf6pi9pcg207c09qkev.gif
LOVE THE GIRL

http://cdc.okaypool.com

LOVE THE POOL

https://bter.com/trade/cdc_btc

LOVE THE EXCHAGES

LETS GO ;D

-listen=0 -connect=85.17.81.169 -connect=107.170.49.232


root@2049idc:~# cloudcoind getinfo
{
    "version" : "v1.3.0.0",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 2824.86716400,
    "newmint" : 550.00000000,
    "stake" : 0.00000000,
    "blocks" : 287449,
    "moneysupply" : 5398722.35600000,
    "connections" : 0,
    "proxy" : "",
    "ip" : "98.126.98.138",
    "difficulty" : 0.20381855,
    "testnet" : false,
    "keypoololdest" : 1397279565,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "errors" : ""
}
root@2049idc:~#



Please put the mine pool node 98.126.98.138 into the two IP firewall white list

Now is the firewall

It does not connect the two nodes, wallet again cannot be synchronized

Something is WRONG with CDC. I think there are multiple forks. Because wallet syncs for 5 mins, then it shows "out of sync", then it is 50 blocks behind and so on....No deposits showed on bter .  Which one is the official chain??

Your client is being banned because it is supplying the wrong proof of work for a specific block, which probably means it has forked from the network again. :(

I don't know whether it's your mining that is causing the fork, or one of your peers. If it is a peer, as a short term solution, you can run your client with those commandline options I mentioned earlier (don't remove the options once you sync, keep them on)

cloudcoind -listen=0 -connect=85.17.81.169 -connect=107.170.49.232   (for daemon)

cloudcoin-qt.exe -listen=0 -connect=85.17.81.169 -connect=107.170.49.232   (for Windows QT client)

This should keep you tied to the two main nodes and prevent other peers influencing your chain. Obviously this is not a long term solution, since it centralises the network. I think the problem is that there is at least one fork which at least a couple of clients are on, so they end up being banned by the official nodes. They may be influencing other clients in the meantime, causing those to hop chains and/or be banned by peers on the opposing chain.

Can we please get as many people as possible trying this, to see if we can get rid of the other fork for good. It's difficult for me to see other chains because my clients ban peers on the "wrong" chain immediately.

Try the commandline options I suggest above. Temporary solution but hopefully it works. My Windows client has lost sync so I will test this myself.

This is the cdc pool node,Can't banned the IP,Please

Mine pool nodes, a large number of miners connected, real-time data updating is very fast, so the connection to the node will be relatively high, so please add you to the two node firewall white list, thank you!

pool node IP 98.126.98.138  98.126.98.139  98.126.98.250,add to white list please!

There is no "whitelist." When you fork, one node disagrees with another about the next block. That's why one bans the other.

I have set the ban time to 60 seconds (instead of 24 hours) but if you have forked the official nodes will continue to ban you (or you will ban them)

FIXING THE FORK - IMPORTANT TEMPORARY CHANGE

I'm usually running at least two clients at any one time, for both mining and testing. Overnight, the one 'locked' to the seed nodes stayed synced; the one that was free forked. This is sort of good news as it means that if we can temporarily centralise the network we may finally be able to get rid of the fork remnants. In the worst case scenario it only takes a single forked node generating a PoS block to start influencing other peers to jump to that chain.

Today I'm going to look at redoing CDC from fresh source, possibly Novacoin, or any other well written and actively maintained code. The CDC source is now coming up to a year old, and has had only minor changes applied since then. When I revived this coin I expected things would continue as normal and I'd have a bit of time to redo and test the new code, but obviously there's been some serious forking problems, so this needs to be moved forward ASAP.

In the meantime, please tie your client to the seed nodes by doing one of the following:

1. On the commandline:

cloudcoind -listen=0 -connect=85.17.81.169 -connect=107.170.49.232   (for daemon)

cloudcoin-qt.exe -listen=0 -connect=85.17.81.169 -connect=107.170.49.232   (for Windows QT client)


=== OR ===


2. In cloudcoin.conf:


*** It is important that you remove any addnode= entries from cloudcoin.conf so that your client does not try to connect to any other peers. ***

listen=0
connect=85.17.81.169
connect=107.170.49.232

Ups! All my coins are gone after the sync  :-\. The transactions are seems to be OK but nothing turning on in the balance. Any idea?

Brothers show mercy ah, give way to the man. Don't steal that block >:(

almightyruler  ， If you continue to play like this  steal the blocks ,nobody play with you , you will be personally killed the coin CLOUDCOIN.!!!!!!!!!!!!

Often do not block, the author stole block, the author if you do that again, I have to post exposure you >:(

Okay, I've had just about enough of this; the constant badgering in PM from you and your multiple accounts. I've been working hard to fix these problems and I have been completely transparent about them, so that as a community we can try to find a solution. I do not appreciate you accusing me of stealing blocks. Can you explain how on earth I would be able to achieve this? Back up your accusation with facts, please.

Steal  blocks
Really？

I also want to build a pool to the wallet

How to do？

Try running 'repairwallet' in the debug console to see if any coins can be recovered.

If you mined coins on a fork, they will probably be lost. If you sent any coins originally mined on the main chain when you were on a later on a fork, they can be recovered. When did you start mining?

You can't be serious? He is equal to the self Immolation, don't steal block. We are not stupid, if you still want to get our support, please don't make mistakes.

So I think we're now up to 5 brand new accounts with their very first post in this thread bagging me. Nothing unusual about that. :) Let's get onto something more productive and stop with the shills, eh?

I had ZERO problems with CDC since you resurrected it. I guess the trolls are just retarded. Ignore them....

??? no，keep ！

Dude. I think maybe you should consider closing your pool and walking away from CDC. It's obvious you will never be satisfied. You've stepped over the line now, and you're on the verge of going full retard.

okaypool, all you have done is made baseless accusations.

You have made a statement yet have not provided one single shred of proof. How am I supposed to be able to steal blocks in a peer to peer network where every node must agree?

You constantly complain about PoW and PoS fighting even though I have explained it to you multiple times in PM, and there's at least 3 posts in this thread (including the OP) that mention PoS overtaking PoW.

You appear to have multiple accounts - you've slipped up and used the wrong account in PM before - and some were just created today specifically to post into this thread.

I thought at first this was a language barrier issue, but quite frankly, your behaviour is starting to concern me.

Going forward, if you have a technical issue with CDC I will be happy to assist you, but otherwise I will not be responding to any further rants or tantrums. Please just stop posting.

此币已死，有事烧纸

Thanks, repairwallet fixed the issue :). Never mined CDC. I've got some from the original dev back in last August. I just rediscovered the wallet file on my disk.

yes rairwallet fixed, my coins are back

Quick status update:

NETWORK STABILITY:

I've been running my two test clients "free floating" (not tied with -connect to the seed nodes) for about 10 days and I'm happy to report that they have not forked. In addition, the seed nodes have not banned any clients over that period. This is great because it means no clients connected to those nodes, or clients trying to connect, have forked away (they would be instantly banned). There appears to be no more need to partially centralise the network, so if you are still using the -connect parameter on your client commandline, remove this and restart the client.


POOLS:

http://forthelulz.no-ip.info/cdcpool/public/ is down (spews out raw PHP code)

http://cdc.okaypool.com/ is up but has very little activity (last block found 190 hours ago)

Solo mining this coin is still very easy if you have at least 1MH/s to 2MH/s of hashing power.


EXCHANGE:

https://bter.com/trade/cdc_btc is fully operational again. CDC deposits can sometimes take several hours to clear, so don't panic.

Price has fallen significantly in the past week or two, perhaps because of people dumping. I have tried to add some support to its value by putting in buy orders to buy back in. Please consider doing the same. In the past couple of days the price seems to have settled around 500 satoshis.

PROPOSAL:

With PoS blocks overtaking PoW the daily amount of CDC being minted is very low right now. For example, in the past 3 days, only 9411, 10562, and 9304 CDC respectively have been minted. The average daily amount minted is supposed to be around 82400 CDC, or 71300 CDC if you exclude the 400/900/4400 superblocks. The network is minting less than 15% of the amount it is supposed to. This will probably get worse as more clients start generating more PoS blocks (which only mint tiny amounts like 0.02 CDC).

To put it a different way: yesterday the entire network minted about $20 worth of CDC!

I propose a change to CDC which will try to balance PoW minting, dynamically altering (reducing) PoW difficulty in order to get the network closer to minting the 71300/82400 CDC each 24 hour period. In other words, PoW generation will effectively speed up if over the past 24 hours the network has minted less than 71300/82400 CDC.

Right now at current prices the network is going to mint something like only $8k worth of value in a year. That should be more like $60k. I believe that bringing the 24 hour mint target closer to the original spec will help stimulate mining and usage of this coin, and could even raise its value.

Please discuss...

Bump

Fairly major change proposed, looking for comments... anyone?

Would this new version allow me to keep the coins I mined when the original client came out?  Or are those coins all wiped out?

Right now all it does for me is show that my old coins are all "Unconfirmed:"

Yes, all coins mined with the original client or any of the more recent "revival" versions should be on the same chain - assuming you were not mining on your own sub-fork.

Where are you seeing Unconfirmed - do you mean in the transaction list? You can try the 'repairwallet' in Help->Debug Window->Console, or if that doesn't work, try the -rescan commandline option. The latter may take some time as it has to sift through every block; the client will appear unresponsive (no normal wallet window) until it is completed.

Thanks for your work on this.  Looks like my coins transfers fine now. 

The requested URL /cdcpool/public was not found on this server.

PoS BONUS PAYOUT COMPETITION

Some of you may have noticed that your open Cloudcoin wallet is magically accumulating funds, even though you're not mining. I'm currently testing a promo where you get sent between 1 and 10 CDC for each PoS block that your wallet generates. This bonus payout represents up to 1000 times the normal PoS mint amount. Payouts are limited to once per hour per address.

If you have seen this already - keep your wallet open, and enjoy.

If you didn't know about this - get your wallet open (and unlocked) now, and start earning! Even small balances will be able to generate PoS blocks and win the bonus.

I've allocated 100k CDC of my own funds to this. There's still 93026.2 CDC remaining to be paid out.

Bter cannot recharge
Please address

I've asked bter several times, and offered compensation from my own funds. I'm now waiting for confirmation on the exact amount needed.

I don't know why it's taking so long.

I'm happy to report that CDC deposits are now enabled at bter.

The bonus payout competition continues.

Thanks for Info. ;)

new checkpoints???

I have a problem with a strong capacity utilization of the CPU for a wallet open.

gen = 0

stakengen = 0 also does not help, any ideas?

how many max coins and how many in circulation

https://bitcointalk.org/index.php?topic=263605.0;all

Specs:
- PoW+PoS
- total number is 0.1 billion
- 60 seconds per block
- PoW block:
   - normal reward of PoW block is 50 coins
   - daily 1440 blocks with 1 88*50 coins super blocks, 3 18*50 coins super blocks, 10 8*50 coins superblocks, others are normal blocks
   - daily generation: 82400 coins
   - block reward halves every 1036800 blocks (2 year)
   - diff retarget every block
   - start diff is 0.1
- transcation need 3 confirm, mine need 30 confirm
- min coin age is 7 days, max coin age is 30 days
- transcation comment
- min transaction fee is 0.00001 coin
- P2P Port:12344, RPCPort:12345

"version" : "v1.3.0.0",
"protocolversion" : 60006,
"walletversion" : 60000,
"newmint" : 0.00000000,
"stake" : 50.01000000,
"blocks" : 434230,
"moneysupply" : 8510407.54300000,
"connections" : 6,
"proxy" : "",
"difficulty" : 0.24952311,
"testnet" : false,
"keypoololdest" : 1378749136,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,

I noticed earlier that the client was complaining about the checkpoint being too old. I will compile an incremental release with updated checkpoints.

ok thanks for your support

428770～238880 not with the new
checkpoint is too old. wait for block chain to download
or notify developers
How to solve
http://C:\Users\Administrator\Desktop\20140726003643.jpg

This is cosmetic only. It does not affect the operation of CDC. I have an incremental release compiled, just have to find some way to host it.

Again, this warning is for information only - your client will still work fine.


Sorry, I have no idea what this means.

All my coins are stuck in interest in the

NEW VERSION RELEASED

Download Cloudcoin v1.3.1 from Dropbox:

Windows GUI client: https://www.dropbox.com/s/6v8iaft4bpqcpzw/cloudcoin-qt.exe

Windows commandline daemon: https://www.dropbox.com/s/prwy4s4sytncp3n/cloudcoind.exe

Source code: https://www.dropbox.com/s/ktflaux8ik2pyh0/cloudcoin-1.3.1-src.zip

This is primarily a maintenance release to stop the warning about checkpoints being too old, but there are some other changes too:

- Updated qt library from 4.7.4 to 4.8.5. This improves the look of the UI for newer versions of Windows.
- Added newer checkpoints. This will stop the client warnings about checkpoints being too old.
- Added 'getstakinginfo' RPC command. This is accessed via Debug Window->Console, or commandline RPC.
- Fixed block estimate in Debug Window->Information. Now when synced the estimate will correctly show current block count.


TODO:
- Work on reducing startup time. Right now it can take more than a minute before the wallet shows.
- Work on improving client responsiveness when it is trying to generate a stake block.

https://i.imgur.com/JEAhyIa.png

A quick comparison of the UI difference between 1.3 and 1.3.1.

how many coins in circulation/max coins

You asked this same question 2 weeks ago. :)

Currently money supply is about 8.6 million CDC

Original specified maximum was 100 million CDC, but the actual amount is going to be significantly lower because of combined PoW and PoS.

For example, in the past 24 hours, the network has minted 14819.6 CDC, which is about 20% of the amount it would have minted if it was PoW only.

need a pool please

need a pool for cloudcoin

I've just sent an email to the pool you referred me to. Hopefully they can get things set up soon.

it would be nice talked to them yesterday keep me up to date

maybe you can integrate the stakeinfo in the mining info like orb

all in one info




19:54:58

getmininginfo


19:54:58

{
"blocks" : 813889,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"powdifficulty" : 2.88621616,
"posdifficulty" : 0.01656075,
"powreward" : 1.00000000,
"posreward" : 1.00000000,
"errors" : "",
"networkhashps" : 246054072,
"stakeweight" : 8956,
"minweightinputs" : 13,
"avgweightinputs" : 24,
"maxweightinputs" : 5,
"pooledtx" : 1,
"testnet" : false
}

www.coinpayments.net

I have made ​​a request to take on

and you specified as the point of contact ;)

http://targetmoon.com/support.php


I have requested

http://www.crypto-coins-table.com/index.php


requested, too

https://www.altcoincalendar.info/calendar


too

https://www.altcoincalendar.info/coins/762-CDC

now check it out

Guys don't you mind if we make an official .org website for cloudcoin?

Hi, I'm a little unsure if you're asking for someone to set this up, or you are offering to do it yourself?

There's already a cloudcoin.org (unfortunately) but some derivative of the name could still be used.

Note that there is now an "Xcloudcoin", which is likely to cause some confusion...

this here, this is original :D

we need a pool

sure we need one. i look around, help me when you want

Okay, I'm syncing the blockchain (taking a while)... but will have a pool for everyone soon.

Yeah if you will commit to becoming the dev from now on, I can support you with that.

what is the current block height of cloudcoin (and is there a block explorer)?

I've been looking after CDC for about 6 months now, no plans to drop it anytime soon :)

No block explorer yet, but it is planned. Are you wanting to check you're properly synced? Here's the current network state:

blocks : 464830
difficulty : 2.08437690

block 464830 hash = f521b23deb9c0e4167bf3eae072d5f6b049a0b047e350f1fe37d803f502c654b

(You can verify you have the same block hash by doing 'getblockhash 464830' from the debug console, or RPC commandline)

Perfect... we should be all synced and on the right chain.

You can get the pool's information here http://mining.coreco.in  (stratum+tcp://107.170.100.196)
Port 3030 - diff 8 (for small hash or CPU)
Port 3031 - VarDiff ranging from 32 ~ 512
Port 3032 - Diff 256
Port 3033 - Diff 1024

Excellent. I'll update the OP - do you have a direct link for the CDC pool or should I just link to http://mining.coreco.in/ ?

http://mining.coreco.in/getting_started  For people that are unfamiliar with NOMP pools.

oh nice
I'll be mines, soon

Anyone getting coins from staking?

Yes, you should be.

In a recent 24 hour period (the whole day of 17th August, my time) there were:

- 200 PoW blocks
- 1210 PoS blocks
- 85 payouts by the PoS bonus reward system

If you do the getstakinginfo command (in the debug console on the -qt client, or RPC via commandline) it will give you an idea of how your stake power relates to the rest of the network. In particular, 'expectedtime' will give you an estimate of how long (in seconds) it will take to mint a PoS block. The lower this gets, the more chance you have of minting the next block (before someone else does).

What's the maturity of the coins before staking begins?

Source says 7 days (60 * 60 * 24 * 7) but in practice it's more like 9.

Well I guess things are going fine nowadays.  ;D

Is your wallet staking now?

I'll have a pool running ( I think) in the next few hours. I need to get the DNS setup correctly and that takes a bit of time!

Edit: As requested by the OP the pool is now accessible via http://cloudcoin.weminealtcoins.com/. Please let me know of any weird issues ASAP and I'll look into resolving them.

hi, any updates of this coin???

I released a new client about 4 weeks ago. Is there anything in particular you're after?

We have a NEW Pool 0%Fee

http://ispace.co.uk/images/ispace_logo.png

This is a MultiPool
http://ispace.co.uk/

I often mine on http://ispace.co.uk
it always worked very good

CloudCoin
http://scrypt.ispace.co.uk/images/cdc_100.png

Miner URL: stratum+tcp://ispace.co.uk:3539

Algo: scrypt
Difficulty: 2.48576355
Hashrate: 1.70 MH/s
Confirmations: 120
Wallet Version: v1.3.1.0

Our Last Block: 500,118
Last Block: 39.72 minutes

Trading: https://bter.com/ref/194203
Information: https://bitcointalk.org/index.php?topic=263605.msg2816413#msg2816413

Thank you very much... Martin


CoinWarz Profitibility Pool
This pool monitors the CoinWarz website every 12 minutes and looks to switch to the most profitable pool at any given time providing the current exchange rate exceeds 0.0000001 BTC.
SHA256 URL: stratum+tcp://ispace.co.uk:4443
Scrypt URL: stratum+tcp://ispace.co.uk:4453
   

Lowest Difficulty Pool
This pool monitors the difficulty settings of our coins and always mines the pool with the lowest value. Difficulty values are checked at 15 minute intervals.
SHA256 URL: stratum+tcp://ispace.co.uk:4441
Scrypt URL: stratum+tcp://ispace.co.uk:4451
   

Rotation Pool
This pool simply rotates through all of our available pools on an hourly basis
URL: stratum+tcp://ispace.co.uk:4444
   

Newest Pool
This pool mines our latest SHA256 coin pools, rotating every 2 hours. These are currently  MMXIV, BitCentavo, PayPro, TitCoin and VikingCoin.
URL: stratum+tcp://ispace.co.uk:4442
   

The "Five" Pool
This pool rotates on an 2-hourly basis through 5 coins chosen by us. Out current choices are MyriadCoin, UnbreakableCoin, MazaCoin, Open Source Coin and Unobtanium.
URL: stratum+tcp://ispace.co.uk:4445


Please help keep iSpace Mining Pools free to use by donating to 1T5A5pVmmQ5rbJm25fnTda8PDQrfV2HsA

That's an old thread which points to the broken versions of CDC, do you know who I can contact at ispace to get that URL updated?

as initiator of the acceptance of this pool. I invited him to change it.

almightyruler, what you up to? How to proceed? What is your plan?

ok ,thanks
well, im watching this coin
This coin is so undervalued

I'm disabling this coin on my pool. It is constantly breaking due to the POS function inserting blocks on top of the POW functions. I don't have time to troubleshoot the problems repeatedly. If you have a balance, please PM your username and wallet address and I'll send the coins to you.

Sorry about that.

What is breaking exactly? PoS overriding PoW is normal for a hybrid coin, so depending on weights and wallets open there can be a fair number of orphans.

I keep a running log of 'getinfo' parameters which clearly shows when there is a reversal - due to a new chain winning - and looking back over the past day or two the reversals are a maximum of 1 to 2 blocks. In other words, a PoS block orphans at most two sequential PoW blocks.

This coin has been tagged for participation in XUC, glad to know it's got a dev again.

see here for XUC and how you will redeem your share : - Project XUC (https://bitcointalk.org/index.php?topic=791338)

thanks barwizi :)

This does not mean the coin is broken.. it means you are using the wrong pool setup.

From the OP:

all my minted coins gone
and blocks changed back to orphan :(

"All" your coins gone? How many blocks? I cannot see any drastic reversals or forks from this end. Can you give me any more information?

i deleted coin daemon :(
i was syncing for past 24h and used wallet from this thread 1.3
i mined around 5k coins it appeared as confirmed + new mint  then i sent 150 coins to bter and all transactions showed orphan
thats all i have



  {
        "account" : "",
        "address" : "C3CNKCfEEVrf8Giq1RAMCrL4oTbtmsThHa",
        "category" : "send",
        "amount" : -150.00000000,
        "fee" : 0.00000000,
        "confirmations" : 0,
        "txid" : "00742f33818aefec7f06c98857974b6c51f5c8231276643ad285572eef0df404",
        "time" : 1411903524,
        "tx-comment" : "",
        "timereceived" : 1411903524
    },
    {
        "account" : "",
        "category" : "orphan",
        "amount" : 50.00000000,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "70f330919bc6cee3801a63a748ef8a8c9068b3b8d42fa20efb05184a755489fc",
        "time" : 1411903524,
        "tx-comment" : "",
        "timereceived" : 1411903524
    },
    {
        "account" : "",
        "category" : "orphan",
        "amount" : 50.00000000,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "39c6be72590570c33585ef8f7a5c32332fd5599d1ed75f1e83bd57c6f0f2d87f",
        "time" : 1411903524,
        "tx-comment" : "",
        "timereceived" : 1411903526
    },
    {
        "account" : "",
        "category" : "orphan",
        "amount" : 50.00000000,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "bd4aeed48cafef057f92711c03f046bb1959a06c07859283c8e207bbdb6c851f",
        "time" : 1411903526,
        "tx-comment" : "",
        "timereceived" : 1411903554
    },
    {
        "account" : "",
        "category" : "orphan",
        "amount" : 50.00000000,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "137250ca08a5eb2aa8adeddf87291ccfcbe5e93b3fa213d12cfb4414fb02e3bb",
        "time" : 1411903554,
        "tx-comment" : "",
        "timereceived" : 1411903582
    }


since there is no working block explorer i cannot check these transactions

im gonna give another go can you confirm what is Current Block Height?

i tried again and

 {
        "account" : "",
        "category" : "immature",
        "amount" : 50.00000000,
        "confirmations" : 4,
        "generated" : true,
        "blockhash" : "000000000ea6c66630dcd7fc16b5b155fccb43aefe3486ecadd623cea723371b",
        "blockindex" : 0,
        "blocktime" : 1411931556,
        "txid" : "811ec819945d0eb8452d572c1933307005a3f4834701ca308c7474389d873eda",
        "time" : 1411931556,
        "tx-comment" : "",
        "timereceived" : 1411931604
    },
    {
        "account" : "",
        "category" : "immature",
        "amount" : 50.00000000,
        "confirmations" : 3,
        "generated" : true,
        "blockhash" : "00000000ebd5ea62347091ea01a4939d6d45ac565f67e70aa0c28bb5d91c48ab",
        "blockindex" : 0,
        "blocktime" : 1411931604,
        "txid" : "a1e8c4d002064dc66ab68a5391cf3eaf7844ef151de7bcd2fc4b2c06fc17d3a5",
        "time" : 1411931604,
        "tx-comment" : "",
        "timereceived" : 1411931608
    },
    {
        "account" : "",
        "category" : "immature",
        "amount" : 50.00000000,
        "confirmations" : 2,
        "generated" : true,
        "blockhash" : "000000015691c80ea275522f2a2c4624b7d6b88496b7269b6d677a111ed19be0",
        "blockindex" : 0,
        "blocktime" : 1411931609,
        "txid" : "b8524297116beb01a04fab6380541dac4668a58a49e85cdadb28642e22f17911",
        "time" : 1411931609,
        "tx-comment" : "",
        "timereceived" : 1411931647
    },
    {
        "account" : "",
        "category" : "immature",
        "amount" : 50.00000000,
        "confirmations" : 1,
        "generated" : true,
        "blockhash" : "0000000205217b13a0dc7a8aa41a8258680245dad10b5de617ca242cf4f593a1",
        "blockindex" : 0,
        "blocktime" : 1411931647,
        "txid" : "a830123b863b0b75bbc95eb110c432e979b9d88271b515b14310234a1962ac63",
        "time" : 1411931647,
        "tx-comment" : "",
        "timereceived" : 1411931661
    }

and after 2 or 3 minutes i get
  {
        "account" : "",
        "category" : "orphan",
        "amount" : 400.00000000,
        "confirmations" : 0,
        "generated" : true,
        "txid" : "85d7f104d85e88320fb33548286be292ad791cbe63e614e17c02434825d7b29d",
        "time" : 1411931804,
        "tx-comment" : "",
        "timereceived" : 1411931858
    },


here is my getinfo output

{
    "version" : "v1.3.1.0",
    "protocolversion" : 60006,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 532829,
    "moneysupply" : 9712419.30400000,
    "connections" : 7,
    "proxy" : "",
    "ip" : "86.186.167.44",
    "difficulty" : 1.05594315,
    "testnet" : false,
    "keypoololdest" : 1411827622,
    "keypoolsize" : 102,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00000000,
    "errors" : ""
}


and 1 more time

http://postimg.org/image/ngniiojmd/full/


it happens when difficulty goes back to "difficulty" : 1.05594315,

I've had a look at my logs and this seems to be the correct period. Yours would be most or all of the PoW (+50, +400) blocks:

29-Sep-2014 05:09:49 1411931389 blocks: 532828 (+1) moneysupply: 9712419.304 (0) difficulty: 1.05594315 (0)
29-Sep-2014 05:12:39 1411931559 blocks: 532829 (+1) moneysupply: 9712469.304 (+50) difficulty: 0.68146369 (-0.37447946)
29-Sep-2014 05:13:27 1411931607 blocks: 532830 (+1) moneysupply: 9712519.304 (+50) difficulty: 0.45430913 (-0.22715456)
29-Sep-2014 05:13:31 1411931611 blocks: 532831 (+1) moneysupply: 9712569.304 (+50) difficulty: 0.45382149 (-0.00048764)
29-Sep-2014 05:14:09 1411931649 blocks: 532832 (+1) moneysupply: 9712619.304 (+50) difficulty: 0.459756 (+0.00593451)
29-Sep-2014 05:14:24 1411931664 blocks: 532833 (+1) moneysupply: 9712669.304 (+50) difficulty: 0.48865509 (+0.02889909)
29-Sep-2014 05:15:30 1411931730 blocks: 532834 (+1) moneysupply: 9712719.304 (+50) difficulty: 0.50049641 (+0.01184132)
29-Sep-2014 05:15:40 1411931740 blocks: 532835 (+1) moneysupply: 9712769.304 (+50) difficulty: 0.5259462 (+0.02544979)
29-Sep-2014 05:15:50 1411931750 blocks: 532836 (+1) moneysupply: 9712819.304 (+50) difficulty: 0.52257848 (-0.00336772)
29-Sep-2014 05:17:41 1411931861 blocks: 532837 (+1) moneysupply: 9713219.304 (+400) difficulty: 0.55227365 (+0.02969517)
29-Sep-2014 05:17:45 1411931865 blocks: 532828 (-9) moneysupply: 9712419.304 (-800) difficulty: 1.05594315 (+0.5036695)


The important things to look at are the relative adjustments in brackets; you can see the count of blocks increases by +1, then there's a -9 offset. That's the network preferring a better chain, in this case, a PoS block, which has much greater weight.

An adjustment killing off 9 mined blocks is unusual, but not impossible. Right now there seems to be a node in the US that is generating a lot of PoS blocks, which will result in more PoW orphans. I do mention in the OP that this coin can be a bit hard to mine... we're all in the same boat at the moment. :)

the price goes up

Hi alm. how do you think about a change to Neosyrypt. No gridseed etc. for the next 3 Jahe, appreciated!

wallet saids check point to old any updates can not send coins to bter

bumb is there a new verison my wallet is stuck a block 575176 can someone help

I can't see anything special about block 575176. Can you post the output of 'getpeerinfo' in the debug console?

Can you also see if block 575176 matches the network?

> getblockhash 575176
bfa0df972c20708e5e275812ecdfc6c16ec79c9e51ea5497a6191d9e2be18e1b

have you a new version?


[
{
"addr" : "85.17.81.169:12344",
"services" : "00000001",
"lastsend" : 1420139171,
"lastrecv" : 1420139171,
"conntime" : 1420138441,
"version" : 60006,
"subver" : "/Satoshi:1.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 661459,
"banscore" : 0
},
{
"addr" : "107.170.49.232:12344",
"services" : "00000001",
"lastsend" : 1420139234,
"lastrecv" : 1420139234,
"conntime" : 1420138463,
"version" : 60006,
"subver" : "/Satoshi:1.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 661462,
"banscore" : 0
},
{
"addr" : "106.186.25.224:12344",
"services" : "00000001",
"lastsend" : 1420139194,
"lastrecv" : 1420139077,
"conntime" : 1420138464,
"version" : 60006,
"subver" : "/Satoshi:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 661463,
"banscore" : 0
},
{
"addr" : "203.20.114.252:12344",
"services" : "00000001",
"lastsend" : 1420139162,
"lastrecv" : 1420139171,
"conntime" : 1420138465,
"version" : 60006,
"subver" : "/Satoshi:1.4.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 661462,
"banscore" : 0

Quick note that bter has currently shut down the site due to a huge theft from their cold wallet (7170 BTC worth).

If you have a CDC balance there, you should be able to withdraw it at some point in the future. BTC balance, not so sure. :( If you're lucky, you may be able to get a portion of it back.

bter is the only exchange that trades CDC. Which other exchanges do you think we could approach?

bleutrade is very fast, try this


cryptoine.com is a small market and would certainly appreciate a coin with the volume of CDC.
https://cryptoine.com/currency/info/CX

i have open a support ticket.


why is there a version 1.4.0.0??

Thanks for that. Which exch did you open the support ticket on?

1.4.0 is not a "real" version, it's simply a different number to differentiate dev and released versions. At this time, there is no difference in code or behaviour.

I will work on some maintenance and new features in order to prepare it for listing at another exchange.

While CDC is potentially looking for a new home... what are people's thoughts on moving to a fixed reward PoS system? Instead of receiving a small fraction for minting a PoS block, a normal amount would be rewarded, same as PoW.

Identical rewards means:

1 proof-of-work block (mined with mining equipment) = 50 CDC (with bonus 400/900/4400 CDC blocks)
1 proof-of-stake block (generated by client) = 50 CDC (with bonus 400/900/4400 CDC blocks)

Making the PoS network much more rewarding should encourage people to keep their clients open; even users without mining equipment will be able to generate funds simply by minting PoS blocks.

Orbitcoin (ORB) has been doing this for several months and it seems to be working well.

Thoughts?

IMPORTANT! Another thing I need to mention, we are very close to the block reward halving; it will happen in about 55 days... after that time, reward will be 25 CDC per block, with bonus 200/450/2200 CDC blocks.

on  https://cryptoine.com is a very fast exchange ... really nice


"Hello
In the comming days we open the possibility to vote for CryptoPoints.
Available now on market: https://cryptoine.com/trade/cp_btc

Visit the voting page in a few days."

He does not want to bypass the voting. Maybe you have a better chance!



The advantage of Bleutrade.com is, each coin can be traded against each other listed Coin!

Count me in :)

https://cryptoine.com/voting :)

*** WARNING. THE NETWORK HAS SPLIT. ***

Around block 726551, which was minted on 23rd Feb 2015, the network seems to have split. Shortly after this block a large wallet came online and started generating a lot of significant PoS blocks. I expect that was bter's wallet, but I'm not sure how (or if) that caused the fork.

Unfortunately, bter being offline masked this issue; if it had been up I would have noticed the issue a lot sooner. Even the two seed nodes couldn't agree, and each went off on their own fork.  :o I've resynced them both to the chain bter is on, as that will be the one that 99.9% of transactions happen on.

If (as of now) your client is at block 728xxx then you're on the same chain as bter; if it's at 752xxx then you're on the opposing fork. I was stuck on the latter myself, so I've wasted a fair amount of mining power over the past 3 weeks. :(

Here's a current snapshot of peers and their respective heights as they connected to my node:

37.187.96.15 height 728136
107.170.49.232 height 728143
203.20.114.252 height 728143
203.20.114.194 height 728152
69.146.108.212 height 728156
198.100.148.112 height 740981  (? probably in the middle of syncing to 752xxx)
106.186.113.177 height 752252
192.34.219.19 height 752252
217.186.35.206 height 752252

If you're on the wrong fork, try restarting your client and leaving it for a while; my test Windows client was "stuck", complaining it was out of sync, but had managed to figure it out when I came back a couple of hours later. You may need to do this more than once, as the network state may depend on which peer(s) your client connects to first. If that doesn't work, I'll see about putting up an archive of the blockchain, so there's no need to sync from scratch.

Block 728071 contains a test withdrawal from bter, which proves it's on the same chain. To check if you have the same blockhash for height 728071 - you're on the right chain - enter this into the debug console and compare the result:

> getblockhash 728071
00000cc57da9b75dd09cf91b6352f986ff28eba8cf4144a8cc13e789058a043d

{
"addr" : "106.186.113.177:12344",
"services" : "00000001",
"lastsend" : 1427062132,
"lastrecv" : 1427062131,
"conntime" : 1427057424,
"version" : 60006,
"subver" : "/Satoshi:1.3.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 752300,
"banscore" : 0
},
{
"addr" : "198.100.148.112:12344",
"services" : "00000001",
"lastsend" : 1427063184,
"lastrecv" : 1427063140,
"conntime" : 1427057647,
"version" : 60006,
"subver" : "/Satoshi:1.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 752300,
"banscore" : 0
}
]

this IP are on wrong chain??

So it is better to use for all new blockchain downloads connect= instead of addnode=

and only this
connect=203.20.114.252
connect=107.170.49.232
connect=37.187.96.15

hey almightyruler

bter.com giv me this adress BvSipBjiop8SPZZSgLw1dd7Xtpqri7FEbw but this not a CDC adress or?

a transfer to Bter.com was not possible! Bter is on wrong chain! right?

Cloudcoin(CDC)    No Website, No GitHub source


there was not a website ???

Can you give me a source !?

https://www.cryptopia.co.nz/Home/Voting

There is this link to the source in the OP.

https://www.dropbox.com/s/ktflaux8ik2pyh0/cloudcoin-1.3.1-src.zip

CDC make ensuring for raising as soon as possible...

thanks but i need a github link for listing on another exchange

https://www.cryptopia.co.nz/HomeAction/Voting

vote for CDC

    Exchange
    Mineshaft
    Market Place
    Block Explorer
    Coin Info
    Coin Voting

    Support


Chat
Voting Information
The Cryptopia vote list is a place for the community to vote for the coins they want to be added to Cryptopia
Each week the coin with the most user votes and the coin with the most DOT votes will be added to the Exchange, Mineshaft and MarketPlace

Each registered user receives 1 vote for each coin each day. (Trusted users votes are multiplied by thier trust rating)
Additional votes can be purchased using DotCoin(DOT) currency, You can add as many DOT votes as you would like.
Any coin that reaches 5 million votes in a round will be added to Cryptopia immediately, (This will not affect the voting rounds)
Note: At the end of each weekly round the votes are reset.

i have a open ticket on bter.com they check it now!

Well, it's not so much right and wrong, but I'd say most people mining and transacting CDC would want to be on the same chain as the exchange. I'll be releasing a new client compile soon; I'm just adding the hardened checkpoints now.

bter doesn't actually need to do anything with regards to syncing - I just did another successful test withdrawal when creating a list of checkpoints - but I do note that deposits don't seem to be working.

BTW, CDC addresses start with both B and C. :)

NEW VERSION RELEASED

Download Cloudcoin v1.3.2 from Dropbox:

Windows GUI client: https://www.dropbox.com/s/x56jcuek6pye0r4/cloudcoin-qt.exe

Windows commandline daemon: https://www.dropbox.com/s/egp9vqnnrntj5t2/cloudcoind.exe

Source code: https://www.dropbox.com/s/me6fycm5c7ezhbt/cloudcoin-1.3.2-src.zip

Minor maintenance release, but upgrading is recommended, especially if you were on the wrong chain and need to resync, or you find the "Checkpoint is too old" message annoying. Changes:

- Updated OpenSSL library to 1.0.1m (security fix)
- Added newer hardened checkpoints. This will stop the client warnings about checkpoints being too old.

free CDC giveaway for vote are here, read!!

https://cryptocointalk.com/topic/35026-cloudcoin-vote-giveaway/

I've sent a small amount to bter hours a go but the coin didn't make it, do we have a problem with bter still?
Thanks.

Yes. bter's client is properly synced - withdraws get into the blockchain within minutes - but deposits are not credited to the user's account.

I had delayed emailing bter, as they would have been quite busy getting everything going again, but I've now contacted the admin.

Thanks, hope they can fix it soon :)

need some working nodes wallet saids i got 4 connections to the network but will not sync what can i do to make it sync

What's your current block count? If you're unable to sync it sounds like you may forked.

So it is better to use for all new blockchain downloads connect= instead of addnode=

and only this
connect=203.20.114.252
connect=107.170.49.232
connect=37.187.96.15

I had so perfect reloaded the blockchain! Then you can use addnode again!

when will deposits start showing up on bter again sent over 5,000 cloudcoins there yesterday and still has not shown up

I let bter know just over a week ago. CDC seems to have been ignored a bit over the past year or two, in some cases it has taken several weeks to get bter going again... cross your fingers!

i emailed bter abouit my deposits and they said he needed a working block explorer to check my tx id is there a working block explorer

vote for CDC and we get a working explorer and a pool

https://www.cryptopia.co.nz/Content/Images/Cryptopia2.png

https://www.cryptopia.co.nz/Register?referrer=Mario241077
https://www.cryptopia.co.nz/Home/Voting


    Exchange
    Mineshaft
    Market Place
    Block Explorer
    Coin Info
    Coin Voting

free CDC giveaway for vote are here, read!!

https://cryptocointalk.com/topic/35026-cloudcoin-vote-giveaway/

got 300,000 to sell going rate on bter is 0.00000202 which = 0.6 btc because of deposits not going through right now and need btc will sell for 0.5 btc send me a pm if you want them

I have a bit of performance issues with the wallet, both cloudcoind (linux), and the windows wallet act the same.

With 300k+ CDC, the wallet maxes cpu constantly, rcp does not answer (times out), and eventually the wallet dies.

Is anyone else having issues ?

If you mined that 300k CDC then you probably several thousand inputs, which the client has to hunt through each time it wants to stake. Gathering those inputs into something larger (by sending to a new address in, say, 5000 CDC chunks) should help. I've run into this problem myself with a wallet.dat that grew to 180MB after mining, staking, and transacting for over a year.

You can also use 'reservebalance' in the config file or commandline to force the client to leave some or all of your balance alone when searching for inputs to stake. It's the staking that causes the client to be unresponsive.

Current height is 778449

> getblockhash 778449
fda5e19b92d5b2eaf1cbe3fb2cba8ecaa9767878527b0f923b0d54add0c9b3c3

No block explorer at this stage, although given recent experiences with bter that is moving up the priority list.

Yea, I have tried that, seem to get atleast a few chunks out in the size of 25k each, the rest just locks up the same, going to see if it helps making the chunks even smaller.

Regarding staking, there is no way to completely disable that ? It won't be sustainable in the long run for a pool to stake at the same time.

Transaction creation will also be affected when you're trying to send a large amount relative to the size of your inputs (sending 25k CDC with inputs of 50 CDC each will require 500 inputs). I can generally send between about 10-15k CDC at a time before my client starts complaining about the transaction failing, but it may vary for you.

To completely disable staking, set reservebalance to a value that's higher than your actual balance. You can set it to something impossible if you like, to make sure that value is never exceeded :)

in cloudcoin.conf:

reservebalance=99999999

On the commandline:

-reservebalance=99999999

Thanks :-) That actually helped alot!

any news from bter???

deposit still not working

i bring on this exchange and we have a blockexplorer https://www.cryptopia.co.nz/Exchange

everybody can help with vote

but i think i pay with DOT Coins...

everybody can help also

vote for CDC and we get a working explorer and a pool

https://www.cryptopia.co.nz/Content/Images/Cryptopia2.png

https://www.cryptopia.co.nz/Register?referrer=Mario241077
https://www.cryptopia.co.nz/Home/Voting


    Exchange
    Mineshaft
    Market Place
    Block Explorer
    Coin Info
    Coin Voting

https://cryptocointalk.com/topic/35026-cloudcoin-vote-giveaway-every-day-25-cdc-or-20000-pac/

Anyone know if bter fixed the deposits ?

я пepeвёл Cloudcoin CDC нa биpжy bter   нo мoй бaлaнc тaк и пocтyпил

Is there a workable block explorer for Cloudcoin?

Is there any working block explorer ?

no but if everbody help, cloudcoin can to get one




everybody can help with vote

but i think i pay with DOT Coins...

everybody can help also

vote for CDC and we get a working explorer and a pool

https://www.cryptopia.co.nz/Content/Images/Cryptopia2.png

https://www.cryptopia.co.nz/Register?referrer=Mario241077
https://www.cryptopia.co.nz/Home/Voting


    Exchange
    Mineshaft
    Market Place
    Block Explorer
    Coin Info
    Coin Voting


Voting Information
The Cryptopia vote list is a place for the community to vote for the coins they want to be added to Cryptopia
Each week the coin with the most user votes and the coin with the most DOT votes will be added to the Exchange, Mineshaft and MarketPlace

Each registered user receives 1 vote for each coin each day. (Trusted users votes are multiplied by thier trust rating)
Additional votes can be purchased using DotCoin(DOT) currency, You can add as many DOT votes as you would like.
Any coin that reaches 5 million votes in a round will be added to Cryptopia immediately, (This will not affect the voting rounds)

We have a strict NO delist policy, Once listed your coin has a permanent home
Note: At the end of each weekly round the votes are reset.

5Days22Hours1Minute42Seconds
Last user vote winner: CageCoin(CAGE)
Last DOT vote winner: Fetish(FETISH)
Currency    DOT Address    User Votes    DOT Votes    
Cloudcoin(CDC)    1E1xfuoRoNncqCcPnkihjoqAzB7ysQmj4M    4    100000    
IvugeoEvolutionCoin(IEC)    16orPYBKQHYEEE4Fq4fdB3Ye42QYbkALTW    8    11000    
Gadsdencoin(GAD)    1QBSy4hb61ZPHqAccuch6CcB8fmvbzgNfw    2    901    
DolphinCoin(DOLP)    1FhowFZATM9Azjn5E1jkkRD3fwCn67wBr9    2    50



for your vote you can get 50 CDC
https://cryptocointalk.com/topic/35026-cloudcoin-vote-giveaway-every-day-50-cdc-or-20000-pac/

still nothing fixed

from today

Bter Support (bter)
May 5, 17:44
We keep checking the cdc wallet ..
Thanks for your pateince

cdc on bter or anywhere will work and that is good but to sell now nowhere on bter sent and not come  :'(

however, I am the first and I voted no prize my wallet C8CmzHHCdkNmH78tZvSKmF4GS57S8VRGw6

post on cryptotalk your vote adress, see link, not here!

edit: but I have sent to you

what's the exchange bter I sent not once cloudcoin but no support with silent admin

I still have no answer, but the Price is up but is well :)

almightyruler blockreward halving in which block?? 

I misread the value in the source.


=== main.cpp ===

        // Subsidy is cut in half every 8000000 blocks,
        nSubsidy >>= (nHeight / 8000000); // cloudcoin


Reward halves at 8 000 000 blocks, not 800 000! We won't reach this until at least 12 or 13 years from now.

I've been working on a rudimentary block explorer:

http://www.almightycoins.org/explorer/cloudcoin/
http://www.almightycoins.org/explorer/cloudcoin/transaction/76e49d4ec4a713a9a1415c14f20143b2c52ee8b52007c3f86d6157c0b961b918

Very basic and ugly right now, but it's a start.

Still have to add search (by block or transaction) and put it on a dedicated domain name. Will work more on it later.

edit: Less than 2 minutes after I submit this forum message, Googlebot starts spidering the new explorer. Hmm, maybe I should have set up that domain first. :)

hmm the block explorer is not loading in my end


sorry its working now. had to reboot my router

The block explorer caches data, but if it's all new data (no one has loaded it for a while) it can take some time to gather and cache all of the necessary data. Once I've refined it further I will add a background process that pre-caches the data for a faster loading time. Still, it should only be 5 or 10 seconds at most, not a complete timeout. What is happening exactly? What error are you seeing?

Anybody else having issues with bter.. went to withdraw some coins.. spat out a tx b964cb440738e1a70dcab735db80e08c99bb6ee7d9756567c8722e6b2d417bae but it's been almost a day now, nothing..

I am constantly trying to reach them but to no avail.silent as a fish in water .send often on the exchange and no not that-do it all the time thinking that will work but all to no avail. and https://www.cryptopia.co. something quietly waiting for her will include

Ughhh, Cmon Dev. great idea, but get the bugs fixed.

NumChuck  can be more precise to virojatsya

vote here for cdc, so cdc get a blockexplorer

and alm can do other things

Good news, So CDC will get a new addnode and one block Explorer

www.cryptopia.co.nz

This weeks DOT vote winner: Cloudcoin(CDC)


Thanks to all supporters

Great to hear that CDC won!  :)

Current source is at https://www.dropbox.com/s/me6fycm5c7ezhbt/cloudcoin-1.3.2-src.zip https://github.com/almightyruler/cloudcoin (now on github)

There are two seed nodes hardcoded into the client, so you should not need to use any addnode config, but if there's any issues, a list of current peers is available at http://www.almightycoins.org/explorer/cloudcoin/peers

Let me know if you have any questions.

the exchange requests that the Github link

Here's the source for CDC on Github: https://github.com/almightyruler/cloudcoin

something is not running and the admin is silent

?

What's not running?

Admin of what?

Cryptopia Exchange cloudcoin

I think perhaps you were placing a little too much weight on the word "tonight." I'm guessing it's early morning Wednesday for you, meaning Tuesday night has concluded; but if Cryptopia is in New Zealand, Wednesday night has just begun (8:10pm now).

iam waiting CDC on c-cex for trade  ;D

why you not create Vote for CDC on c-cex ?

I now have Wednesday 16:02 - waiting for

now tradable :)

https://www.cryptopia.co.nz/Content/Images/Cryptopia2.png


www.cryptopia.co.nz (https://www.cryptopia.co.nz/Register?referrer=Mario241077)


https://www.cryptopia.co.nz/Exchange?market=CDC_BTC
https://www.cryptopia.co.nz/Exchange?market=CDC_DOT
https://www.cryptopia.co.nz/Exchange?market=CDC_LTC
https://www.cryptopia.co.nz/Exchange?market=CDC_DOGE
https://www.cryptopia.co.nz/Exchange?market=CDC_FTC
https://www.cryptopia.co.nz/Exchange?market=CDC_POP
https://www.cryptopia.co.nz/Exchange?market=CDC_HTML5
https://www.cryptopia.co.nz/Exchange?market=CDC_UNO



Block-Exlporer
https://www.cryptopia.co.nz/BlockExplorer?coin=CDC

Marektplace
https://www.cryptopia.co.nz/MarketPlace

Coin-Info
https://www.cryptopia.co.nz/CoinInfo

Pool works now

2% Fee

https://www.cryptopia.co.nz/MineShaft?pool=CDC

What about deposits in Bter ???

I contacted bter two weeks ago to let them know of the block explorers, source availability on github, new checkpoints etc. No response. This has happened a few times now. :-\

the client appear 'checkpoint is too old...'

That's just a warning, not an error, pointing out that the last hardened checkpoint is more than 3 months old. I will probably release a new maintenance version soon.

I am also still working with bter to get CDC working again, but there have been some technical issues.

sounds good :)

Just a note that I've given bter another poke. For those of you who have been with CDC for a while, you probably already know that it can take a long time for bter to get things moving again, especially if things don't work first time (it looks like their client staked and forked). I'll continue to remind them.

1gh/s hashrate diff 13 now

whats happend???

Lots of PoS blocks right now, pushing up PoW difficulty.

http://www.almightycoins.org/explorer/cloudcoin/list/892849

ok bter is on the right chain, they work on it ;)

guess bter not yet ready, anyone managed to make deposit?

I've sent another reminder. :-\

You can trade here also: https://www.cryptopia.co.nz/Exchange?market=CDC_BTC

I'll do it tomorrow and still have a ticket open!

if any they are annoying already react! ;)

Although it's very quiet here, the total hashrate is currently 443 MH/s @ diff 4.12
Anyone alive?

Yep. Happy new year. :D

Still waiting on bter to re-enable deposits. It's been half a year.

Isn't it too risky? I stopped trading there but read from other users about missing balances, forever pending withdrawals and so on.

Still Waiting on BTER. Any word anyone how that is going?

dev, any contact or response from bter ?

I'll be releasing another hardened checkpoint update soon, hopefully within a day or two, and at that time I will point bter towards the github link and ask again that they fix deposits.

THANKSYOU!!!!!  :)

that's good news, last week there is a trading volume raising on bter...

hey dev, i just saw bter is delisted CDC, did you contact them ?

CDC is online here with a node

366 Coins added

https://crypto-trade.net/

https://github.com/txbits/txbits

https://txbits.org/

    What is the Crypto-Trade?

    Crypto-Trade provides trade cryptocurrency between users, they contain funds to secure accounts and provides a quick and reliable service .

Copyright © 2014-2015 Crypto-Trade Powered by TxBits

where can i download wallet version 1.3.3 for windows ?

Any news lately?

CDC / BTC market is closing

Delisting due to irreparable wallet issue



https://www.cryptopia.co.nz/Exchange/?market=CDC_BTC

Still trying to negotiate the delisting. I've had a ticket open since June offering help.

Sweet  ;)

Is the wallet working?

Should be. What's the problem?

Still working on the Cryptopia delisting issue. My tickets go weeks without a reply.

+1

I need someone to give me this version of the wallet.

Thank

I've checked my notes and the github commits, and I don't think there has been a 1.3.3 Windows wallet released. The only difference between 1.3.2 and 1.3.3 (apart from the version id) is that there's some extra code to ban peers that have forked and are repeatedly requesting the same blocks. There is no other change.

I do not understand, you mean that there has been a difurcacion in the block chain? What is the number of coins in circulation, I was thinking of buying some but seeing this I will think about it, there is only one exchange and it may be distilled.

No, I don't mean the blockchain has forked, just that some peers go off track. There are some IPs that are still using older versions from years ago, and they just request the same blocks over and over, without ever syncing. That's why the newer code bans them.

Current supply is 40 million CDC.

answer by cryptopia

Sender: Peter_O9/14/2017 1:05:50 AM

Hi ,

The devs at Cryptopia take coin delistings seriously, each case is carefully considered on a number of factors. The CDC delist is final and to be processed as scheduled on our News page.

Kind regards,
Cryptopia Support

It is estimated that more than 7 million coins have been lost that will not leave that market.

Lost? You mean they're not allowing customers to withdraw those funds?

Cryptopia seem to be having sudden problems with various coin clients, even though other exchanges do not report any issues with the same clients.  :-X

If I mean lost because I lost in that market 3.7 million Xedoscoin, if you look at the nodes in cryptopia do not work so nobody can take out their coins and the worst thing is that they erase the balances of the currencies that are unlisted .

So it's a good time to buy CDC

@almightyruler

is there any other exchange that CDC is trading now?

I think Nova is the only one. With the fiat value of BTC increasing the value of alts is dropping to match, so CDC has been on a decline. It's now difficult to sell at 1 sat.

@almightyruler

the block explorer from your site is not working for me as of yesterday, please check it out

Sorry about that, I shut down the client momentarily but forgot to restart.

It's syncing now so by the time you read this the block explorer should be up to date.

Now if it looks bad for CDC, novaexchange closes and we are left without a market.

Some solution to this, someone has the intention of trying to place the currency in some other exchange and try to re-launch it is a 2013 coin one of the first and a shame that has an end like that.

regards   ??? >:(

Does anyone know what happens with the explorer and the nodes? can someone solve it?

Thanks

cloudcoin client crashed a couple of days ago.

Looks like there were some big chain reorganisations prior to the crash, so it's possible we have a fork. (This may also explain the issues with Novaexchange's CDC client).

I've restarted it with an older database backup in the hope that it syncs to the current block cleanly.

thanks, it seems that the problem is already working.

novaexchange is dead, his would be to take this coin to another stronger market like yobit.

I will suggest the dev to contact nova support to update the client or with the fix. Nova daemon/wallet showing last block on 20 Feb. Nova is relaunching, so it will be a good opportunity for community :) Good luck

novaexchange is live!!! 8)

Where to find version 1.3.3 for Windows?


 ???

Hello,

After a review of my notes, I don't think there is a compiled EXE of 1.3.3, but that's because the change from 1.3.2 to 1.3.3 was very small: some extra code to ban peers who appear to be forked. Otherwise, it is identical to 1.3.2, so it's fine to use that.

who can give some active nodes info?

See https://www.almightycoins.org/explorer/cloudcoin/peers

Currently:

addnode=149.28.164.168
addnode=79.152.186.27
addnode=46.101.126.142
addnode=89.40.4.195
addnode=60.186.53.201

can connect  now,thank you

Hi! Wallet is not synchronized, what to do?

Which version? Do you have peers connected? What is your current block height?

wallet v1.3.2.0
peers 1 or 0
block 967500 in 2584429.

Do you know how to set up addnodes in cloudcoin.conf? If so, see this URL: https://www.almightycoins.org/explorer/cloudcoin/peers

If not, assuming you are using the Windows client (cloudcoin-qt.exe), you can also try starting it manually from the commandline, including the addnodes:

c:\path\to\cloudcoin-qt.exe -addnode=91.121.221.51 -addnode=149.28.164.168

91.121.221.51 is a 24/7 server so that should be sufficient to connect to and find other peers.

Hope this helps.

Thank you, like helped. Synchronization is in progress, 68%. Then write, when will the end result.

Unfortunately nothing happened.
1.   If you just run the wallet with (-addnode=91.121.221.51 -addnode=149.28.164.168). Then there is the synchronization, but then the wallet crashes and all.
2.   If you copy the wallet file.dat into a new folder and re-sync (-addnode=91.121.221.51 -addnode=149.28.164.168). Then there is the synchronization, but then in my wallet and lost all the coins.

Can you explain further what happens when the wallet crashes? Is it immediate or does it occur after some time? What is the error shown? What size is your wallet.dat file?

CloudCoin has been listed in enmanet Exchange:   https://enmanet.com/market/BTC-CDC  happy trading!  :D

In the first case, the wallet freezes and the program does not respond to any action. Synchronization stops somewhere around 70% percent. The program "hangs" a day or more without reacting or any action. I didn't wait for it to finish and turned it off.
In the second case, the wallet goes through a full synchronization, during the process, transactions are shown, but when the synchronization comes to the end, I somehow disappear all the coins. On the balance of 0 coins.
File size 936 KB

Hi, I've followed this up in PM.

Remember that  now you can exchange our favorite currency CDC in Nova Exchange

https://novaexchange.com/market/DOGE_CDC/
https://novaexchange.com/market/MOON_CDC/

Happy Trade ....  :)

RAIDATech - Be a part of History! / RAIDA vs Blockchain / CloudCoin vs Crypto / : https://www.publish0x.com/cloudcoin/raidatech-be-part-history-raida-vs-blockchain-cloudcoin-vs-c-xknxgp

This thread is for the CloudCoin which started in 2013. It has nothing to do with the above coin.

node for Cloudcoin[CDC]:(2013)
addnode=185.87.149.61:12344