[ANN] Catcoin - 0.9.1.1 - Old thread. Locked. Please use 0.9.2 thread.

[rampa]

Hi. Thats rampa from manicminer.in

 How to know i am in the good chain?

  I downloaded the github source. my actuakl block number is 27789. but diff is really low. 3.65099479,

 Is this correct?

You are on the wrong chain.  You will have to delete the following in your .catcoin directory, and then re-sync:
blocks
chainstate
peers.dat

4 connections, but is not starting to  download blocks :-(

 any special addnode?

[rampa]

Hi. Thats rampa from manicminer.in

 How to know i am in the good chain?

  I downloaded the github source. my actuakl block number is 27789. but diff is really low. 3.65099479,

 Is this correct?

You are on the wrong chain.  You will have to delete the following in your .catcoin directory, and then re-sync:
blocks
chainstate
peers.dat

4 connections, but is not starting to  download blocks :-(

 any special addnode?

 Ops. my dfault. downloading now,,,,

[vetalysd]

VOTE FOR CATCOIN

please donate for dev.
BTC: 13MVMftimCmpQEsryo47pTs97ubmwkT31Y
LTC: Lh9ChfS1X3YWXmapr66nQjj3qZmys3qkNw
DOGE: DJMxzVrURhmsWFZHCjK5kDVHEqP5FcfGvy

[tekke]

Hello Dev team, I've been a CAT supporter since day one, all the coins that I have traded have been mined by me. A few days ago, I made a withdrawal from Coinex  , they gave me a TX ID but the coins never got to my address , I'm thinking they went in the wrong chain. Could you please check it out and tell me if I'm right ?

Withdrawal | 464.38722127 CAT
Destination: 9hCRptCe4LaF18zxUFB1qZ8ynXFYy7CKHU
TXID: 78a41d37b455fa029e00bbf4d447639bf86f642343b7ec911f25664b3ef54cfd

If they went in the wrong chain , does it mean that they are lost forever? that would be very sad , since it was almost 1/3 of my coins ( I mine with a HD7770). Hope you can help me.
thanks in advance

[catoshi]

Hello Dev team, I've been a CAT supporter since day one, all the coins that I have traded have been mined by me. A few days ago, I made a withdrawal from Coinex  , they gave me a TX ID but the coins never got to my address , I'm thinking they went in the wrong chain. Could you please check it out and tell me if I'm right ?

Withdrawal | 464.38722127 CAT
Destination: 9hCRptCe4LaF18zxUFB1qZ8ynXFYy7CKHU
TXID: 78a41d37b455fa029e00bbf4d447639bf86f642343b7ec911f25664b3ef54cfd

If they went in the wrong chain , does it mean that they are lost forever? that would be very sad , since it was almost 1/3 of my coins ( I mine with a HD7770). Hope you can help me.
thanks in advance

IT should be sent instantly and fully confirmed shortly after.  Have you followed up with the exchange.

[SlimePuppy]

DEV FLASH

It appears that the CoinEX CAT mining pool is not yet running V0.9.0-PID code.  While we do have multiple support tickets open with them, we cannot yet confirm that the exchange or pools are running the correct code or are on the 'live' fork.

We recommend that nobody use either the CoinEX exchange or mining pool until we confirm they are running the latest code and are on the current fork.

DEV FLASH

FYI Folks...

[SlimePuppy]

Hello Dev team, I've been a CAT supporter since day one, all the coins that I have traded have been mined by me. A few days ago, I made a withdrawal from Coinex  , they gave me a TX ID but the coins never got to my address , I'm thinking they went in the wrong chain. Could you please check it out and tell me if I'm right ?

Withdrawal | 464.38722127 CAT
Destination: 9hCRptCe4LaF18zxUFB1qZ8ynXFYy7CKHU
TXID: 78a41d37b455fa029e00bbf4d447639bf86f642343b7ec911f25664b3ef54cfd

If they went in the wrong chain , does it mean that they are lost forever? that would be very sad , since it was almost 1/3 of my coins ( I mine with a HD7770). Hope you can help me.
thanks in advance

tekke - CoinEX was down recovering from being hacked/attacked when we upgraded to V0.9.0 code.  We have multiple tickets open with them to make sure they're updated and surfing the correct chain but so far we have not received a response from them.  They have the ability to recover the coins and resend them on the live block chain, but you'll likely have to open a support ticket with them to get action.  There's nothing else we on the dev team can do to get CoinEX moving.

Andy

[tekke]

Thanks a lot for your response. I have  open a support ticket with them but so far 0 answer. This whole hacked/scam/fucked up exchanges thing that is going on in the crypto community is ruining everything.

[xZork]

I have tried twice now to get the client up-to-date and I get stuck at block 27453, That is the current block, but I show 7 hours behind.

[vondi1122]

Hi guys,

any new announcements so far? How is the new difficulty algorithm working? Are there any plans for the future concerning development/marketing so far?

Greetings and good luck
vondi1122

[SlimePuppy]

DEV FLASH

We have released a new Windows wallet binary package.  This is to fix the OpenSSL security flaw dubbed HeartBleed.
This is a mandatory upgrade.  While there is a complete readme.txt file in the package, it should require only deleting the old binary and replacing it with this new V0.9.0.1 wallet qt file.  After running the new wallet, we recommend you change your password if you encrypt the wallet.

A new Mac wallet is forthcoming.  Unix users, pools, and exchanges do not have to update catcoind binaries as they can update their OpenSSL package separately.  The only difference between the V0.9.0 and V0.9.1 wallet binaries are the contents of the OpenSSL library - there is no change to the CATcoin wallet other than the linked library - OpenSSL 1.0.1g.


MS Windows Wallet packages are available in two flavors:

Self-extracting 7zip archive:
http://www.catcoinwallets.com/win/catcoin0901.exe
SHA256: E3DF82C14C51BC8D62D6FCD5E9935E79CF0E5FB103D0429147A5F51915B8A9B1

Regular zip archive:
http://www.catcoinwallets.com/win/catcoin0901.zip
SHA256: 6E0B017BFC8F1951212F1237E7F37B22EFDC85BB8EA745A0603C97510E248219

If you want to build a Windows catcoind.exe or wallet from source, the source is here:
https://github.com/CatcoinOfficial/CatcoinRelease

And build instructions are here:
http://www.catcoinwallets.com/win/catcoin_wallet_build_windows.pdf

DEV FLASH

[catoshi]

DEV FLASH

We have released a new Windows wallet binary package.  This is to fix the OpenSSL security flaw dubbed HeartBleed.
This is a mandatory upgrade.  While there is a complete readme.txt file in the package, it should require only deleting the old binary and replacing it with this new V0.9.0.1 wallet qt file.  After running the new wallet, we recommend you change your password if you encrypt the wallet.

A new Mac wallet is forthcoming.  Unix users, pools, and exchanges do not have to update catcoind binaries as they can update their OpenSSL package separately.  The only difference between the V0.9.0 and V0.9.1 wallet binaries are the contents of the OpenSSL library - there is no change to the CATcoin wallet other than the linked library - OpenSSL 1.0.1g.


MS Windows Wallet packages are available in two flavors:

Self-extracting 7zip archive:
http[Suspicious link removed]
SHA256: E3DF82C14C51BC8D62D6FCD5E9935E79CF0E5FB103D0429147A5F51915B8A9B1

Regular zip archive:
http://www.catcoinwallets.com/win/catcoin0901.zip
SHA256: 6E0B017BFC8F1951212F1237E7F37B22EFDC85BB8EA745A0603C97510E248219

If you want to build a Windows catcoind.exe or wallet from source, the source is here:
https://github.com/CatcoinOfficial/CatcoinRelease

And build instructions are here:
http://www.catcoinwallets.com/win/catcoin_wallet_build_windows.pdf

DEV FLASH

[vondi1122]

DEV FLASH

We have released a new Windows wallet binary package.  This is to fix the OpenSSL security flaw dubbed HeartBleed.
This is a mandatory upgrade.  While there is a complete readme.txt file in the package, it should require only deleting the old binary and replacing it with this new V0.9.0.1 wallet qt file.  After running the new wallet, we recommend you change your password if you encrypt the wallet.

A new Mac wallet is forthcoming.  Unix users, pools, and exchanges do not have to update catcoind binaries as they can update their OpenSSL package separately.  The only difference between the V0.9.0 and V0.9.1 wallet binaries are the contents of the OpenSSL library - there is no change to the CATcoin wallet other than the linked library - OpenSSL 1.0.1g.


MS Windows Wallet packages are available in two flavors:

Self-extracting 7zip archive:
http://www.catcoinwallets.com/win/catcoin0901.exe
SHA256: E3DF82C14C51BC8D62D6FCD5E9935E79CF0E5FB103D0429147A5F51915B8A9B1

Regular zip archive:
http://www.catcoinwallets.com/win/catcoin0901.zip
SHA256: 6E0B017BFC8F1951212F1237E7F37B22EFDC85BB8EA745A0603C97510E248219

If you want to build a Windows catcoind.exe or wallet from source, the source is here:
https://github.com/CatcoinOfficial/CatcoinRelease

And build instructions are here:
http://www.catcoinwallets.com/win/catcoin_wallet_build_windows.pdf

DEV FLASH

proud of our developers thumbs up

[bonesoul]

http://cat.coinium.org/

Coinium.org Network: http://www.coinium.org/
Graphs: http://www.coinium.org/pool/CAT

Updated to v0.9.0.1

[vondi1122]

its going up guys, take your chances

[vetalysd]

VOTE FOR CATCOIN

please donate for dev.
BTC: 13MVMftimCmpQEsryo47pTs97ubmwkT31Y
LTC: Lh9ChfS1X3YWXmapr66nQjj3qZmys3qkNw
DOGE: DJMxzVrURhmsWFZHCjK5kDVHEqP5FcfGvy

[niothor]

its going up guys, take your chances

Just don't do the cat dump

[catoshi]

its going up guys, take your chances

Just don't do the cat dump

Real love is forever

[coinme.info]

Hi, hope someone can help with the new wallet not syncing past block 27619

FYI.

New Install of Win8.1 64

First time install of new wallet 9.0.1 from catcoin official web site.

1st attempt. Install Wallet, did not copy conf from wallet download to /apdata/catcoin folder, begin sync, stuck block 27619

2nd attempt. Delete everything in /appdata/catcoin folder except wallet.dat, added conf file from download zip with nodes only, resync stops at 27619

3rd attempt. Delete everything in /appdata/catcoin folder except wallet.dat, resync stops at 27619.

This from the debug log.

Code:

2014-04-20 22:41:48 Invalid or missing peers.dat; recreating
2014-04-20 22:41:48 Loaded 0 addresses from peers.dat  1ms
2014-04-20 22:41:51 mapBlockIndex.size() = 1
2014-04-20 22:41:51 nBestHeight = 0
2014-04-20 22:41:51 setKeyPool.size() = 100
2014-04-20 22:41:51 mapWallet.size() = 3
2014-04-20 22:41:51 mapAddressBook.size() = 2
2014-04-20 22:41:51 AddLocal([2001:0:5ef5:79fb:14af:c6b3:d106:c423]:9933,1)
2014-04-20 22:41:51 dnsseed thread start
2014-04-20 22:41:51 Loading addresses from DNS seeds (could take a while)
2014-04-20 22:41:51 addcon thread start
2014-04-20 22:41:51 net thread start
2014-04-20 22:41:51 opencon thread start
2014-04-20 22:41:51 dumpaddr thread start
2014-04-20 22:41:51 msghand thread start
2014-04-20 22:41:51 upnp thread start
2014-04-20 22:41:51 init message: Done loading
2014-04-20 22:41:51 AddToWallet a34dee0ef4594d6421a04685f49d432619c0ce1da85aff03cb7bcf26310fdb35  
2014-04-20 22:41:51 AddToWallet c8e062d5ea616f6c1f98da05472b2a3433939c5b193013ce95b30a7ce680fc52  
2014-04-20 22:41:51 AddToWallet f7e38a3dce7dffa97005743cb3effe3269a536c356a2d5e59a583136524af07d  
2014-04-20 22:41:51 refreshWallet
2014-04-20 22:41:53 Added 1 addresses from 107.170.40.107: 0 tried, 1 new
2014-04-20 22:41:53 trying connection 107.170.40.107:9933 lastseen=135.7hrs
2014-04-20 22:41:54 connected 107.170.40.107:9933
2014-04-20 22:41:54 send version message: version 70002, blocks=0, us=[2001:0:5ef5:79fb:14af:c6b3:d106:c423]:9933, them=107.170.40.107:9933, peer=107.170.40.107:9933
2014-04-20 22:41:54 UPnP: ExternalIPAddress = 10.0.0.34
2014-04-20 22:41:54 UPnP Port Mapping successful.
2014-04-20 22:41:54 Added time data, samples 2, offset +2 (+0 minutes)
2014-04-20 22:41:54 Moving 107.170.40.107:9933 to tried
2014-04-20 22:41:54 receive version message: /Satoshi:0.9.0/: version 70002, blocks=27619, us=46.249.59.220:1982, them=107.170.40.107:9933, peer=107.170.40.107:9933
2014-04-20 22:41:54 Added 2 addresses from 65.254.66.160: 1 tried, 2 new

Could this node be the problem? 2nd line at the end of log snippet above

2014-04-20 22:41:54 receive version message: /Satoshi:0.9.0/: version 70002, blocks=27619, us=46.249.59.220:1982, them=107.170.40.107:9933, peer=107.170.40.107:9933


UPDATE: After checking the wallet again it is now syncd and over the fork block.

Looks like it finally found a node that had the correct blockchain. Still think the original node in the wallet might have issues.

[Blaksmith]

Hi, hope someone can help with the new wallet not syncing past block 27619

FYI.

New Install of Win8.1 64

First time install of new wallet 9.0.1 from catcoin official web site.

1st attempt. Install Wallet, did not copy conf from wallet download to /apdata/catcoin folder, begin sync, stuck block 27619

2nd attempt. Delete everything in /appdata/catcoin folder except wallet.dat, added conf file from download zip with nodes only, resync stops at 27619

3rd attempt. Delete everything in /appdata/catcoin folder except wallet.dat, resync stops at 27619.

This from the debug log.

Code:

2014-04-20 22:41:48 Invalid or missing peers.dat; recreating
2014-04-20 22:41:48 Loaded 0 addresses from peers.dat  1ms
2014-04-20 22:41:51 mapBlockIndex.size() = 1
2014-04-20 22:41:51 nBestHeight = 0
2014-04-20 22:41:51 setKeyPool.size() = 100
2014-04-20 22:41:51 mapWallet.size() = 3
2014-04-20 22:41:51 mapAddressBook.size() = 2
2014-04-20 22:41:51 AddLocal([2001:0:5ef5:79fb:14af:c6b3:d106:c423]:9933,1)
2014-04-20 22:41:51 dnsseed thread start
2014-04-20 22:41:51 Loading addresses from DNS seeds (could take a while)
2014-04-20 22:41:51 addcon thread start
2014-04-20 22:41:51 net thread start
2014-04-20 22:41:51 opencon thread start
2014-04-20 22:41:51 dumpaddr thread start
2014-04-20 22:41:51 msghand thread start
2014-04-20 22:41:51 upnp thread start
2014-04-20 22:41:51 init message: Done loading
2014-04-20 22:41:51 AddToWallet a34dee0ef4594d6421a04685f49d432619c0ce1da85aff03cb7bcf26310fdb35  
2014-04-20 22:41:51 AddToWallet c8e062d5ea616f6c1f98da05472b2a3433939c5b193013ce95b30a7ce680fc52  
2014-04-20 22:41:51 AddToWallet f7e38a3dce7dffa97005743cb3effe3269a536c356a2d5e59a583136524af07d  
2014-04-20 22:41:51 refreshWallet
2014-04-20 22:41:53 Added 1 addresses from 107.170.40.107: 0 tried, 1 new
2014-04-20 22:41:53 trying connection 107.170.40.107:9933 lastseen=135.7hrs
2014-04-20 22:41:54 connected 107.170.40.107:9933
2014-04-20 22:41:54 send version message: version 70002, blocks=0, us=[2001:0:5ef5:79fb:14af:c6b3:d106:c423]:9933, them=107.170.40.107:9933, peer=107.170.40.107:9933
2014-04-20 22:41:54 UPnP: ExternalIPAddress = 10.0.0.34
2014-04-20 22:41:54 UPnP Port Mapping successful.
2014-04-20 22:41:54 Added time data, samples 2, offset +2 (+0 minutes)
2014-04-20 22:41:54 Moving 107.170.40.107:9933 to tried
2014-04-20 22:41:54 receive version message: /Satoshi:0.9.0/: version 70002, blocks=27619, us=46.249.59.220:1982, them=107.170.40.107:9933, peer=107.170.40.107:9933
2014-04-20 22:41:54 Added 2 addresses from 65.254.66.160: 1 tried, 2 new

Could this node be the problem? 2nd line at the end of log snippet above

2014-04-20 22:41:54 receive version message: /Satoshi:0.9.0/: version 70002, blocks=27619, us=46.249.59.220:1982, them=107.170.40.107:9933, peer=107.170.40.107:9933


UPDATE: After checking the wallet again it is now syncd and over the fork block.

Looks like it finally found a node that had the correct blockchain. Still think the original node in the wallet might have issues.

Nope, that node is valid, as the 0.9.0.1 version is "only" for the Windows and Mac pre-compiled versions for the HeartBleed bug security fix.  Any version reporting as 0.9.0 is most likely a linux system.  Manually compiled versions on linux systems use the libraries installed on the system, and are not required to have the version bump.

The reason you "seemed" stuck on block 27619, was because that was the last block at the time, and there was an extended period of time before the next block.  Once more blocks were found, your wallet showed sync'd up.

Blak