I mined them on my home computer, and naturally you can't find them on yours not "copycat" blockchain.
Then we're done here. There is no way you mined 115 CAT blocks on your home computer from 10-13 July.
Topic: [ANN] Catcoin - 0.9.3.0 - page 24. (Read 57711 times)
I mined them on my home computer, and naturally you can't find them on yours not "copycat" blockchain.
9psk417ZEveQhFYLR13YaCdSV2NWr8oCSi
115 blocks from 10 to 13 July.
All other was before split and send to Cryptsy, or 2 days ago when I already know about 2 blockchain.
There are no transactions on that address between 10 and 13 July.115 blocks from 10 to 13 July.
All other was before split and send to Cryptsy, or 2 days ago when I already know about 2 blockchain.
Please provide information on the pool you were mining on and any transaction IDs for the payouts.
9psk417ZEveQhFYLR13YaCdSV2NWr8oCSi
115 blocks from 10 to 13 July.
All other was before split and send to Cryptsy, or 2 days ago when I already know about 2 blockchain.
115 blocks from 10 to 13 July.
All other was before split and send to Cryptsy, or 2 days ago when I already know about 2 blockchain.
I lost block mined in version 9.1.1
Please provide txid and addresses for any blocks or coins you believe you have lost.
I lost block mined in version 9.1.1
I do not knew about version 9.2.0 a weak ago and I do not know about 'hozer'.
Before advertised hardfork block, new and old version must be work with same parameters.
But you change code that accept timewrapped 44227 block and create new blockchain,
different from main 9.1.1 chain before 46331 block. It is yours fault.
I do not knew about version 9.2.0 a weak ago and I do not know about 'hozer'.
Before advertised hardfork block, new and old version must be work with same parameters.
But you change code that accept timewrapped 44227 block and create new blockchain,
different from main 9.1.1 chain before 46331 block. It is yours fault.
50 CAT Bounty for CAT Pool Information
Are you mining a pool not on the community pool list? Please tell us about the pool and include a CAT address - we want to include all pools!
Thanks!
Are you mining a pool not on the community pool list? Please tell us about the pool and include a CAT address - we want to include all pools!
Thanks!
Hi,
Here you have a working addnode for 0.9.2 from hashnova. Even me I have started banning wrong clients through firewall.
addnode=node.hashnova.com:9933
Cheers,
David
Great to hear, David! Thanks very much! Here you have a working addnode for 0.9.2 from hashnova. Even me I have started banning wrong clients through firewall.
addnode=node.hashnova.com:9933
Cheers,
David
I mean 9.2.0
You try use any come-off, but not accept yours fault.
Dude - the point you keep missing is that we are INTENTIONALLY forking this code to a new difficulty algo to fix the network once and for all. We KNOW we're forking. We KNOW we removed the 30 second minimum kludge. We KNOW we removed at least two other code weaknesses. It's not a 'bug' or a 'fault' or an 'error' - we expected the soft-fork as well! And if you read up a few posts (and the OP, and posts in the previous threads) then you know full well that we've been working on this update for the past year. The bug is in the current PID code which was deployed with 9.1.1 and that's the bug that's being exploited today to drive our difficulty high. That STOPS at block 46331.You try use any come-off, but not accept yours fault.
If you are using V9.2.0 then you are on the correct code, on the real CAT network, and all of your coins are safe.
If you still think you lost coins because of the soft fork from a few days ago, then please provide mining and/or transaction info and we'll dig into it. If you intentionally mined hozer's attack fork, then you're on your own. But if you unintentionally fell off the CAT network as a result of the soft fork before upgrading to V9.2.0, then we'll work with you.
I mean 9.2.0
You try use any come-off, but not accept yours fault.
You try use any come-off, but not accept yours fault.
I repeat second time: I am not connecting to the fork. This addnode was added for testing only 3 day ago.
By the way blockchain split after block 44226 - 2015-06-30
I used 9.1.1 version and no addnode in config
since 3 day ago I use 9.2.2 version (and 9.1.1 for testing)
I sometimes check block count on coinwarz.com
Coinwarz is not yet updated and therefore the info you find there is NOT CORRECT.
The current wallet for the CAT network is Version "Satoshi 0.9.2.0" and it is linked in the OP.
Yes, we are aware that Hozer/catcoiner/tmagik/TechnoMagik has fake code and fake nodes. He has a 'catoshi 9.3.2', a 'catcoin 0.9.2.4' client in addition to the 9.2.2 you are using. You are using fake code that is not CAT, you are working on a blockchain that is not CAT and thus you should take your concerns to one of Hozer's threads or IRC channels.
I repeat second time: I am not connecting to the fork. This addnode was added for testing only 3 day ago.
By the way blockchain split after block 44226 - 2015-06-30
I used 9.1.1 version and no addnode in config
since 3 day ago I use 9.2.0 version (and 9.1.1 for testing)
I sometimes check block count on coinwarz.com
And 9.1.1 version with empty database, never connect to 9.2.0 chain, it stuck on block 44226
I repeat second time: I am not connecting to the fork. This addnode was added for testing only 3 day ago.
By the way blockchain split after block 44226 - 2015-06-30
I mined lost blocks 10-13 July in version 9.1.1 without adding any addnode.
Please provide details of the blocks you mined from 10-13 July.I add 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
only in version 9.2.0 20 July for experiment.
I can't choose on which chain my wallet.
Here is where you are very, very wrong. When you intentionally connect to nodes that are NOT on the CAT network then you are NOT mining CAT and you ARE choosing the chain for your wallet.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
only in version 9.2.0 20 July for experiment.
I can't choose on which chain my wallet.
vampirus - this is at least the third time you are being told this:
YOU ARE INTENTIONALLY CONNECTING TO A FORK THAT IS NOT ON THE CAT NETWORK. NOT A SINGLE ONE OF YOUR 'ADDNODE's IS ON THE CAT NETWORK.
What you are doing is exactly like mining UNO and complaining that you're not seeing DOGE transactions in your UNO wallet.
If you want to work with CAT, then download the proper wallet and it will connect to the CAT network. If you don't, then I hope you find a community that caters to your desires.
I repeat second time: I am not connecting to the fork. This addnode was added for testing only 3 day ago.
By the way blockchain split after block 44226 - 2015-06-30
Block 44227 was time wrapped and rejected in real 9.1.1 blockchain, but accepted in 9.2.0 bugged version.
I mined lost blocks 10-13 July in version 9.1.1 without adding any addnode.
Please provide details of the blocks you mined from 10-13 July.I add 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
only in version 9.2.0 20 July for experiment.
I can't choose on which chain my wallet.
Here is where you are very, very wrong. When you intentionally connect to nodes that are NOT on the CAT network then you are NOT mining CAT and you ARE choosing the chain for your wallet.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
only in version 9.2.0 20 July for experiment.
I can't choose on which chain my wallet.
vampirus - this is at least the third time you are being told this:
YOU ARE INTENTIONALLY CONNECTING TO A FORK THAT IS NOT ON THE CAT NETWORK. NOT A SINGLE ONE OF YOUR 'ADDNODE's IS ON THE CAT NETWORK.
What you are doing is exactly like mining UNO and complaining that you're not seeing DOGE transactions in your UNO wallet.
If you want to work with CAT, then download the proper wallet and it will connect to the CAT network. If you don't, then I hope you find a community that caters to your desires.
I mined lost blocks 10-13 July in version 9.1.1 without adding any addnode.
I add 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
only in version 9.2.0 20 July for experiment.
I can't choose on which chain my wallet.
Client connect automatically to 8 nodes with minimum ping.
I add 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
only in version 9.2.0 20 July for experiment.
I can't choose on which chain my wallet.
Client connect automatically to 8 nodes with minimum ping.
I'll pay a 100 CAT bounty for the miner that breaks this block --> 45276.
Who's ready to join us digging?
I'm digging, but I don't need the bounty ;-)
Hi,
Here you have a working addnode for 0.9.2 from hashnova. Even me I have started banning wrong clients through firewall.
addnode=node.hashnova.com:9933
Cheers,
David
Here you have a working addnode for 0.9.2 from hashnova. Even me I have started banning wrong clients through firewall.
addnode=node.hashnova.com:9933
Cheers,
David
I'll pay a 100 CAT bounty for the miner that breaks this block --> 45276.
Who's ready to join us digging?
I do take FULL responsibility for approving the code to completely remove the 30 second minimum code for 0.9.2.0.
I take full responsibility for removing all of Hozer's code from CAT - including the 30 second minimum. I also worked to re-align (update) our codebase with current LTC - which is the source for the original CAT code when launched in 2013 by KR105.The community made clear that they did NOT want block restrictions. The current code does not need artificial restrictions. The post fork code certainly doesn't need any such kludges.
CAT has been forking since launch - most either unintentional or as a result of the environment evolving faster than we have - and that's been happening both with and without artificial time limits. For these reasons, the Dev team worked to bring the community a CAT that finally works. Mine to the fork and watch CAT run!
Jump to: