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

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

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?  

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.

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.  

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.

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

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)

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.

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

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.

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.

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? 

we need a reality show for this shit.

Good - you have the current wallet.

I understand solo mining, and have done it on CAT.  That's why I asked you for info on what you were using and how you were configured - because I know for a fact the wallet works - if it did NOT work, I wouldn't have allowed it to be released.

The hash rate reported by the wallet is a very rough guess based on how long it took to solve blocks.  Nobody on the network knows how many miners are connected.  Individual pools can measure their hash rate if they choose, but most use a block time estimate as well.  Bottom line - nobody can say for sure that they are about 1/3 of the network.

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

I'm using the current wallet, from the OP in this thread on 12/26.


You're talking apples and oranges with pool and solo mining..  You're pool mining in your own pool, and a pool elsewhere.

Solo mining requires the wallet to work, which it will not do for me.

And watching you guys bicker is hysterical.  

You're not 'fixing' anything by using Berkeley 5.3 for the Windows build.  We want to use the SAME database for all wallets so that databases are compatible.  The database proven to work for the MinGW Windows builds, as specified in the build instructions and used for the current wallet, is 6.0.20.  The Ubuntu repositories currently hold 5.1.4 for 12.04 and 5.3.21 for 14.04.  There is nothing wrong with the specified database - it works just fine.

NO NO NO.  You want to cheat miners out of legitimate blocks by using an arbitrary minimum time limit.  The community and entire dev team said "hell no" when you tried to muscle that through earlier.  That's when you put the hacked code on one of three network seed nodes and caused the fork-fest from hell.  You might also remember that's when you were kicked off the dev team and banned from the dev channel.  Troll somewhere else - you're still fired.

We are staying true to Satoshi's papers and to the intent of crypto.  We will NOT cheat miners, we will NOT introduce centralized control, we will NOT manipulate code to make charts "look nice".  Not Going To Happen.

I have 15 MH/s on my own experimental pool, and 15 on GeekHash - both are working fine.  My wallets are compiled straight from the CatcoinOfficial/CatcoinRelease git.  What wallet are you running?  Where did you download it from?  And what was in your catcoin.conf when you were solo mining?

There is no 'kluged wallet' - the wallet and the release code is fully functional.  In addition, the code is fully open - there is no 'private code' and no code known by only one dev.

Digishield appears to be one option.  There are others that are being evaluated as well.

We already know that when we have a decent hash rate the algo smooths out and blocks approach the desired 10 minutes.  The largest problem we have right now with regards to miners is that we're too profitable for some to ignore.  I'm not entirely sure that's a real problem.   Make no mistake, however - the code IS being improved.

Yeah Hozer - you sure can show people what code to run to take-over a coin - you did it to CAT while supposedly on the dev team.  That's why we fired you.

I realize this forum is the land of misfit trolls, but really - do you think people have already forgotten what you did to CAT?  Based on the PMs I've been getting, I'm thinking not...

There's no keys. If you want to take over cat, all you need to do is rent or buy 50 to 100 mhash and it's yours. I can tell you what code to run (or change) if you want to have reasonable block times and limit swings caused by switchpools.

I have tested code that partially solves the difficulty adjustment problem. What I need are some people who are willing to test and deploy it in production. Once we have some automated tests we can fine-tune how it works, and add the Heavycoin temporal retargeting which decreases the difficulty if there are really long blocks.

What's ridiculous is the amount of arguing over stupid shit we have done when we could have fixed this 6 months ago the first time I posted code that solves the problem.

How about go right to the source and get the latest bitcoin-core instead?
I need some help with https://bitbucket.org/catcoin/catcoin to do the following

1) making gitian to build wallets work
2) fixing the windows build to use bdb5.3
3) miners to run catcoinds with a 3 to 5 minute minimum block time

(once that's all done I can port the catcoin block changes into the bitcoin-core codebase)

All the testing I've done shows the minimum block time should get us back to moderately usefull functionality, and *after* we do that, we can talk about other ways to fix difficulty adjustments once we have an automated regression tests running on all platforms with https://travis-ci.org/tmagik/catcoin

And until blaksmith has founder status on #catcoin-dev, you can join #catoshi-dev if you want to talk about development. I will not participate any further theoretical religious arguments that do not have a running regression test. If you want me to listen to you, write some code, otherwise the ultimate authority is whomever buys the most hashpower.

Seriously, yes.  Pull one of the better up-to-date LTC flavors and make your life easier.