Topic: {ANN} CDC|Cloudcoin 2.0 COMING - Ultimate Official Thread|TRADED ON BTER| - page 4. (Read 25621 times)
January 17, 2014, 11:10:28 AM
作者在吗？bter为什么网站的首页没有CDC的,这很不公平啊！
January 17, 2014, 09:11:01 AM
Damn, ppl fall for cloudcoin again 
January 17, 2014, 09:04:40 AM
Was such a waist of time, power and hash. Disappointed. 
January 17, 2014, 09:00:52 AM
CDC 什么情况啊！
January 14, 2014, 09:51:57 AM
Let this shitcoin die 
January 14, 2014, 09:38:41 AM
Thanks! I'm at block 223930. does that seem right?
Yes, that seems to be the current block number for the network. Remember it's stuck in proof-of-stake only mode, you cannot mine.
And this "redemption" thing on the website saying "send coins to me" and I will send them back. Is this for real or a scam?
The original dev of this coin used multiple accounts as shills when launching this coin, to try to drum up interest (and even pose as a fake investor). Look at his reputation score on here, then consider whether sending all your CDC to him is a good idea.
As far as a block explorer, I don't think one exists, unfortunately.
January 14, 2014, 09:14:06 AM
has anyone successfully got their coins to Bter.com to trade?
Yes, a few days ago. It took a day or two to fully confirm because of the small number of proof-of-stake blocks that were being minted.
I sent 1 CDC to bter to test on the 11th at the moment it shows 266 confirms, but still noting at Bter.com. I pressed the "sync" button but nothing
are there any working explorers where i can view the transaction?
January 14, 2014, 08:45:18 AM
SCAM...don't send your coins to anyone !!!!!
January 14, 2014, 08:34:35 AM
has anyone successfully got their coins to Bter.com to trade?
Yes, a few days ago. It took a day or two to fully confirm because of the small number of proof-of-stake blocks that were being minted.
Thanks! I'm at block 223930. does that seem right?
And this "redemption" thing on the website saying "send coins to me" and I will send them back. Is this for real or a scam?
January 14, 2014, 07:57:43 AM
has anyone successfully got their coins to Bter.com to trade?
Yes, a few days ago. It took a day or two to fully confirm because of the small number of proof-of-stake blocks that were being minted.
January 14, 2014, 07:21:24 AM
has anyone successfully got their coins to Bter.com to trade?
January 09, 2014, 10:45:43 AM
Cloudcoin now there is no technology to maintain it? Cloudcoin when longer active again? We look forward to more than a month. 
January 09, 2014, 05:29:22 AM
This was also recently posted by someone who seems to know what they're talking about. Reproducing here as he doesn't have full post access yet.
My understanding of this explanation is that because Cloudcoin places so much value on proof-of-stake blocks (much more so than other coins) it is possible for a rogue node that owns sufficient coins to override (cancel) most mined blocks... which coincidentally is what has been happening for months.
Message follows:
almightyruler, Guess I need to post in the noob forum first. Been following what you've posted on the main CDC thread and have also been curious about the issues with this coin.
The way the chain trust is calculated on CDC is the issue. It puts a very high trust on the stake blocks relative to the work blocks.
No other POS+POW coin that I looked at calculates block trust this way. The value generated for a proof of stake block is weighted far higher than a work block. Each work block increments the block trust value by 1, each stake block is trusted by over a million.
The first generated stake block in the log for example.
This alone wouldn't necessarily cause the clipping to occur. Each client should still receive the mined blocks and place its POS blocks at the end of the chain. Either it was a client on the network that excessively slow at receiving new blocks or a modified client that only will accept POS blocks and reject POW blocks. I'm assuming the later. If a "good client" submitted a POS block, the POW blocks mined since the last POS would be accepted and the "bad client" would accept the longer chain. Someone with a lot of coins, maybe a million premine, would possibly do this
. I was going to test this with some CDC that should generate a stake in a couple days, but mining has now become impossible.
Also mining the coin recently locked due to a miner setting their clock back by over 700 seconds from the previous mined block. That set the target for the next block to be below zero. The client will reject any block with a target of zero or less in the CheckProofOfWork call. It's a simple fix and I was able to mine a few blocks. Since it affects the method of calculating difficulty, blocks I generate are rejected by the network. Unfortunately it would require a client update. Also this could also be an issue for any coin that retargets its difficulty every mined block.
My understanding of this explanation is that because Cloudcoin places so much value on proof-of-stake blocks (much more so than other coins) it is possible for a rogue node that owns sufficient coins to override (cancel) most mined blocks... which coincidentally is what has been happening for months.
Message follows:
Isn't the 1,000,000 CDC showing for the first couple of hours on cryptometer simply the massive premine? It's right there in the client code:
First block? Grant a million CDC to the miner.
Code:
if(nHeight == 1)
{
nSubsidy = 1000000 * COIN;
}
{
nSubsidy = 1000000 * COIN;
}
First block? Grant a million CDC to the miner.
almightyruler, Guess I need to post in the noob forum first. Been following what you've posted on the main CDC thread and have also been curious about the issues with this coin.
The way the chain trust is calculated on CDC is the issue. It puts a very high trust on the stake blocks relative to the work blocks.
Code:
(IsProofOfStake()? (CBigNum(1)<<256) / (bnTarget+1) : 1)
No other POS+POW coin that I looked at calculates block trust this way. The value generated for a proof of stake block is weighted far higher than a work block. Each work block increments the block trust value by 1, each stake block is trusted by over a million.
The first generated stake block in the log for example.
Code:
SetBestChain: new best=00000002d220876cda59 height=12409 trust=12410 date=08/02/13 12:30:41
SetBestChain: new best=000000014a6b9e2a2cce height=12410 trust=12411 date=08/02/13 12:31:02
SetBestChain: new best=e7616b332a619fc2099e height=12411 trust=1060988 date=08/02/13 12:33:07
SetBestChain: new best=000000014a6b9e2a2cce height=12410 trust=12411 date=08/02/13 12:31:02
SetBestChain: new best=e7616b332a619fc2099e height=12411 trust=1060988 date=08/02/13 12:33:07
This alone wouldn't necessarily cause the clipping to occur. Each client should still receive the mined blocks and place its POS blocks at the end of the chain. Either it was a client on the network that excessively slow at receiving new blocks or a modified client that only will accept POS blocks and reject POW blocks. I'm assuming the later. If a "good client" submitted a POS block, the POW blocks mined since the last POS would be accepted and the "bad client" would accept the longer chain. Someone with a lot of coins, maybe a million premine, would possibly do this
. I was going to test this with some CDC that should generate a stake in a couple days, but mining has now become impossible. Also mining the coin recently locked due to a miner setting their clock back by over 700 seconds from the previous mined block. That set the target for the next block to be below zero. The client will reject any block with a target of zero or less in the CheckProofOfWork call. It's a simple fix and I was able to mine a few blocks. Since it affects the method of calculating difficulty, blocks I generate are rejected by the network. Unfortunately it would require a client update. Also this could also be an issue for any coin that retargets its difficulty every mined block.
January 09, 2014, 05:16:02 AM
Proof-of-work blocks are stalled due to two blocks being out of sequence. CDC (and other coins with the same parent source that hit a negative time between blocks) will not mint any further PoW blocks until the code is fixed. It's very simple to fix this particular problem, but getting people to upgrade will be the difficult part... and there's also other issues with CDC (such as the PoS blocks reversing PoW from mining) which would still be a problem.
In summary, as of this moment:
1. You can send and receive CDC, but it could take 24+ hours for enough PoS blocks to go through the network to confirm the transaction.
2. You cannot mine CDC at all. The clients and network will not accept any PoW blocks.
In summary, as of this moment:
1. You can send and receive CDC, but it could take 24+ hours for enough PoS blocks to go through the network to confirm the transaction.
2. You cannot mine CDC at all. The clients and network will not accept any PoW blocks.
January 08, 2014, 04:45:43 AM
my client says out of sync and it gives message about checkpoint too old contact developer
January 06, 2014, 10:03:00 PM
Cloudcoin live?
January 03, 2014, 11:52:43 PM
Things have gone from bad to worse. Around 8 hours ago there was another "window of opportunity" for about 8 minutes where PoW blocks were accepted by the network. Since that time, there have been no further PoW blocks making it to the network at all... which is different to the cycle we've seen in recent days where PoW blocks are accepted, then reversed. It seems to be the client that is ignoring them now; cgminer never reports "Accepted," only "Rejected"
This may be the same thing that's happening to Orbitcoin: a corrupt PoS block prevents any further PoW blocks. If what someone said on a thread about that coin is correct, this is the end of mining, until there's a dev fix.
This may be the same thing that's happening to Orbitcoin: a corrupt PoS block prevents any further PoW blocks. If what someone said on a thread about that coin is correct, this is the end of mining, until there's a dev fix.
January 03, 2014, 09:28:28 AM
In the past 48 hours there has only been one very brief period where found PoW blocks were not rejected by the network. It lasted for 40 seconds only. For the other 172760 seconds every PoW block was reversed.
Money supply has gone up by 4600 CDC in 48 hours. It should have gone up by at least 144000 CDC.
This coin is effectively dead until someone fixes the problem.
Money supply has gone up by 4600 CDC in 48 hours. It should have gone up by at least 144000 CDC.
This coin is effectively dead until someone fixes the problem.
January 01, 2014, 10:23:16 PM
This graph demonstrates found PoW blocks being periodically reversed over a roughly 2 hour period. The network is propagating those PoW blocks, several in sequence, then for some reason the network readjusts the chain, which revokes all of the PoW blocks.
Note that this data is based on passive network monitoring, it has nothing to do with my own mining efforts.
January 01, 2014, 07:58:27 PM
People holding their coins are making a small amount of interest via PoS, but miners trying to create new coins are having no luck.
Clearly it demonstrates how PoS is superior to PoW and how the rich don't control the network and become richer! Jump to: