Topic: [ANN] Catcoin - 0.9.1.1 - Old thread. Locked. Please use 0.9.2 thread. - page 10. (Read 131061 times)

Yes, please speak up. If you like what Slimepuppy is doing, please say so publicly, or at least message me on irc.

The only thing I've heard from the community is the code sucks, and one of the donors to the insurance fund objects to the way you are trying to take over the community with no public evidence you have community support.

Geekhash is back up after today's maintenance, and the block time charts are back as well.

Andy

Your seed node was removed from the coinbase three months ago.  The code running on testnet has ALL of your "contributions" removed.  As has been our process from the start, release code will be pushed to CatcoinRelease when it's vetted and ready for release and not a second before.

Nobody but you is crying 'dictator' Troy.  I'm fulfilling my duties as assigned by the dev team and as outlined in the OP - I'm communicating with the community.  I shall continue to do that until such time as Maverick or the rest of the dev team changes that arrangement.

No.  You took on the insurance fund while you were an active part of the CAT dev team.  That is not "hozer's retirement fund" - that safety net was put in place to help miners and pool operators during our network trouble of last year.  You lost access to any dev projects when you so severely violated the ethics of the team and project that we fired you.

What you're saying when you continue to recommend people run your private code is that it's OK to deviate from accepted code and that it's ethical to take-over a coin network for one's own purposes.  Bzzzt - thanks for playing.

That's false as there is a working block explorer.  We're working to gain control of the domain name, and are also building a replacement explorer on a new server.
https://bitcointalksearch.org/topic/m.9980153
https://bitcointalksearch.org/topic/m.9987687

First, Troy, do you know what it means to have been FIRED?  What it means to most normal people is that you no longer have any say, and do not get to make demands.

For the record, and for the community, the domains and sites I have registered and maintain are common knowledge - and I remind everyone that should I ever leave this project that the domains and servers will be handed over to the dev team at that time.  I consider those registered domains and sites to be COMMUNITY PROPERTY for the benefit of CAT.

I maintain the primary seed node server, the catcoinwallets.com domain name and wallet web server, and the seed node DNS records. Blaksmith maintains the 2nd seed node server, the testnet, and his pool.  I have never left a domain or server to expire and will not.  I've just leased a 2nd server from CrownCloud and will be adding a seed node and wallet repository there as well.

catchain.info is not available to be registered until it's been dead for at least 30 days.

Hozer - let me make this very, very clear to you and to the rest of this community:  I'm a retired intelligence analyst.  I know more than I care to know about terrorists and insider threats.  You have chosen to be both during your association with CAT.  (Frankly, you started working against the coin when she was less than a month old.)  An association, I might add, that was deemed necessary before I became part of the dev team because the team was desperate for a programmer.  Because of your behavior, most folks involved in the project didn't want you to be part of it.  We're not desperate any longer.  You've shown your true colors.  No more lies.  You've been fired.  You are free to leave.

Community - if you still care about this project, speak up.  Not just in the form of the amazing PMs I've received (thank you!) but here on the forum.  Thanks in advance.

Andy

Really?  I was not aware that you were even remotely involved in this fund.  I am aware that various members of the community donated coin to the fund, however.  Care to share donation info with us?

Folks, the Geekhash front-end web page and the block time chart posted at catstat.info and catcoinwallets.com is temporarily down while Blaksmith does pool maintenance and upgrades.

In addition to his fun, a fallen tree knocked out his internet access yesterday and it's shaky today.

The pool back-end is fine and mining work is being served and tallied as normal.

I'll edit this when the pool and charts are back.

Andy

Same old ego, same old 'me, me me' attitude.  

Hozer - you couldn't find enough people to fill the 'catcoin foundation' board because not enough people trust you.  Those such as me that DID get involved walked away when it was clear that you didn't care about the cat community, but rather were only looking for a way to fill your bank account at our expense.  Your terrorism with the network was the last straw.

The code will be released when it's ready.  If that doesn't give you what you want, when you want it, like a six year old, then don't let the door hit you on the way out.

Request 2:  Advise us when your seed node is off line and when you've forwarded the cat insurance fund proceeds to Maverick.

I request that the contribution I made to the insurance fund be returned to me, because I understood the fund was being administered by Hozer, and the agreement was that any funds left over after paying out funds per the specific formula and procedure laid out by Hozer, would be returned back to me. Now that this arrangement has been terminated, any funds not already paid out to legitimate beneficiaries of the funds from out of what I contributed, are due back to me. I object to the idea funds I put into trust for a specific purpose becoming commandeered to be used for purposes I may find objectionable.

Thank you,

Etblvu1

Block explorer link is fixed on http://catstat.info

The url will probably change at some point once I get around to reading Apache proxy docs.

I've got my A2 (30mhash) pointed at http://catstat.info:9927/static/graphs.html?Day until the litecoin difficulty drops in a day or two. Now please hurry up and fix the code so I can justify leaving it there longer.

the code is still there, and you know perfectly well how to make the seed node irrelevant with a new wallet, so solve both problems at the same time by removing the minimum time code and releasing a new wallet. I'll know you did it because the catcoind on the node I'm running will fork off on a chain by itself when it sees a block less than 30 seconds, and there will be no new connections to it, and then I can shut it down.

This is not up to you to be the dictator of catcoin. You can post code, and see if the hashrate follows your code. The reason I have the insurance fund is because I posted code, and people ran it, and pools mined with it. If you want the insurance fund, you have to prove it with cryptographic (aka blockchain) evidence that the code you released has sufficient long-term hash-power behind it to be a viable cryptocurrency.

As it is now you can't even easily prove it because we don't even have a working block explorer.

Or maybe how about this, I'll send the remaining 10,165 cat from the insurance pool to whomever gets a block explorer working and sends me a plan on how they are going to keep it running for the next 5 years. Convince me you know what you're doing and that you have a domain registered for more than a year, or a plan for paying it on time. Right now the only person I believe has any capacity to do that is Blaksmith.

And if I get the block explorer running first I get to keep the CAT. (BTW, I'll pay reasonable BTC or cash for catchain.info if anyone knows how to re-register it before it fully expires)

New miners in the house - Nice JOB everyone! 

Your code has already been removed, and the community has already been informed why we accepted your kludge and why it is no longer in the codebase.

https://bitcointalksearch.org/topic/m.9251852

https://bitcointalksearch.org/topic/m.9219553

Please advise when your seed node is off-line and when you have forwarded the CATcoin insurance fund to Maverick.  Thanks in advance.

We've got this.

please remove the 30 second minimum block time code and hardfork if you are not going to mention it in the marketing, and update the README.md on github as well. The material you have now is quite misleading.

We added that because we were in a hurry to get something working, and all of you approved of it, and kept running it for the last half a year. If you don't like it now, then get rid of it, because as it is, it's way too short. So my opinion is it would be nice if 'the dev team' could make a decision. Hardfork and go back to no minimum block time, or soft-fork upgrade to a longer minimum block time. 3-5 minutes is probably reasonable without re-tuning the PID.

I don't really care which, but pick something and get on with it, maybe you'll learn something.

This is the current status of the project.  Please bring necessary additions/deletions. We'll update the OP once the review's complete.  Thanks in advance,   Andy
---------------------------------------




Information
PoW algorithm: Scrypt
Current Code Version: 0.9.1.1
Premine: ABSOLUTELY ZERO!
Block reward: 50 CAT
Block time: 10 minutes
Retarget: 1 Block, Using a custom PID algorithm designed by Blaksmith.
Starting difficulty: 108
Max supply: 21 million
Reward halving interval: 210,000 blocks
Source code: https://github.com/CatcoinOfficial/CatcoinRelease

Client
Windows Standalone Wallet: http://www.catcoinwallets.com/win/catcoin090101.exe
SHA256 hash: 7F26E6E2D08DA50DCAFBB384C2F2500FA0F3B8440EF202CDEFBD1255DB3A92E4

Windows .zip file: http://www.catcoinwallets.com/win/catcoin090101.zip
SHA256 hash: 7ABF4E133215C5857E312180420A274CFE914AF67DC57A191D2D3BE8BBADAB5D

Mac OSX Mavericks .DMG file : http://www.catcoinwallets.com/mac/Catcoin-Qt.dmg
SHA256: 4DA8F22B9BE24A3F5FC8CB8F179335EE9343BDCD291B045362453118B8D74880



Pools
Geekhash Pool 0% fee
P2Pool Nodes


Block explorer
http://altexplorer.info/chains/CAT/block_crawler.php
Exchange
Coined Up: https://coinedup.com/OrderBook?market=CAT&base=BTC
Cryptsy: https://www.cryptsy.com/markets/view/136

The Dev Team!

We'd like to take this opportunity to introduce our dev team (IRC usernames are used here, but are mostly the same as the Bitcointalk usernames):

KR105 - Creator and Honorary Dev of Catcoin
Kevin McCurdy (aka Maverickthenoob): Face of the dev team, Facebook page admin, code tester and general Catcoin supporter.
Mack25 - Developer of the .org website and also developer of the CatFlip website
Raistlinthewiz - Developer and GitHub source contributor with commit access.
Sir_Knee_Grow - Catcoin subreddit mod/creator and owner or the ##catcoin IRC channel
Blaksmith: Professional programmer, pool operator, testnet, IRC mod
ZeroDrama: Prominent forum and IRC contributor who has been active since launch, heavy contributions to the last fork
Andy Hecker (SlimePuppy): Windows client compiler, forum Rep, IRC mod, "and other duties as required"
ambethia: Mac OSX Compiler.



Others
Website: http://catcoins.org/ Official Site
Website: http://catcoinwallets.com/
Catcoin price Android app: https://play.google.com/store/apps/details?id=stringtheory.cryptos.cat
Subreddit: http://reddit.com/r/catcoins
Facebook: https://www.facebook.com/CatcoinOfficial
Twitter: https://twitter.com/CatcoinOfficial
IRC: ##catcoin and #catcoin-dev
Faucet: http://www.thebitcoinmaster.com/catcoin/index.php

Satoshi came up with some great stuff, but he is not a god. There are a lot of bad assumptions in the Satoshi-derived C++ *coin clients, and it's not even clear what they all are. Now when you add in altcoins, difficulty adjustments, and the fact that some of the smartest programmers on the planet are getting paid over 6 figures USD to work on high-frequency trading bots (and probably mining-farm profit-switchers), we have quite the challenge on our hands.

But the biggest problem is still understanding the problem. The code does exactly what you tell it to do, not what your imaginary ideology of what crypto is supposed to be.

We have one obvious problem: the difficulty swings all over the place. I have some code that makes different assumptions than Satoshi did on how to deal with that. This code is apparently controversial. Now what would be useful is to have someone else write some code that attempts to resolve this difficulty swing issue in a different way. You might take Heavycoin's temporal retargeting, for example, which I think would probably work pretty well. But the point is, and if you look back I've said this before, you have to write code, and test it, and it works better if there are multiple people working together who can provide positive feedback, and most importantly, *patches to the code*

Logic check, aisle 5...   Geekhash also monitors and reports miner hash rate.  But since nobody knows the actual NETWORK hash rate, it's impossible to know any single miner's percentage of the network hash power.  It can be estimated but not known for certain.  It would be FANTASTIC if we could know, because then coin's difficulty adjustment process could lock-in on the planned block time and stick there.  But since dividing one's hash rate by an unknown value cannot give a known percentage, the rest of Hozer's process breaks rather quickly.  Yet another hollow attempt to obfuscate.

Posts reported for violating forum spam and advertising rules.

Last notice, Hozer - you were fired and banned from this project because you have in the past and continue to work to destroy the coin.  Your efforts to sew FUD and try to tell people that the BS of which you reek is actually rose perfume is not going to work.

Please find another place to call home - this isn't it.

What part of "Peer to Peer Network" is so difficult to understand?  Different codebases are not PEERS.  You can write any code you wish - but it's not Bitcoin if the critical portions of the code don't match or critical functions are changed.

Yeah, Hozer - we remember the forks of February - and the back-stabbing terrorist SOB that caused it.  We solved that problem when we fired you.

Dev members are being vetted much more strongly and professionally than they were in the past.

Food for thought.

Dogecoin just got hit by a bug bitcoin fixed a long time ago. (edit: I need to check the dates on articles better. Dogecoin fixed a bug a long time ago that was fixed by bitcoin a longer time ago, catcoin should not be affected by either of these bugs. The point, I hope, is still important)

http://bitcoinmagazine.com/3668/bitcoin-network-shaken-by-blockchain-fork/

A decentralized system that depends on all of us running exactly the same code is not a decentralized system. Having one 'blessed' wallet binary or github release that we all must use or face ridicule and damnation is not, in my opinion, a good thing. You all are, of course, free to disagree with me, if you wish.

But remember, remember, the fifth of.. um, I mean... the forks of february..?

Lots of coin developers like to blame their users when they don't understand something, or instead try to sell you something shiny and new like ethereum, mastercoin, and just about anything else announced in crypto in the last 2 years.

This attitude irritates me, and I would rather take it as a learning opportunity, and attempt to fix the mess we inherited from Bitcoin. So if we start with a design goal for catcoin to be that a solo-miner with 10% of the hash rate should be able to get about 10% of the catcoin mined over a 1 week period. If this does not work, then if you can admit catcoind is broken, we can work on an upgrade.

Now, because of probabilities, we'd probably have to say 10% of the hashrate should only expect 1% of the catcoin over 1 day, and there are not enough blocks in a day to get sufficient smoothing of the random way in which blocks are found.