[ANN] Catcoin - 0.9.3.0

[SlimePuppy]

On which chain yours wallet, depend on connections to one or other chain. Which more connections that winner.
I use maxconnections=5
and
addnode=107.170.40.107 - 45643
addnode=62.210.254.171 - 45643
addnode=146.0.32.101     - 45643
addnode=98.115.147.74   - 45224
addnode=108.61.10.90    - 45224

if I add connections with 45224 my wallet switch to new blockchain, but I lost many coins.
Therefore I will support old 45643 chain.
In my opinion 45224 - wrong chain.

You will have to talk to Hozer on your lost coins then.  As he is "A single entity" that is causing that fork in the chain, against "A community of many" on the official chain.

Good luck getting your coins to work with his chain.

Blak.

Good luck indeed.

To be very accurate:  the chain 'vampirus' is mining isn't a 'fork' from Catcoin - it's a completely separate blockchain with completely different parameters than CATcoin.  It is a completely separate coin that is using our graphics, port, and name.  It is not CAT, it is run by a single entity that has proven himself to be a thief, and  is NOT in any way CAT.  Anyone mining there is not generating CAT - they're generating Hozer's 'copycat' coin.

[SlimePuppy]

wallet fully syncs:)
but still missing coins
................

not yet redeemed. any idea why?

Your link is infected.

Nothing wrong with the link.  The virus scanner is likely keying on the character string for the TxID and comparing it to its signature database.  That's happened before with coins. 

Sorry for the block explorer hang-up today - I checked it last night and it was up and running normally.  I've been traveling all day today and couldn't check the site until I returned.  It's running fine and is absolutely not infected with anything.  My Kaspersky scans are clean, and the server logs are clean.

Andy

[SlimePuppy]

seriusly this coin is broken. not getting any coins in my wallet (latest ver) and its stuck on synchronizing (15hrs behind atm bkicj 45207) very weird.

CAT's running fine.  I just opened my wallet and received 4.8 CAT from Bejjan's pool.  Prior to that, I received mined coins from GeekHash on the 16th.

If you didn't get your wallet from http://catcoins.org/ (which links to http://catcoinwallets.com/) or your source from https://github.com/CatcoinOfficial/CatcoinRelease then you are not running CATcode.

Check the block chart at http://catcoinwallets.com/ to see if blocks are flowing normally.  Any wallet will say 'behind' until the next block is found.



We fork into our stable block rate at 46331 and I for one cannot wait.

[vampirus]

OK, I switch to right chain.

[SlimePuppy]

FYI everyone - this isn't new, unfortunately.

https://bitcointalk.org/index.php?topic=411527.0

This isn't an official fork.

Someone wants to fork the coin. He's welcome to, but it doesn't have the support of the community.

This is the worst kind of FUD.

Hit the link for context.  News flash:  Hozer's been trying to 'hoze' the chain since just after launch. What we're seeing today is just the latest attempt.

CAT is strong, our community is strong, and unlike too many coins that started well after we did and died, we are still alive and well.

Andy

[SlimePuppy]

We were made aware this morning that the pools at SmarterHash have been mining CAT for at least three weeks and have not been on the coin's blockchain.  We didn't know they were mining CAT, they didn't contact us, and we do not have them on the list of known-good pools that can be found in the OP or the community sites:

http://catcoins.org/
https://www.reddit.com/r/catcoins/

If you've been mining there, you have not been mining CAT.  We advise that you stop mining there until further notice.

We are working with the folks at SmarterHash to bring them into the community.  When they're on-track, we'll add them to the pool lists.

Andy

edit... Jeff from 'smarterhash' refuses to connect to the main network and acknowledges that his pool has been mining their own fork.  Instead of fixing the problem, he's decided to shut-down his CAT mining node.  SmarterHash will not be included in our pool list.

/edit

[SlimePuppy]

All Righty CATs - we've been working on Bittrex to add CAT to their exchange.  They want to hear from the community before they accept us.  Feel free to request CAT at Bittrex here:

https://bittrex.zendesk.com/hc/en-us/articles/202583854-Submitting-a-Coin-to-Bittrex-Updated-07-20-15

We've already submitted all the info they need - source, links, threads, community, etc.  All you have to do, if you want CAT on Bittrex, is to open a support ticket and demand CAT.

We've never been de-listed - the two other exchanges we've been on from the start closed their doors and/or were hacked into bankruptcy.

If you prefer another exchange, please link it as well!

Andy

[vampirus]

Network hashrate:

old   9.1.1 (45862) 414 MH
new 9.2.0 (45262) 125 MH

[SlimePuppy]

Network hashrate:

old   9.1.1 (45862) 414 MH
new 9.2.0 (45262) 125 MH

Vampirus - there is only one CAT network.  The current block is 45268.

Any coin network's hash rate numbers are estimates based on how fast or slow previous blocks were solved.  It is impossible to know the actual network hash rate.

Block chart - shows difficulty, block time, and current block
http://catcoinwallets.com/

Block explorer
http://catcoinwallets.com:2750/chain/Catcoin

If you have the seed nodes from the OP in your catcoin.conf then you should be on the network with either client.  I maintain a seed node and build/test windows and linux wallets - I have absolutely no problem syncing with V9.1.1 or V9.2.0 on either operating system.  Note the info from the Mac wallet build - the wallet compiled, ran, connected to the CAT network, and fully synchronized within minutes.

Code:

rpcuser=username
rpcpassword=userpassword
server=1
daemon=1
testnet=0
listen=1
addnode=167.160.36.82
addnode=173.254.235.58
rpcport=7000
rpcallowip=192.168.*.*

[vampirus]

9.1.1 info http://www.coinwarz.com/cryptocurrency/coins/catcoin
9.2.0 info https://pool.hashnova.com/pools/Catcoin/CAT/

Network's hash rate - it's average for some previous period of time.

When You remove min block time in version 9.2.0 - difficulty start changed dramatically,
and  we may wait block 46331 several months.

[SlimePuppy]

9.1.1 info http://www.coinwarz.com/cryptocurrency/coins/catcoin
9.2.0 info https://pool.hashnova.com/pools/Catcoin/CAT/

Network's hash rate - it's average for some previous period of time.

When You remove min block time in version 9.2.0 - difficulty start changed dramatically,
and  we may wait block 46331 several months.

Yes - there are a number of ways to calculate a hash rate - but it is still an estimate based on the previous block difficulty and the time it took to solve that block.  Because there is no way to know who is mining the network, and because of the random nature of block generation, this is only a very crude estimate.

Yes - we knew that the difficulty would jump around.  We've been here before and it's ok.  Block generation will be slower than normal until we hit the block, but CAT's block generation has been off since launch.  The minimum block time was a kludge to help after a flaw in the algo was identified, and was only necessary when the network hash rate is very low.  The new code is a result of 18 months of work and doesn't need any cheats.

Yes, it can take more time than planned to get to 46331 but it doesn't have to.  It depends on us miners.  All of my 33MH/s are crunching CAT, and I've just bought another 15 MH/s that'll be on-line in a couple of days.  The only way we're going to get to a stable CAT is to mine to the fork.

[bejjan]

There hashrate distributed to CAT via my pool is quite high at times, as you can see per the last 120 blocks found by the pool.

https://pool.bejjan.net/pool/CAT

Version 0.9.2.0

Note: The page says it's synching but you can see that it remains on the correct blockheight, the sync indicator is at fault as it is reading from the peerlist and selects the highest startingheight, will be fixed when i find the time

[bejjan]

Code:

    {
        "addr" : "209.162.51.83:9933",
        "services" : "00000003",
        "lastsend" : 1437597339,
        "lastrecv" : 1437596616,
        "bytessent" : 349,
        "bytesrecv" : 75520,
        "blocksrequested" : 0,
        "conntime" : 1437596506,
        "version" : 70002,
        "subver" : "/Catoshi:0.9.3.2/",
        "inbound" : false,
        "startingheight" : 45868,
        "banscore" : 0
    },

Yet another lame version.

Banned via firewall.

[SlimePuppy]

Ok everyone - I did some wallet experiments today.

I backed-up my personal Windows wallet.dat and did sets of before/after tests with 9.1.1 and 9.2.0 wallets, with and without catcoin.conf and addnodes.  Keep in mind that the 9.1.1 wallet does have the 30 second minimum block time code while the 9.2.0 wallet does not (even before the fork block).

A brand new 9.1.1 wallet with NO catcoin.conf, no addnodes, and no peer.dat will not automatically join the CAT network.  It will take more than 30 minutes to sync on the copycat chain.
A brand new 9.1.1 wallet with a catcoin.conf and addnodes will not automatically join the CAT network.  It will take more than 30 minutes to sync on the copycat chain.
A brand new 9.1.1 wallet with an existing peer file will join the CAT network and will sync within seconds.

A brand new 9.2.0 wallet with NO catcoin.conf, no addnodes, and no peer.dat WILL automatically join the CAT network and will fully sync in minutes.
A brand new 9.2.0 wallet with a catcoin.conf  will also automatically join the CAT network and will fully sync in minutes.


Updating to V9.2.0 is a mandatory upgrade, CATs - it takes us to a fully-inclusive network that generates regular 8-12 minute blocks.  For the first time since launch in Dec 2013 we will have regular blocks regardless of the network hash rate after our fork at block 46331.

[Blaksmith]

Code:

    {
        "addr" : "209.162.51.83:9933",
        "services" : "00000003",
        "lastsend" : 1437597339,
        "lastrecv" : 1437596616,
        "bytessent" : 349,
        "bytesrecv" : 75520,
        "blocksrequested" : 0,
        "conntime" : 1437596506,
        "version" : 70002,
        "subver" : "/Catoshi:0.9.3.2/",
        "inbound" : false,
        "startingheight" : 45868,
        "banscore" : 0
    },

Yet another lame version.

Banned via firewall.

Here are the 4 IP addresses that I have found attaching themselves to the network that is NOT 9.1.1 or 9.2.0
107.170.40.107
115.74.173.72
204.44.65.108
209.162.51.83

Each pool owner / wallet holder, do what you wish with those IPs

For all those still running 9.1.1, PLEASE update your wallets!

Blak

[SlimePuppy]

I'll pay a 100 CAT bounty for the miner that breaks this block --> 45276.

Who's ready to join us digging?

[SlimePuppy]

Code:

    {
        "addr" : "209.162.51.83:9933",
        "services" : "00000003",
        "lastsend" : 1437597339,
        "lastrecv" : 1437596616,
        "bytessent" : 349,
        "bytesrecv" : 75520,
        "blocksrequested" : 0,
        "conntime" : 1437596506,
        "version" : 70002,
        "subver" : "/Catoshi:0.9.3.2/",
        "inbound" : false,
        "startingheight" : 45868,
        "banscore" : 0
    },

Yet another lame version.

Banned via firewall.

Here are the 4 IP addresses that I have found attaching themselves to the network that is NOT 9.1.1 or 9.2.0
107.170.40.107
115.74.173.72
204.44.65.108
209.162.51.83

Each pool owner / wallet holder, do what you wish with those IPs

For all those still running 9.1.1, PLEASE update your wallets!

Blak

In addition to those, I also block:

97.125.228.181
198.41.222.173

Both run hozer's "catoshi" clients.

[vampirus]

Let me say, why I believe that "copycat" is main chain.
My 9.1.1 wallet was online about 2 month and I mine CAT on my own server.
3 day ago I found, that we have 2 CAT chain.
You change code that affect on blockchain before block 46331, that was advertised as hardfork.
First time 9.1.1 and 9.2.0 version accept all blocks. First block, that was found before 30 sec gap
was accepted in 9.2.0 version and rejected in 9.1.1 wallet. CAT split into 2 different chains.
If Cryptsy accept version 9.2.0 I lost 7600 CAT mined in official 9.1.1 version and before advertised hardfork block.

[Blaksmith]

Let me say, why I believe that "copycat" is main chain.
My 9.1.1 wallet was online about 2 month and I mine CAT on my own server.
3 day ago I found, that we have 2 CAT chain.
You change code that affect on blockchain before block 46331, that was advertised as hardfork.
First time 9.1.1 and 9.2.0 version accept all blocks. First block, that was found before 30 sec gap
was accepted in 9.2.0 version and rejected in 9.1.1 wallet. CAT split into 2 different chains.
If Cryptsy accept version 9.2.0 I lost 7600 CAT mined in official 9.1.1 version and before advertised hardfork block.

Well, the "30 second minimum" has been a BIG issue since we put it up, just to fix the other cludge.  It probably should have been kept in until the actual fork block, but I will admit, there was a slight oversight in the code, and it was removed before the hard fork block coming up.  That oversight HAS caused this last fork.  But again, with it removed, we are NOT limited to being denied legit blocks, just because they are "before 30 seconds".  Or as Hozer's wants, "3 MINUTES".  

I do take FULL responsibility for approving the code to completely remove the 30 second minimum code for 0.9.2.0.  So, again, we leave it up to the community ... do you want to be rejected "VALID" blocks because they are not at least 3 minutes past the last block, or would you like to be credited the legitimate block you have earned, even if it is way less than the 3 MINUTES after the last block was found that Hozer's coin wants to enforce.


Edit:

If Cryptsy accept version 9.2.0 I lost 7600 CAT mined in official 9.1.1 version and before advertised hardfork block.

Totally impossible to mine 152 blocks within the last 24 - 48  hour period of time, BY YOURSELF, unless you have 10GH worth of Scrypt to push towards it.  The fork did not happen until after 07-20-2015.

[SlimePuppy]

If Cryptsy accept version 9.2.0 I lost 7600 CAT mined in official 9.1.1 version and before advertised hardfork block.

Let's take this apart.

If you mined the CAT blockchain with any official wallet prior to the release of V9.2.0, then you have CAT.  

If you mined any fork (including hozer's intentional copycat fork) prior to the release of V9.2.0, then you did not mine CAT.  This is not a result of a code error or dev team decision - this is a basic function of the entire cryptcoin system - soft forks happen regularly and the line with more proof of work is the 'real' chain while the rest are orphaned.

If you continued to use V9.1.1 after the release of V9.2.0 - a MANDATORY upgrade - then you mined CAT.

If you continued to use V9.1.1 after the release of V9.2.0 on Hozer's copycat fork, then you didn't mine CAT.

If you have any questions about whether you mined CAT or not, the truth is in the blockchain and the explorer:
http://catcoinwallets.com:2750/chain/Catcoin

You can tell that you have CAT if you can find your transactions on the explorer and it shows a full history from generation.
If you mined on Hozer's fork, then you will not see coin generation on the CAT network.  You will have to go to him for compensation.  Since you intentionally used addnodes to hozer's network, you intentionally abandoned any opportunity to mine CAT.  Maybe Hozer will start a copycat-CAT exchange service for the folks he scammed.

On which chain yours wallet, depend on connections to one or other chain. Which more connections that winner.
I use maxconnections=5
and
addnode=107.170.40.107 - 45643
addnode=62.210.254.171 - 45643
addnode=146.0.32.101     - 45643
addnode=98.115.147.74   - 45224
addnode=108.61.10.90    - 45224

if I add connections with 45224 my wallet switch to new blockchain, but I lost many coins.
Therefore I will support old 45643 chain.
In my opinion 45224 - wrong chain.