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

[serje]

why the hell is the spread so big between cryptys and allcrypt???

[SlimePuppy]

Post your catcoin.conf please?  And share what device(s) you were using for mining and what mining software you were using as well.  We'll get you running.

Thanks in advance...

rpcuser= -gone-
rpcpassword=  -gone-
maxconnections=1000
rpcallowip=*
rpcport=7000
daemon=1
server=1
gen=0
testnet=0
listen=1
addnode=162.243.226.39:9933
addnode=213.136.68.97:9933
addnode=97.125.247.123:9933
addnode=107.170.40.107:9933

Anything else?  

Yes - I still need the miner and software.  Post the miner command line info or config file as well, please.

You can remove the addnodes.  Max connections is limited to 8 normally, so the 1000 is not going to do anything useful.

IF your miner is pointed at this computer's IP and port (assuming it's an ASIC and controlled by another box, or is something run by the same machine) then you'll still need to let it run for more than 2 days as hitting a block is still by chance, chance takes longer when blocks are slow, and there's a possibility that blocks will be orphaned if mega-hash comes in during our fast block phase.

On my personal/test pool, for example, mining with 15MH/s, I found 8 blocks, had 6 orphaned, and am waiting the 120 confirms for the two blocks that remain.

I use that .conf file for any solo mining, as it is pretty much plug and play, just change the user/pass/nodes and port. (which this is about the 30th coin I've used it on)

Since all you need is the user/pass/port/server/listen/allowip then yeah, pretty much...  You might as well get rid of the stuff that you don't need as you're changing all the required entries anyway...

The mining software is multi-miner which is a gui interface for BFG miner.  This allows me to have a list of several coins to mine, and switch in literally 2 clicks, and has worked on everything else..  It's also more or less required since I have 6 asics and they require individual serial numbers to be called out with clock speed.  It's pointed at the wallet which is on another box, at the correct port evidenced by it getting a difficulty.

So - you're using a quick-switch front-end for a mining package that is not the easiest to get working correctly and as yet unidentified mining ASICS - and you think that solo-mining a coin that you don't know the overall hash rate for is a path to instant wealth as long as you give it two whole days?  

Again, you mention your test pool.  I DON'T HAVE A POOL, I AM SOLO MINING..

Yes, I heard you every time you said you were SOLO MINING.  My comment about the pool on my machine was about ORPHANS not about the mining interface.  Also, whether one solo mines, uses a stratum proxy, or a pool (which is all I'm really using this experimental pool for - a stratum proxy), they require the SAME INTERFACE AND FUNCTIONS FROM THE COIND.

I point the finger back at the wallet.  I have not in my year plus of mining, mined something, with a large percentage of the hash, for 2 days, and never saw a block, unless the wallet is fucked up.

You are welcome to put your fingers where you wish.  Were I you, I'd use a pool, as it's clear you either don't or won't understand how to analyze your successes or failures to determine root cause.  

The slow block/fast block phase is a complete bullshit, and needs to get fixed

Of course the slow block/fast block phase needs to get fixed.  That's why we're testnetting ways to fix it.

Since you say you've successfully solo mined other coins with your current configuration, and since you acknowledge that when you connect to your catcoin wallet you get difficulty info (and I assume other indications of a good config as well), and since the Cat codebase is based on and uses the same code found in Bitcoin, Litecoin, and thus nearly every other coin on the streets, and since pools and mining software interface with wallets the same way, and since I have personally solo-mined (successfully) on our current windows wallet, it's pretty clear that the wallet's doing exactly what it's supposed to be doing.

Let's analyze the battlefield you've chosen to extract profits from.  During the slow blocks (they're slow because most of the mining hash has jumped off - leaving me and a couple of others that are mining), your ~15MH/s will be a significant part of the hash rate, but the difficulty is high.  Result:  slow block generation.  When the difficulty falls off, more miners come in - the blocks are fast because the hash rate is high and difficulty is lower.  Result:  You are no longer a significant part of the hash rate and block generation is not as fast as one might expect.

Hopefully you now agree that the source of your apparent frustration is your expectation, not your hardware or software choices.

Enjoy your weekend.

[damm315er]

Post your catcoin.conf please?  And share what device(s) you were using for mining and what mining software you were using as well.  We'll get you running.

Thanks in advance...

rpcuser= -gone-
rpcpassword=  -gone-
maxconnections=1000
rpcallowip=*
rpcport=7000
daemon=1
server=1
gen=0
testnet=0
listen=1
addnode=162.243.226.39:9933
addnode=213.136.68.97:9933
addnode=97.125.247.123:9933
addnode=107.170.40.107:9933

Anything else?  

Yes - I still need the miner and software.  Post the miner command line info or config file as well, please.

You can remove the addnodes.  Max connections is limited to 8 normally, so the 1000 is not going to do anything useful.

IF your miner is pointed at this computer's IP and port (assuming it's an ASIC and controlled by another box, or is something run by the same machine) then you'll still need to let it run for more than 2 days as hitting a block is still by chance, chance takes longer when blocks are slow, and there's a possibility that blocks will be orphaned if mega-hash comes in during our fast block phase.

On my personal/test pool, for example, mining with 15MH/s, I found 8 blocks, had 6 orphaned, and am waiting the 120 confirms for the two blocks that remain.

I use that .conf file for any solo mining, as it is pretty much plug and play, just change the user/pass/nodes and port. (which this is about the 30th coin I've used it on)

Since all you need is the user/pass/port/server/listen/allowip then yeah, pretty much...  You might as well get rid of the stuff that you don't need as you're changing all the required entries anyway...

The mining software is multi-miner which is a gui interface for BFG miner.  This allows me to have a list of several coins to mine, and switch in literally 2 clicks, and has worked on everything else..  It's also more or less required since I have 6 asics and they require individual serial numbers to be called out with clock speed.  It's pointed at the wallet which is on another box, at the correct port evidenced by it getting a difficulty.

So - you're using a quick-switch front-end for a mining package that is not the easiest to get working correctly and as yet unidentified mining ASICS - and you think that solo-mining a coin that you don't know the overall hash rate for is a path to instant wealth as long as you give it two whole days?  

Again, you mention your test pool.  I DON'T HAVE A POOL, I AM SOLO MINING..

Yes, I heard you every time you said you were SOLO MINING.  My comment about the pool on my machine was about ORPHANS not about the mining interface.  Also, whether one solo mines, uses a stratum proxy, or a pool (which is all I'm really using this experimental pool for - a stratum proxy), they require the SAME INTERFACE AND FUNCTIONS FROM THE COIND.

I point the finger back at the wallet.  I have not in my year plus of mining, mined something, with a large percentage of the hash, for 2 days, and never saw a block, unless the wallet is fucked up.

You are welcome to put your fingers where you wish.  Were I you, I'd use a pool, as it's clear you either don't or won't understand how to analyze your successes or failures to determine root cause.  

The slow block/fast block phase is a complete bullshit, and needs to get fixed

Of course the slow block/fast block phase needs to get fixed.  That's why we're testnetting ways to fix it.

Since you say you've successfully solo mined other coins with your current configuration, and since you acknowledge that when you connect to your catcoin wallet you get difficulty info (and I assume other indications of a good config as well), and since the Cat codebase is based on and uses the same code found in Bitcoin, Litecoin, and thus nearly every other coin on the streets, and since pools and mining software interface with wallets the same way, and since I have personally solo-mined (successfully) on our current windows wallet, it's pretty clear that the wallet's doing exactly what it's supposed to be doing.

Let's analyze the battlefield you've chosen to extract profits from.  During the slow blocks (they're slow because most of the mining hash has jumped off - leaving me and a couple of others that are mining), your ~15MH/s will be a significant part of the hash rate, but the difficulty is high.  Result:  slow block generation.  When the difficulty falls off, more miners come in - the blocks are fast because the hash rate is high and difficulty is lower.  Result:  You are no longer a significant part of the hash rate and block generation is not as fast as one might expect.

Hopefully you now agree that the source of your apparent frustration is your expectation, not your hardware or software choices.

Enjoy your weekend.

I am enjoying my weekend, thank you very much.  I had 3 days off of work in the month of december, including weekends, so 4 days off in a row I almost didn't know what to do with myself...

The unnamed asics are gridseed g-blades, I have 3 units, 2 stock, and 1 overclocked, each unit has 2 separate mining blades.  The stock units are supposed to run at 800mhz, and a single gridseed g-blade with both blades running 800mhz will do 5.2 mh/s, and easily overclock a bit, but like different amounts of overclocking.  Typically they like 837 mhz, but I have one that likes 850 mhz, and one that only likes 825 mhz, averaging that out each g-blade is good for about 5.6 mh/s..  The overclocked one is supposed to run at 975 mhz, but one blade likes 962, the other one likes 987 so that works out to about 6.6 mh/s.  So that makes 6 blades, that need to be set at 4 different operating speeds, and called out by serial numbers to get assigned the proper speed.  All total, that works out to 18.15 mh/s, but I had a power cable fail so I only put 5 blades or about 15 mh's toward cat for 2 days.

I have been running these since may, so I know them pretty well.  They are not without their quirks, and the USB drivers are finicky.  But they seem to like the BFG mining software, as I have been using it since shortly after it was released and it was a real improvement over the modded CGminer that was the recommended and having to restart the computer nearly every time I wanted to switch mining.

In that time, I have successfully solo mined (this is a partial list, because I've deleted the wallets of several coins that I've mined and sold off, with no intention of picking them up again):
BitcoinFast,
CryptoGraphic Anomaly,
Credits,
Einsteinuim,
Emerald,
Feathercoin,
Florin,
Franko,
Guncoin,
Hundred,
Imperial,
Infinite coin,
Money,
Netcoin,
NYC coin,
Octocoin,
Phoenix coin,
Riecoin,
Ronpaul coin,
Seedcoin
and
Syscoin.  

All of them successfully, with these very asics, with this same software and this same GUI, and the wallets on the same (different) machine that the cat wallet is on.

This very same rig is also running 5 280x or better GPU's. (which are no longer pointed as scrypt)

I have even run this puny 18 mh/s and gotten several Syscoin blocks in 2 days up against nearly a gigahash.  Yet, after all that, somehow my 15 mh/s against 45 mh/s in 2 days can't manage to get a single block, and it's in my setup?

And you imply that I want to mine Cat to get rich quick?

You are a funny man..  

[SlimePuppy]

I am enjoying my weekend, thank you very much.  I had 3 days off of work in the month of december, including weekends, so 4 days off in a row I almost didn't know what to do with myself...

The unnamed asics are gridseed g-blades, I have 3 units, 2 stock, and 1 overclocked, each unit has 2 separate mining blades.  The stock units are supposed to run at 800mhz, and a single gridseed g-blade with both blades running 800mhz will do 5.2 mh/s, and easily overclock a bit, but like different amounts of overclocking.  Typically they like 837 mhz, but I have one that likes 850 mhz, and one that only likes 825 mhz, averaging that out each g-blade is good for about 5.6 mh/s..  The overclocked one is supposed to run at 975 mhz, but one blade likes 962, the other one likes 987 so that works out to about 6.6 mh/s.  So that makes 6 blades, that need to be set at 4 different operating speeds, and called out by serial numbers to get assigned the proper speed.  All total, that works out to 18.15 mh/s, but I had a power cable fail so I only put 5 blades or about 15 mh's toward cat for 2 days.

I have been running these since may, so I know them pretty well.  They are not without their quirks, and the USB drivers are finicky.  But they seem to like the BFG mining software, as I have been using it since shortly after it was released and it was a real improvement over the modded CGminer that was the recommended and having to restart the computer nearly every time I wanted to switch mining.

In that time, I have successfully solo mined (this is a partial list, because I've deleted the wallets of several coins that I've mined and sold off, with no intention of picking them up again):
BitcoinFast,
<snip>
All of them successfully, with these very asics, with this same software and this same GUI, and the wallets on the same (different) machine that the cat wallet is on.

This very same rig is also running 5 280x or better GPU's. (which are no longer pointed as scrypt)

I have even run this puny 18 mh/s and gotten several Syscoin blocks in 2 days up against nearly a gigahash.  Yet, after all that, somehow my 15 mh/s against 45 mh/s in 2 days can't manage to get a single block, and it's in my setup?

And you imply that I want to mine Cat to get rich quick?

You are a funny man..  

That's a nice bunch of words.  Unfortunately, you've commented about a lot of cool-sounding stuff, but nothing relevent to your problem.  I've said that a number of times, but you haven't gotten it yet.

First, going backward, here's the catcoin.conf for my private pool.  Look familiar?  :

Code:

server=1
daemon=1
rpcuser=<redacted>
rpcpassword=<redacted>
rpctimeout=30
rpcallowip=127.0.0.1
rpcport=7000

Sit down and listen to the old guy for a couple of minutes...

You are still ASSUMING you know the network hash rate, and thus estimating how many blocks you SHOULD receive based on that.  Block counts are based entirely on CHANCE.  Chance, by definition, is RANDOM.  Nobody - regardless of how many shiny toys they use - can get around chance - especially in only two days.  That's the first problem with your expectation.

The second is that a miner is a businessperson, and a smart business owner does her research.  Let's start with a tool that the Cat devs provide that most other coins do not:



We can see from this block-time chart that this coin currently is NOT generating regular 10 minute blocks.  It IS, however, generating a 10 minute block AVERAGE which is all that a coin is SUPPOSED TO TO - 10 minute blocks are a TARGET and a long-term average.  No, i'm not suggesting this is a normal looking chart - clearly it's not and I'll say yet again since repetition can sometimes be useful - we know it's not right and we're pounding changes on testnet.

As I explained last message - and you apparently ignored - during the slow blocks the network hash rate is very low - and frankly, my 30MH/s is most of it.  Even with that, look at the block history on Geekhash - our last known pool and note who's getting the slow blocks:

http://geekhash.org/?q=block_history
edit...
sorry, need an account to see the blocks...here's a screenshot I just took:  https://www.dropbox.com/s/q751l6z71fe4ur0/catblock_gh.jpg?dl=0
/edit
Slimepuppy and Blaksmith.  That's right - the dev team is mining the slow blocks - we've got our machines connected 24/7 supporting this coin.  (ZeroDrama would be in that mix as well, but his 30MH/s Zeus boxes melted the PSUs a couple of weeks back.)  Even with that, however, we're not snagging the low diff blocks - because that's when larger pools come in and snag those ~10 blocks.  That's when you would have the best chance to get fast blocks if the network hash rate stayed down - but it isn't - that's when the network hash rate spikes, because that's when the other quick-switching miners jump in.

Now that we've done your due diligence, I think we also have to observe that you are not being forced to mine this coin - clearly there's some value for you.  If you want the coins, you have to mine.  The absolute worst way to run an ASIC is to jump them around.  My Gridseeds, GAW Fury, and Black Widows take about 20 minutes just to get up to full speed; and my Antminers don't like pool switching much at all either.  Neither did my GPU rigs when I ran those.

So...my recommendation is to pick a coin you want to support and get on-board - and get rid of the front-end code that makes it easy to switch.  Jumping around - whether in currencies, coins, stocks, or bonds is a fool's errand.  They are mostly random and chaotic systems.  Gamblers always think they know better, but the folks that run the casinos are not gamblers, they're businessmen...  

You probably won't like all that I've said, but it comes from the heart and is as honest as humanly possible.
Good Hunting.
Andy

[MadGhost]

I am enjoying my weekend, thank you very much.  I had 3 days off of work in the month of december, including weekends, so 4 days off in a row I almost didn't know what to do with myself...

The unnamed asics are gridseed g-blades, I have 3 units, 2 stock, and 1 overclocked, each unit has 2 separate mining blades.  The stock units are supposed to run at 800mhz, and a single gridseed g-blade with both blades running 800mhz will do 5.2 mh/s, and easily overclock a bit, but like different amounts of overclocking.  Typically they like 837 mhz, but I have one that likes 850 mhz, and one that only likes 825 mhz, averaging that out each g-blade is good for about 5.6 mh/s..  The overclocked one is supposed to run at 975 mhz, but one blade likes 962, the other one likes 987 so that works out to about 6.6 mh/s.  So that makes 6 blades, that need to be set at 4 different operating speeds, and called out by serial numbers to get assigned the proper speed.  All total, that works out to 18.15 mh/s, but I had a power cable fail so I only put 5 blades or about 15 mh's toward cat for 2 days.

I have been running these since may, so I know them pretty well.  They are not without their quirks, and the USB drivers are finicky.  But they seem to like the BFG mining software, as I have been using it since shortly after it was released and it was a real improvement over the modded CGminer that was the recommended and having to restart the computer nearly every time I wanted to switch mining.

In that time, I have successfully solo mined (this is a partial list, because I've deleted the wallets of several coins that I've mined and sold off, with no intention of picking them up again):
BitcoinFast,
<snip>
All of them successfully, with these very asics, with this same software and this same GUI, and the wallets on the same (different) machine that the cat wallet is on.

This very same rig is also running 5 280x or better GPU's. (which are no longer pointed as scrypt)

I have even run this puny 18 mh/s and gotten several Syscoin blocks in 2 days up against nearly a gigahash.  Yet, after all that, somehow my 15 mh/s against 45 mh/s in 2 days can't manage to get a single block, and it's in my setup?

And you imply that I want to mine Cat to get rich quick?

You are a funny man..   

That's a nice bunch of words.  Unfortunately, you've commented about a lot of cool-sounding stuff, but nothing relevent to your problem.  I've said that a number of times, but you haven't gotten it yet.

Sit down and listen to the old guy for a couple of minutes...

You are still ASSUMING you know the network hash rate, and thus estimating how many blocks you SHOULD receive based on that.  Block counts are based entirely on CHANCE.  Chance, by definition, is RANDOM.  Nobody - regardless of how many shiny toys they use - can get around chance - especially in only two days.  That's the first problem with your expectation.

The second is that a miner is a businessperson, and a smart business owner does her research.  Let's start with a tool that the Cat devs provide that most other coins do not:



We can see from this block-time chart that this coin currently is NOT generating regular 10 minute blocks.  It IS, however, generating a 10 minute block AVERAGE which is all that a coin is SUPPOSED TO TO - 10 minute blocks are a TARGET and a long-term average.  No, i'm not suggesting this is a normal looking chart - clearly it's not and I'll say yet again since repetition can sometimes be useful - we know it's not right and we're pounding changes on testnet.

As I explained last message - and you apparently ignored - during the slow blocks the network hash rate is very low - and frankly, my 30MH/s is most of it.  Even with that, look at the block history on Geekhash - our last known pool and note who's getting the slow blocks:

http://geekhash.org/?q=block_history
Slimepuppy and Blaksmith.  That's right - the dev team is mining the slow blocks - we've got our machines connected 24/7 supporting this coin.  (ZeroDrama would be in that mix as well, but his 30MH/s Zeus boxes melted the PSUs a couple of weeks back.)  Even with that, however, we're not snagging the low diff blocks - because that's when larger pools come in and snag those ~10 blocks.  That's when you would have the best chance to get fast blocks if the network hash rate stayed down - but it isn't - that's when the network hash rate spikes, because that's when the other quick-switching miners jump in.

Now that we've done your due diligence, I think we also have to observe that you are not being forced to mine this coin - clearly there's some value for you.  If you want the coins, you have to mine.  and the absolute worst way to run an ASIC is to jump them around.  My Gridseeds, GAW Fury, and Black Widows take about 20 minutes just to get up to full speed; and my Antminers don't like pool switching much at all either.  Neither did my GPU rigs when I ran those.

So...my recommendation is to pick a coin you want to support and get on-board - and get rid of the front-end code that makes it easy to switch.  Jumping around - whether in currencies, coins, stocks, or bonds is a fool's errand.  They are mostly random and chaotic systems.  Gamblers always think they know better, but the folks that run the casinos are not gamblers, they're businessmen... 

You probably won't like all that I've said, but it comes from the heart and is as honest as humanly possible.
Good Hunting.
Andy

May be we need to have a more optimized miner.

[hozer]

I am enjoying my weekend, thank you very much.  I had 3 days off of work in the month of december, including weekends, so 4 days off in a row I almost didn't know what to do with myself...

The unnamed asics are gridseed g-blades, I have 3 units, 2 stock, and 1 overclocked, each unit has 2 separate mining blades.  The stock units are supposed to run at 800mhz, and a single gridseed g-blade with both blades running 800mhz will do 5.2 mh/s, and easily overclock a bit, but like different amounts of overclocking.  Typically they like 837 mhz, but I have one that likes 850 mhz, and one that only likes 825 mhz, averaging that out each g-blade is good for about 5.6 mh/s..  The overclocked one is supposed to run at 975 mhz, but one blade likes 962, the other one likes 987 so that works out to about 6.6 mh/s.  So that makes 6 blades, that need to be set at 4 different operating speeds, and called out by serial numbers to get assigned the proper speed.  All total, that works out to 18.15 mh/s, but I had a power cable fail so I only put 5 blades or about 15 mh's toward cat for 2 days.

I have been running these since may, so I know them pretty well.  They are not without their quirks, and the USB drivers are finicky.  But they seem to like the BFG mining software, as I have been using it since shortly after it was released and it was a real improvement over the modded CGminer that was the recommended and having to restart the computer nearly every time I wanted to switch mining.

In that time, I have successfully solo mined (this is a partial list, because I've deleted the wallets of several coins that I've mined and sold off, with no intention of picking them up again):
BitcoinFast,
<snip>
All of them successfully, with these very asics, with this same software and this same GUI, and the wallets on the same (different) machine that the cat wallet is on.

This very same rig is also running 5 280x or better GPU's. (which are no longer pointed as scrypt)

I have even run this puny 18 mh/s and gotten several Syscoin blocks in 2 days up against nearly a gigahash.  Yet, after all that, somehow my 15 mh/s against 45 mh/s in 2 days can't manage to get a single block, and it's in my setup?

And you imply that I want to mine Cat to get rich quick?

You are a funny man..  

That's a nice bunch of words.  Unfortunately, you've commented about a lot of cool-sounding stuff, but nothing relevent to your problem.  I've said that a number of times, but you haven't gotten it yet.

Sit down and listen to the old guy for a couple of minutes...

You are still ASSUMING you know the network hash rate, and thus estimating how many blocks you SHOULD receive based on that.  Block counts are based entirely on CHANCE.  Chance, by definition, is RANDOM.  Nobody - regardless of how many shiny toys they use - can get around chance - especially in only two days.  That's the first problem with your expectation.

The second is that a miner is a businessperson, and a smart business owner does her research.  Let's start with a tool that the Cat devs provide that most other coins do not:

(catstat.info chart snipped)

We can see from this block-time chart that this coin currently is NOT generating regular 10 minute blocks.  It IS, however, generating a 10 minute block AVERAGE which is all that a coin is SUPPOSED TO TO - 10 minute blocks are a TARGET and a long-term average.  No, i'm not suggesting this is a normal looking chart - clearly it's not and I'll say yet again since repetition can sometimes be useful - we know it's not right and we're pounding changes on testnet.

As I explained last message - and you apparently ignored - during the slow blocks the network hash rate is very low - and frankly, my 30MH/s is most of it.  Even with that, look at the block history on Geekhash - our last known pool and note who's getting the slow blocks:

http://geekhash.org/?q=block_history
Slimepuppy and Blaksmith.  That's right - the dev team is mining the slow blocks - we've got our machines connected 24/7 supporting this coin.  (ZeroDrama would be in that mix as well, but his 30MH/s Zeus boxes melted the PSUs a couple of weeks back.)  Even with that, however, we're not snagging the low diff blocks - because that's when larger pools come in and snag those ~10 blocks.  That's when you would have the best chance to get fast blocks if the network hash rate stayed down - but it isn't - that's when the network hash rate spikes, because that's when the other quick-switching miners jump in.

Now that we've done your due diligence, I think we also have to observe that you are not being forced to mine this coin - clearly there's some value for you.  If you want the coins, you have to mine.  and the absolute worst way to run an ASIC is to jump them around.  My Gridseeds, GAW Fury, and Black Widows take about 20 minutes just to get up to full speed; and my Antminers don't like pool switching much at all either.  Neither did my GPU rigs when I ran those.

So...my recommendation is to pick a coin you want to support and get on-board - and get rid of the front-end code that makes it easy to switch.  Jumping around - whether in currencies, coins, stocks, or bonds is a fool's errand.  They are mostly random and chaotic systems.  Gamblers always think they know better, but the folks that run the casinos are not gamblers, they're businessmen...  

You probably won't like all that I've said, but it comes from the heart and is as honest as humanly possible.
Good Hunting.
Andy

May be we need to have a more optimized miner.

If anyone would like to discuss the mathematics and control-theory about how to optimize both the miners and catcoind to get reasonable returns for solo-mining, please join #catoshi-dev. Otherwise try mining on http://catstat.info:9927/static/ where we can all see what your hashrate is, and most importantly, when you are mining, and I can debug it if anything is wrong.

The biggest problem I have is that I can't debug ignorance of economic and control theory, and how the two are inextricably linked with cryptocoins. Some others on this group have different assumptions about how things work, and how they should work, and this seems to be one of the reasons we have regular catfights.

If you can convince me you've been mining, and it's working right, and there are shares on p2pool, and you still don't get any catcoin, I'll send you some, because it's the right thing to do to make sure solo miners with 5 to 10% of the hashrate get 5-10% of the catcoins mined. If it's not working, then something is broken, and if we can cooperate instead of catfight, we have all the source code to fix the damn thing, so let's fix it.

[hozer]

I point the finger back at the wallet.  I have not in my year plus of mining, mined something, with a large percentage of the hash, for 2 days, and never saw a block, unless the wallet is fucked up.

No rejects, no orphans, nothing.

The slow block/fast block phase is a complete bullshit, and needs to get fixed, along with the solo mining.

I mine other stuff that doesn't solo mine, but at least the dev's admit to a problem instead of trying to blame the miner when it is a wallet issue.

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.

[hozer]

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..?

[SlimePuppy]

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..?

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.

[SlimePuppy]

If anyone would like to discuss the mathematics and control-theory about how to optimize both the miners and catcoind to get reasonable returns for solo-mining, please join <spam deleted>. Otherwise try mining on <spam deleted> where we can all see what your hashrate is, and most importantly, when you are mining, and I can debug it if anything is wrong.

The biggest problem I have is that I can't debug ignorance of economic and control theory, and how the two are inextricably linked with cryptocoins. Some others on this group have different assumptions about how things work, and how they should work, and this seems to be one of the reasons we have regular catfights.

If you can convince me you've been mining, and it's working right, and there are shares on p2pool, and you still don't get any catcoin, I'll send you some, because it's the right thing to do to make sure solo miners with 5 to 10% of the hashrate get 5-10% of the catcoins mined. If it's not working, then something is broken, and if we can cooperate instead of catfight, we have all the source code to fix the damn thing, so let's fix it.

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.

[hozer]

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..?

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*

[SlimePuppy]

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
---------------------------------------

Catcoin - CAT

The Scryptcat version of Bitcoin!

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

[hozer]

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
---------------------------------------

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.

[SlimePuppy]

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
---------------------------------------

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.

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://bitcointalk.org/index.php?topic=441402.msg9251852#msg9251852

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

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.

[SlimePuppy]

New miners in the house - Nice JOB everyone! 

[hozer]

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
---------------------------------------

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.

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://bitcointalk.org/index.php?topic=441402.msg9251852#msg9251852

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

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.

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)

[hozer]

New miners in the house - Nice JOB everyone! 

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.

[hozer]

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.

[etblvu1]

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

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

[SlimePuppy]

New miners in the house - Nice JOB everyone!  

I've got my A2 (30mhash) pointed at <snip> 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.

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.