[ANN] Catcoin - 0.9.3.0

[SlimePuppy]

A note on CRYPTSY:

They've updated their blog entry to list a number of coins that are open for withdrawal.  CAT is not yet on the list - it's still in 'maintenance' mode.

If you have other coins there, you might check-in to see if you can retrieve them.

http://blog.cryptsy.com/


Andy

[1713587211]

1713587211

[1713587211]

1713587211

[1713587211]

1713587211

[1713587211]

1713587211

[krile]

Is the development still going with this coin?

[SlimePuppy]

Is the development still going with this coin?

Yes - sure is.

[Thepuj]

I want to have mined some coins. I have selected Catcoin as my target for mining as my hardware is lousy, there are only few mining Catcoin and I love cats. With bigger coins I would mine for years before I get something. With Catcoin I hope to get something within one or two months.

I am currently mining on scryptpool. As I am the only one there I am effectively a solo miner there. Can I just really solo mine with my address in the blockchain? If so how?

Is there an official way to use Mini private keys with Catcoin?

Thanks

[Thepuj]

Am I cursed with this coin or is my mining setup borken? With another coin I can successfully mine, but with this one nothing in four times my expected duration to get a block. Why has a 100% unsupported coin such a high hash rate?

[krile]

Can someone explain this, the debug log is getting spammed constantly with this. In the last few months it grew to over 4,5GB in size. This is funny, the blockchain size is only 40MB, but the debug.log is over a hundred times bigger

Code:

2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 43442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43941 ddf6a90be42e923bdf533f7ee32e5c9ebc17cd6ea706b462bd61d65cf6792580
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30   getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30   getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65

I am killing this node if this does not get fixed.

[Blaksmith]

Can someone explain this, the debug log is getting spammed constantly with this. In the last few months it grew to over 4,5GB in size. This is funny, the blockchain size is only 40MB, but the debug.log is over a hundred times bigger

Code:

2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 43442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43941 ddf6a90be42e923bdf533f7ee32e5c9ebc17cd6ea706b462bd61d65cf6792580
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30   getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30   getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65

I am killing this node if this does not get fixed.

Unfortunately, that was the results of the last forking that happened.  You should be able to stop your catcoind, and restart it.  While it is stopped, you can delete your debug.log to free up your hdd space.  You may also want to delete your peers.dat file too, because it is still hooking on to the old forks, and your peer.dat file has old non-updated nodes listed.

[krile]

Can someone explain this, the debug log is getting spammed constantly with this. In the last few months it grew to over 4,5GB in size. This is funny, the blockchain size is only 40MB, but the debug.log is over a hundred times bigger

Code:

2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 43442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43941 ddf6a90be42e923bdf533f7ee32e5c9ebc17cd6ea706b462bd61d65cf6792580
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30   getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 43942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 44441 14146ac52e6ecc3e38affc7614611e163cf87144e86feb59756546e3d3e15e23
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 43441 2bcc859b678cfbdb4cc4d5e187103fc2aac6afb6c41eb49851127b6d76a51227
2016-03-23 15:06:30 getblocks 41442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41941 7b29260a3acc9c4f56963c39051f4681cb7fbae6b506c0d8390d5981576c73d5
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65
2016-03-23 15:06:30 getblocks 40442 to 258918baedfc92c62494f3832c3c8a27049634f61b06d27bfd10f1eb0c25b1ae limit 500
2016-03-23 15:06:30   getblocks stopping at limit 40941 576dfee71ef9ef5f80a9810c503a0f9d7aff27a680e88631c17bec76ae6401bb
2016-03-23 15:06:30 getblocks 41942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42441 a3ea38399677f2a8f4a2e166e6a9708478d2e0dcf9f1648c820b3c9eac6da1fe
2016-03-23 15:06:30 getblocks 40942 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 41441 a631d628fb2a369c4aada89a8ba54505f1855891553676f73d496cf3de1cdaff
2016-03-23 15:06:30 getblocks 42442 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2016-03-23 15:06:30   getblocks stopping at limit 42941 511e72c92803545f6d02352d3548c8e6e86b8d301853d8d7cbc4dfcbd613cc65

I am killing this node if this does not get fixed.

Unfortunately, that was the results of the last forking that happened.  You should be able to stop your catcoind, and restart it.  While it is stopped, you can delete your debug.log to free up your hdd space.  You may also want to delete your peers.dat file too, because it is still hooking on to the old forks, and your peer.dat file has old non-updated nodes listed.

Thanks for the tip. Deleted the peers.dat, for now the debug log is giving normal output. But the last time I just restarted the daemon, and it was ok in the beginning, but after a day or two it started spamming again...

Wouldnt it be a good idea to make the nodes disconnect from the outdated ones?

[krile]

Like I suspected, deleting the peers.dat did not fix this problem.

This thing is also eating my upload bandwidth, around 1MB/s...

Any other suggestions?

[Thepuj]

I got the two IP from the initial posting in this thread in my catcoin.conf. I don't get the entries you get, just something like:

2016-03-27 10:38:14 trying connection 96.125.240.228:9933 lastseen=6550.5hrs
2016-03-27 10:38:19 connection timeout

which I assume is ok. With just 7 connections it is probably trying to find more.

But I am now mining at least 6 times the expected time to find a block hash without any result. It is probably more likely that here is something wrong than it is just bad luck.

[Thepuj]

I think these are all IPs I have ever seen:

"addr" : "108.61.10.90:9933"
"addr" : "109.182.144.114:9933"
"addr" : "146.0.32.101:9933"
"addr" : "167.160.36.82:9933"
"addr" : "173.254.235.58:9933"
"addr" : "69.118.78.156:9933"
"addr" : "98.115.147.74:9933"

[krile]

I have 20 connections.

This one is causing the problem I think, the only one on an older version and you can see that the bytes sent/recieved are extremely hihg:

Code:

                                               
        "addr" : "192.99.13.67:50394",             
        "services" : "00000003",                   
        "lastsend" : 1459109854,                   
        "lastrecv" : 1459109855,                   
        "bytessent" : 183272754934,                
        "bytesrecv" : 9404197537,                  
        "blocksrequested" : 2,                     
        "conntime" : 1458895868,                   
        "version" : 70002,                         
        "subver" : "/Satoshi:0.9.1.1/",            
        "inbound" : true,                          
        "startingheight" : 48642,                  
        "banscore" : 0                             
   

There is no command to disconnect this node.

Is there an option in the .conf file to ban a node. Like opposite to "addnode=" ?

[Blaksmith]

I have 20 connections.

This one is causing the problem I think, the only one on an older version and you can see that the bytes sent/recieved are extremely hihg:

Code:

                                               
        "addr" : "192.99.13.67:50394",             
        "services" : "00000003",                   
        "lastsend" : 1459109854,                   
        "lastrecv" : 1459109855,                   
        "bytessent" : 183272754934,                
        "bytesrecv" : 9404197537,                  
        "blocksrequested" : 2,                     
        "conntime" : 1458895868,                   
        "version" : 70002,                         
        "subver" : "/Satoshi:0.9.1.1/",            
        "inbound" : true,                          
        "startingheight" : 48642,                  
        "banscore" : 0                             
   

There is no command to disconnect this node.

Is there an option in the .conf file to ban a node. Like opposite to "addnode=" ?

What I have had to do in the past, since there is no direct ban that can be done in the config file, is manually block all in and out traffic of that specific IP address.

The node should auto ban for sending crap data, but since it is not actually sending bad data, but just asking over and over and over for data, it doesn't trigger the ban for that IP.

[Thepuj]

I got with 250kHps in about 20 days nil, nothing, nichts, nada. So I finally stopped my catcoin mining.

[krile]

I have 20 connections.

This one is causing the problem I think, the only one on an older version and you can see that the bytes sent/recieved are extremely hihg:

Code:

                                               
        "addr" : "192.99.13.67:50394",             
        "services" : "00000003",                   
        "lastsend" : 1459109854,                   
        "lastrecv" : 1459109855,                   
        "bytessent" : 183272754934,                
        "bytesrecv" : 9404197537,                  
        "blocksrequested" : 2,                     
        "conntime" : 1458895868,                   
        "version" : 70002,                         
        "subver" : "/Satoshi:0.9.1.1/",            
        "inbound" : true,                          
        "startingheight" : 48642,                  
        "banscore" : 0                             
   

There is no command to disconnect this node.

Is there an option in the .conf file to ban a node. Like opposite to "addnode=" ?

What I have had to do in the past, since there is no direct ban that can be done in the config file, is manually block all in and out traffic of that specific IP address.

The node should auto ban for sending crap data, but since it is not actually sending bad data, but just asking over and over and over for data, it doesn't trigger the ban for that IP.

I shut down the node for now. I was never mining, just supporting the network... Hope the developers release a patch for this.

[SlimePuppy]

I got with 250kHps in about 20 days nil, nothing, nichts, nada. So I finally stopped my catcoin mining.

Feel free to join one of the pools - solo mining with 250k hash pretty much died years ago.  In the mean time, post a CAT address.

[krile]

Any thoughts on making the cat PoS also?

I have two cats at home, I just hate seeing this coin slowly die...

Any updates planed? My node is still off due to the log spamming...

[vampirus]

Many CATs stuck on Cryptsy, until they return or sell CAT, I do not believe something happens.
I lost 77K myself.

[SlimePuppy]

Any thoughts on making the cat PoS also?

I have two cats at home, I just hate seeing this coin slowly die...

Any updates planed? My node is still off due to the log spamming...

From the beginning, krile, this was intended to be a POW coin only.  We've (dev and community) looked at changing coin parameters at each major fork in the road and the answer each time has remained the same:  POW and 10 minute blocks.  It appears we're the last 'bitcoin in scrypt' original coin still standing.  And as the community and devs identified problems with things like KGW et al, we were able to side-step the problems other coins walked into.  Note that we are not one of the coins still struggling with profit-switch miners - that's no longer a problem for CAT.

CAT's very much alive and will remain so - just because there aren't a lot of posts here doesn't mean much - we're still on IRC 24/7, still have testnet and updates in the pipeline, and are still working on exchanges and opportunities to use CAT in the real world.  BitFUDtalk really isn't the center of the universe.

I'm still interested in your 'log spamming' - I run a seed node and have my personal wallets.  I'm only seeing normal P2P network traffic - no spamming.  Will you please paste a segment and PM me or pastebin it and link?  Thanks in advance!


It appears that Cryptsy's dead and gone.  http://www.coindesk.com/cryptsy-assets-frozen-as-florida-court-appoints-receiver/

I had CAT there as well and was trading.  At this point the best thing I can say about that mess is that I'm using it as a reminder of why the best place to keep coin is in my personal wallet.  I won't 'invest' more than I am willing to lose, I don't send coins to exchanges unless I'm going to exchange them and withdraw.  I don't keep coins on pools, I don't use on-line wallets, I don't keep coins even at Coinbase.  The wallet is our friend here...the wallet on my computer.  That's the only one I can absolutely trust.

And finally, CATs - for the members of this dev team, this project has never been a 'pump and dump' project, or a 'ponzi scheme', or any of the other scams that we've all seen for years.  That's one thing that has been different about CAT from the start.  We have been working to build a reliable coin - a coin that "just works" like it's supposed to in today's environment.  Coins have come and gone, many exchanges have come and gone, but CAT is still here and still working.  That's a good thing!

[SlimePuppy]

CATs - one of the things we hoped to do with CAT was to support animal-related charities.  The only way to make that happen today is to sell CAT for FIAT and donate.  One project we've been watching is LittleDuke's DoABitOfGood.  We've been in touch with him for quite some time and we like the work he's doing and more importantly, we like WHY he's doing the work.  That said:

The 2GiveCoin has extended an offer to the CAT community to exchange some CAT for a stake in the 2GiveCoin POS/POW charity infrastructure.  As this is an early project that may fail (though I sincerely hope it succeeds!), I can't recommend swapping any more CAT than one would be OK losing.  For more on this project, hit their project link.

I'd like to cordially invite you all to consider a "reverse-merger" into 2GIVE the new POS/POW Givecoin 2.0 crypto that is easy to mine in the wallet to compete for the 1% TXFEE block rewards!
<snip>
https://bitcointalk.org/index.php?topic=741714.0
<snip>
If you're interested, download the 2GIVE wallet and PM me your Give* address and I will create a Catcoin addr for you to send coins to -- once confirmed I'll send the same number of 2GIVE back to you.  It's just that simple!

As a way to encourage participation, I will donate ten 1000CAT amounts to CATs that want to swap for 1000 2GIVE.  Hit LittleDuke's site, create a wallet, and post an address here.  I'll send 1000 CAT to LittleDuke for each person that requests it, and we'll look forward to posts from fellow CATS when their 2Give arrives.