Topic: [ANN][CDC] CLOUDCOIN REVIVAL. PoW/PoS. ** LATEST MARCH 2015 OPENSSL FIX ** - page 13. (Read 41382 times)
April 15, 2014, 04:21:28 AM
almightyruler ， If you continue to play like this steal the blocks ,nobody play with you , you will be personally killed the coin CLOUDCOIN.!!!!!!!!!!!!
April 15, 2014, 04:14:19 AM
Brothers show mercy ah, give way to the man. Don't steal that block 
April 15, 2014, 04:07:38 AM
i put in my payout info and the coins are still in the pool is there a problem with the pool payouts
April 15, 2014, 03:40:16 AM
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?
. The transactions are seems to be OK but nothing turning on in the balance. Any idea? 
April 15, 2014, 03:37:48 AM
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. ***
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:
Code:
listen=0
connect=85.17.81.169
connect=107.170.49.232
*** 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. ***
cloudcoind -listen=0 -connect=85.17.81.169 -connect=107.170.49.232
Your node steal block
This is not good
Even steal, do not steal so much, In order to develop our CDC, show mercy please,thank you!
April 14, 2014, 07:42:36 PM
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. ***
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:
Code:
listen=0
connect=85.17.81.169
connect=107.170.49.232
*** 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. ***
April 14, 2014, 10:02:20 AM
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)
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)
But the actual situation is ban time for an hour, we found this situation, Temporary exchange the pool IP, renew synchronization,or,Will happen to mine disarster, AH
In addition, if the CDC wallet was always so easy to forking, that would be a very serious problem
April 14, 2014, 09:51:51 AM
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)
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)
April 14, 2014, 09:45:38 AM
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
Now is the firewall
It does not connect the two nodes, wallet again cannot be synchronized
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.
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!
April 14, 2014, 09:14:07 AM
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??
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.
April 14, 2014, 09:09:07 AM
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
Now is the firewall
It does not connect the two nodes, wallet again cannot be synchronized
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.
April 14, 2014, 08:09:30 AM
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??
April 14, 2014, 08:05:29 AM
-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
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
April 14, 2014, 07:09:33 AM
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
LOVE THE GIRL
http://cdc.okaypool.com
LOVE THE POOL
https://bter.com/trade/cdc_btc
LOVE THE EXCHAGES
LETS GO
April 14, 2014, 01:41:47 AM
April 13, 2014, 10:46:28 AM
OH My God, the version 1.3 without little effect, node can not synchronous
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.
April 13, 2014, 10:11:25 AM
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
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
OH My God, the version 1.3 without little effect, node can not synchronous
We found bter's wallet is not synchronous
April 13, 2014, 03:30:22 AM
Deposit addresses on bter starting with "B" : BwZqNy6JxvbJhgf..................
WTF?
WTF?
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. April 13, 2014, 03:28:38 AM
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
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
April 13, 2014, 03:19:16 AM
Deposit addresses on bter starting with "B" : BwZqNy6JxvbJhgf..................
WTF?
WTF?
Jump to: