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

[Blaksmith]

The wallet's up.  Thanks again for the heads-up folks.  Andy

Windows wallet:
http://catcoinwallets.com/win/Catcoin_0.9.2.0.zip
SHA256: A3FAC5C54F2E22B2918823140A4D121BA25160DFB3E2AEDB073A14E30A5204B9

seems to be stuck 6 hours behind?
i'm up around 44193..

Current block, at the time of this post, is 44177, showing 4 hours behind, because the last block was almost 5 hours ago.

The official explorer reflects that too: http://catcoinwallets.com:2750/chain/Catcoin

[1715189838]

1715189838

[1715189838]

1715189838

[1715189838]

1715189838

[1715189838]

1715189838

[SlimePuppy]

The wallet's up.  Thanks again for the heads-up folks.  Andy

Windows wallet:
http://catcoinwallets.com/win/Catcoin_0.9.2.0.zip
SHA256: A3FAC5C54F2E22B2918823140A4D121BA25160DFB3E2AEDB073A14E30A5204B9

seems to be stuck 6 hours behind?
i'm up around 44193..

The good chain is 5 hours back right now and on block 44177.  There's a catcoin.conf in the Windows distro package - add those two seed nodes to your existing catcoin.conf (delete any others - especially if any start with 170.x.x.x).

These are the network seed nodes.  They're in the code as well - you shouldn't have to add them.  But do clean any nodes out of appdata/roaming/catcoin/catcoin.conf that aren't these:

Code:

addnode=167.160.36.82
addnode=173.254.235.58

Andy

[barrysty1e]

ouch; have just had my linux wallet running the whole time.. oh well

[SlimePuppy]

Well, it didn't take our resident hacker long to start messing with us.  IP 107.170.40.107 is a former network seed node run by hozer.  Way to stay true to your stripes...

Code:

{
"addr" : "97.125.228.181:40528",
"services" : "00000003",
"lastsend" : 1435436221,
"lastrecv" : 1435436221,
"bytessent" : 140718,
"bytesrecv" : 4326,
"blocksrequested" : 0,
"conntime" : 1435434686,
"version" : 70002,
"subver" : "/Catoshi:0.9.3.2/",
"inbound" : true,
"startingheight" : 44659,
"banscore" : 0
},
{
"addr" : "209.162.51.83:9933",
"services" : "00000003",
"lastsend" : 1435436221,
"lastrecv" : 1435436080,
"bytessent" : 343,
"bytesrecv" : 75292,
"blocksrequested" : 0,
"conntime" : 1435435025,
"version" : 70002,
"subver" : "/Catoshi:0.9.3.2/",
"inbound" : false,
"startingheight" : 44177,
"banscore" : 0
},

[SlimePuppy]

Ok...  Now that we're rolling towards block 46331, here's what to expect once we get to the new code.

First, a reminder:  Sending to/from Cryptsy should be normal up to our fork.  Hold off on transfers at the fork until we post that things are working - let me risk my CATs before you risk yours.

As everyone knows (painfully knows...), the PID algo that seemed perfect on testnet started to gallop once we forked into it on mainnet.  We've been in this fast/slow block mode for far too long while we dealt with attacks and forks and searched for a difficulty adjust algo that worked better for our relatively small coin in this 'modern' environment.

We worked on tweaks and filters for PID, single algos, and combinations - including DGW2 and 3 and 1- and 3-block Digishield.  The winner by far was the dual random Digishield/PID that's in V9.2.0.  All of the minimum block time kludges have been removed (as well as all of the other attempts to fix things since V8).

This combination moves around enough to show that it's alive, but will never drop the difficulty too low the way our current code does.  Yes, we've attracted coin switch miners in the past when our difficulty droped low enough (read:  too low) and that's given blocks away and then kicked our diff up too high.  As we've said all along, the goal has been to stabilize the difficulty while resisting hoppers and common exploits as much as possible.  Hopefully this is what'll happen in mid-July.

This code runs a 9-12 minute block time during smooth periods, resists hash 'attacks' very well while properly responding to new miners on the network.  It also does the best job of ramping the difficulty back down if an attacker stays on us for many hours then pulls their miners.  Fingers crossed CATs.  If all goes well, this'll finally be the stability we've all wanted since the coin launched at Christmas, 2013.

Andy


http://catcoinwallets.com/images/testnet/24b.jpg


http://catcoinwallets.com/images/testnet/34b.jpg




Ada the mighty huntress is on fork watch...

[SlimePuppy]

ouch; have just had my linux wallet running the whole time.. oh well

James - How's your sync looking now?

[barrysty1e]

has been good for a while now, just lamenting the loss of 900CAT that i accrued
both windows wallet and headless under debian work fine, block 44191 at diff 93

[SlimePuppy]

has been good for a while now, just lamenting the loss of 900CAT that i accrued
both windows wallet and headless under debian work fine, block 44191 at diff 93

PM sent

[hozer]

has been good for a while now, just lamenting the loss of 900CAT that i accrued
both windows wallet and headless under debian work fine, block 44191 at diff 93

That's just slimepuppy stealin your catz with blockchain reorgs.

To be serious, I have no idea who's running alternative code, and the nature of the protocol is it's very hard to tell if a node is providing a fake 'version' string. At this point it would probably be profitable to instamine both sides of a fork if there's no other major consistent hashpower.

Hell, I even had my miner turned off because it seemed like everyone else had given up. Maybe I should turn it back on, this might be profitable if the 'official' hardfork chain locks up.

[Blaksmith]

has been good for a while now, just lamenting the loss of 900CAT that i accrued
both windows wallet and headless under debian work fine, block 44191 at diff 93

That's just slimepuppy stealin your catz with blockchain reorgs.

To be serious, I have no idea who's running alternative code, and the nature of the protocol is it's very hard to tell if a node is providing a fake 'version' string. At this point it would probably be profitable to instamine both sides of a fork if there's no other major consistent hashpower.

Hell, I even had my miner turned off because it seemed like everyone else had given up. Maybe I should turn it back on, this might be profitable if the 'official' hardfork chain locks up.

Again, take your FUD elsewhere.... You PROVED that YOUR code is giving some of the version numbers (with what you showed of the difference between official and what you run).  And as well as you have run in the past your "Catoshi" code.  You HAVE been reported.  I personally don't put people on ignore, just so I can see what BS they keep spewing, but you are very close to going on it!.

[SlimePuppy]

has been good for a while now, just lamenting the loss of 900CAT that i accrued
both windows wallet and headless under debian work fine, block 44191 at diff 93

That's just slimepuppy stealin your catz with blockchain reorgs.

To be serious, I have no idea who's running alternative code, and the nature of the protocol is it's very hard to tell if a node is providing a fake 'version' string. At this point it would probably be profitable to instamine both sides of a fork if there's no other major consistent hashpower.

Hell, I even had my miner turned off because it seemed like everyone else had given up. Maybe I should turn it back on, this might be profitable if the 'official' hardfork chain locks up.

You have no idea?  I guess you no longer control your VPN node running the bogus 9.2.1 code?  Or the trash you linked up a few posts?

Since it's your BS that's caused the hozer-fork, how about you return etblvu1's donated coins to him and replace james' cats out of the CAT insurance fund that you stole?

Seriously - you should have listened to the cypherpunks that advised you to run official code, but maybe you missed that when you were FUDing on Bitcoin and complaining about John Deere, hmmm?
https://cpunks.org/pipermail/cypherpunks/2015-June/007896.html

[SlimePuppy]

Ok CATs.  As some of you know, last time we had a forkfest, folks in the community (including me), donated CATs out of their pockets to fund an insurance program to take care of the community in the event of a network meltdown.  As most of you also know, Hozer stole it when he was kicked off the dev team for running hacked clients on mainnet and on a formerly-official seed node (107.170.40.107).

The dev team has been carrying this coin during her slumber while we've worked on this new algo.  We've mined with our own machines and/or leased rigs to 51% the network back together last time hozer caused more than 14 forks.  We're mining it now.  I have all of my scrypt miners on CAT mainnet now that testnet work is complete - I own a pair of Black Widows and a pair of Furys for a solid 30MH/s pool-side.

Since Troy/Hozer/tmagik/catcoiner/Troy Benjegerdes/technomagik won't do the right thing after all this time, I will.

- Would everyone that donated to the CAT insurance fund please PM, email, or get me on IRC in #catcoin-dev and provide details of how many CAT they donated?  It's payback time.  Eric - I expect to hear from you as well.

- Everyone else - please make sure you are running official code and are on the network before transferring funds.  Official info is here:

http://catcoins.org/
http://catcoinwallets.com/
https://github.com/CatcoinOfficial/CatcoinRelease
http://www.reddit.com/r/catcoins/
https://www.facebook.com/CatcoinOfficial
https://twitter.com/CatcoinOfficial


- If you've lost CATs recently, please PM, email, or get to me on IRC and give me details.  If we can fix it, we will.

I'm a disabled US military veteran on a fixed income and I'm a CAT - we don't leave CATs behind.

Andy

[hozer]

Ok CATs.  As some of you know, last time we had a forkfest, folks in the community (including me), donated CATs out of their pockets to fund an insurance program to take care of the community in the event of a network meltdown.  As most of you also know, Hozer stole it when he was kicked off the dev team for running hacked clients on mainnet and on a formerly-official seed node (107.170.40.107).

The dev team has been carrying this coin during her slumber while we've worked on this new algo.  We've mined with our own machines and/or leased rigs to 51% the network back together last time hozer caused more than 14 forks.  We're mining it now.  I have all of my scrypt miners on CAT mainnet now that testnet work is complete - I own a pair of Black Widows and a pair of Furys for a solid 30MH/s pool-side.

Since Troy/Hozer/tmagik/catcoiner/Troy Benjegerdes/technomagik won't do the right thing after all this time, I will.

- Would everyone that donated to the CAT insurance fund please PM, email, or get me on IRC in #catcoin-dev and provide details of how many CAT they donated?  It's payback time.  Eric - I expect to hear from you as well.

- Everyone else - please make sure you are running official code and are on the network before transferring funds.  Official info is here:

http://catcoins.org/
http://catcoinwallets.com/
https://github.com/CatcoinOfficial/CatcoinRelease
http://www.reddit.com/r/catcoins/
https://www.facebook.com/CatcoinOfficial
https://twitter.com/CatcoinOfficial


- If you've lost CATs recently, please PM, email, or get to me on IRC and give me details.  If we can fix it, we will.

I'm a disabled US military veteran on a fixed income and I'm a CAT - we don't leave CATs behind.

Andy

I will be quite happy to refund anyone who contributed to the insurance fund. My recollection is Eric is quite happy to have me continue to hold the funds, and definitely does NOT approve of giving them to you.

I will also be happy to discuss with an authorized representative of Cryptsy how to arrange management of a transparent refund/insurance fund if they have unhappy customers. This will be contingent on a more detailed code audit to ensure that whatever code they decide to run does not have any substantial exploitable bugs. This includes bugs that allow miner timestamp fiddling to control the difficulty.

Please post any follow-up discussion to https://www.reddit.com/r/catcoins/comments/3bg928/controversial_catcoin_fork/ as this forum has proven, yet again, to be unusable for productive work.

Let me re-iterate one thing. I have done a brief code audit, and the approach of switching algorithms based on the timestamp MAY BE EXPLOITABLE, and not just by pools, but possibly by single miners. If this is what end-users (and not pool operators, or those with mining interests) actually want, then please make your voice heard on the reddit forum, or just upvote/downvote any comments there.

[hozer]

There you go... ADVERTISING YOUR NON OFFICIAL CODE...

Take your crap elsewhere!

If you look at the dates on that, you'll see that's been posted for around 9 months, which makes it a little silly when you claim I've not disclosed it.

If you have to rely on some official stamp of approval for a cryptocoin code, how is this any better than the federal reserve? Isn't this supposed to be determined by the algorithms and the mathematics? Have you tried modifying a miner so it produces only 44 second timestamps to see what happens on testnet?

[Blaksmith]

There you go... ADVERTISING YOUR NON OFFICIAL CODE...

Take your crap elsewhere!

If you look at the dates on that, you'll see that's been posted for around 9 months, which makes it a little silly when you claim I've not disclosed it.

If you have to rely on some official stamp of approval for a cryptocoin code, how is this any better than the federal reserve? Isn't this supposed to be determined by the algorithms and the mathematics? Have you tried modifying a miner so it produces only 44 second timestamps to see what happens on testnet?

It is the COMMUNITY's stamp of approval that has spoken up to update the OFFICIAL code to be used to help fix the coin.  That is the complete opposite of how you say that the federal reserve runs.  How is ONE PERSON's code running AGAINST the OFFICIAL code LESS like the federal reserve you want to try and compare it to?  It seems like the ONE PERSON that keeps this BS going, is the one that wants to act like THE dictator. 

And BTW, the timestamp is when the first catcoind receives it, NOT what a miner sends.  Read the code more.

Again I state... Take your shit elsewhere....

[SlimePuppy]

I will be quite happy to refund anyone who contributed to the insurance fund. My recollection is Eric is quite happy to have me continue to hold the funds, and definitely does NOT approve of giving them to you.

Eric requested the return of his contribution on January 6, 2015.  Please post the transaction ID for his refund.  Thanks in advance.

https://bitcointalk.org/index.php?topic=441402.msg10061356#msg10061356

[hozer]

And BTW, the timestamp is when the first catcoind receives it, NOT what a miner sends.  Read the code more.

I think if you do not understand https://en.bitcoin.it/wiki/BIP_0022 and https://en.bitcoin.it/wiki/BIP_0023 and why the 'time' field is mutable by the miner, you should probably not be writing code that depends on the timestamp.

I appreciate the work you did writing the PID code, however it seems it would be better for catcoin if the community ignored the CatcoinOfficial github from now on. We will also need volunteers to implement the https://gitian.org/ build process so there is more than one person building binaries. This is standard practice for Bitcoin, and if you are running a binary without cross-checking it from multiple independent sources, I would suggest this may be a bad idea.

[Blaksmith]

Thanks for being #1 of my ignore list... bye bye ... Troy / Hozer / whateverthefuckyouwanttocallyourself.

For the rest of the community, I do NOT take ignores lightly.  This ignore of someone that wants to continue trying to push people away from the coin, is well deserverd, and the stress levels are not needed either..  Please PM me if you think I should un-ingore Hozer.

And since I know you can still see this Hozer, how about that transaction number where you were to give Eric his Catcoin back?

[hozer]

We are not the only ones having arguments over consensus.

http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/008775.html

If there's anyone that would like to mediate a better solution than what we have going on now, please comment at https://www.reddit.com/r/catcoins/comments/3bg928/controversial_catcoin_fork/ with your ideas.

I also would like to remind everyone that it's easier to get a consensus if we give everyone the benefit of the doubt and assume we all want a globally distributed consensus system based on Cats. I've gotten pissed off and said shit that does no good questioning other people's motives. While it's great drama, it doesn't really address the problem.

[SlimePuppy]

We are not the only ones having arguments over consensus.

<snip>

If there's anyone that would like to mediate a better solution than what we have going on now, please comment at <snip> with your ideas.

I also would like to remind everyone that it's easier to get a consensus if we give everyone the benefit of the doubt and assume we all want a globally distributed consensus system based on Cats. I've gotten pissed off and said shit that does no good questioning other people's motives. While it's great drama, it doesn't really address the problem.

Troy - while you're welcome to your opinion, when it comes to 'consensus' here you've been soundly overruled by the community.  Some messages can be found up a few pages - and none of them are from me, so you cannot even make this personal.

I really don't know why you feel the need to sling manure here.  The BIPs you dredged up are very old news and have been propagating through the coin system for years.  The politics of other coins have zero to do with CAT.  We are, however, working and collaborating with members of a number of other coin projects - helping those we can and learning from those that have things to share.  That includes dev team members from BTC, LTC, FTC, and other projects.  Finally, there is NOTHING controversial about progress on CAT outside your mind.  Our number one problem from the beginning has been finding a way to manage difficulty moves in this modern coin environment and in harmony with well-respected triage practices we've been putting most of our effort on existential threats.  We've put those things that are real threats to the longevity of CAT high on the list and have focused on those.

Finally, Troy - as has been made very, very clear from the very beginning of this coin project - clear from well before I joined the dev team - we are not here to create a 'global consensus system' based on cats - we are here to create and grow an internet payment system called CATCoin and hopefully use it as a tool to improve the lives of flesh-and-blood cats and other animals.  You clearly missed that when we were working on the foundation - we wanted to help cats and you only wanted to help yourself.  There's our disconnect.  And that is a disconnect that is not bridgeable or subject to compromise.

Stir your fertilizer anywhere you care to - but not here.  This community has made clear that you do not speak for them.  This dev team has also made clear that you do not speak for us.  Good luck with your reddit thread and your soybeans.

As for me, I had my fill of terrorists when I was in uniform - I don't need any in retirement.  Welcome to solitary confinement on the ignore list.

Andy