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

Yes, I am unable to update my wallet. I downloaded the latest one from this thread and as each hour passes, so does the sync with network time increases.

define unable to update your wallet? make sure when you extract it you're running the new version of Catcoin-QT

Hey guys, after I downloaded the 8910 update I was unable to update my wallet.

OS: Windows 7
Client Version: v0.8.9.10-unk-beta

I had this issue and simply replaced by wallet.dat with an older backup. The age of the wallet backup doesn't matter, so I keep all my old backups in case one gets corrupted.

first let us know what OS you have.

if on linux:
close the app
delete everything except catcoin.conf and wallet.dat
backup catcoin.conf and wallet.dat
start the app

skydivebr,

   Please tell us what operating system you are running, and what wallet (help/about Catcoin/ version number).  Also, please tell us what wallet you are upgrading from and whether it was stand-along or installed.

    Thanks!

I cant update my wallet..=/

Error: Failed to connect best block
terminate called after throwing an instance of 'std::runtime_error'
  what():  CDB() : can't open database file wallet.dat, error -30974


Help guys!

Alright guys, I promised a few people I'd make a post about the status of the project, and to clear some concerns a few people have brought forward.

First off, to our users and pool operators, than you for your patience during this trying time, I know it's not easy to deal with forks, constant upgrades, and lost coins. For that you have my teams' sincere thanks.

With that being said, I am troubled by the sheer number of accusations that have been made against our pool owners, especially Coinium. Raistlinthewiz (the pool op) has been one of our closest supporters since the launch of this coin. He's worked tirelessly to bring a high quality pool with a custom front end offering many statistical advantages that have been a huge advantage to the team, and the community. I have spoken with him directly and he has confirmed losses in excess of 4000 CAT due to overpayment for invalid blocks that we're not caught before they were paid out. In the interest of disclosure, I have compensated him 500 CAT from my personal reserves in order to offset at least some of these loses. He has agreed to cover the rest with his own personal funds. I take accusations against him and our other pool ops very seriously , because (and I can't stress this enough) they were not at fault for these losses. This was something that was a network issue, start-to-finish, and was both unpredictable and unavoidable. I know it's frustrating that many of you may have lost coins, but the pools were not responsible for that. Also, as much as I'd like to say otherwise so you could have someone to blame, neither was my team. We've been working around the clock to resolve these issues, and we're finally to a place we're we believe we've resolved this issue for the immediate future.

To clarify what happened, I'll explain a couple of key issues that caused this whole incident:

1. KR105, the original dev, hard-coded the master seed nodes into the source code of catcoin. These nodes pointed to a domain that hasn't existed in over 2 months, this resulted in the catcoin wallets going into a P2P mode, and caused some people who were freshly syncing to download bad blockchains from old ancient nodes. We still are seeing some people running the original catcoin daemon and this was causing havoc within the network. We've tried to combat this a few ways, most importantly, the team and some of the pool owners have deployed a number of new super-nodes, that are both fast and stable. We've corrected the master seednodes in the new source code and this was applied with the maintenance patch. As we see more new wallets and pools come online, we will have less and less network issues, and we've already received positive feedback from users and one of our exchanges at how much faster the network syncs now, so for now we'll take that as a very nice step in the right direction.

2. ComputeMinWork: This was the root of the issue. Because of the new periods of low diff, followed by huge hash rate influxes, we saw a dramatic increase in the work submitted to the network, unfortunately due to another oversight by the original dev, this caused a protection system within the bitcoin code to activate and ban any nodes that were submitting work too quickly, and we were effectively DDoSing ourselves. This resulted in our primary nodes not talking to each other and as a result all the forks happened because none of the nodes were synced up because they were banned from each other. We've relaxed this protection slightly to accommodate this issue, and this has caused a dramatic improvement within the network.

Hope this helps, it was kind of the quick and dirty explanation, and some of my team could explain some of the changes in more detail, because I was not here while they were being built.

My CAT has now cleared in Cryptsy. I'm glad it took so long. I made the right decision and changed my mind. I'm sending it straight back to wallet. The new wallet is the dogs bollox cats whiskers! Works like a charm. THANKS DEVs!
 

The answers you seek have been posted multiple times in the past 24 hours.

We released the V8.9.10 maintenance wallet.  Pools and exchanges are still upgrading.  Once they upgrade, the have to work through transactions processed on the wrong blockchains.  Once all the analysis is complete, 'lost' coins will be replaced.

Update for those in the same situation:

Cryptsy sorted out all of my missing deposits without any problems, all I needed to do was send them the following info:

Transaction ID
Type of Coin
Date Sent
Amount sent

It's quite easy to get all of this using the blockchain explorer (blocks.catstat.info, when it goes back up), simply search for your Cryptsy deposit address, all the info you need should be there. If it isn't, then your coins were probably on the wrong fork...

so ok i try the p2pool node http://solidpool.org/ and now you had 500+
for one day

from my laptop that is what I get, I really love to mine cat, but I place my money on servers for the complete farm of servers that host http://www.e-pool.net and all the pools

I found blocks 23404 and 23406 on us.coinium.org; both are now confirmed in MPOS and account balance is ZERO, no payout whatsoever.

REALLY worried about how these upcoming blocks that get confirmed behave.

ALREADY lost 502 CAT on coinium during "forks", also; this bullshit is happening with my coinium account.

ID        Date                                    TX Type    Status    Payment Address    TX #    Block #    Amount
293218    2014-02-19 07:25:07    TXFee    Confirmed    9fyYnT5r...6x9rrD5a                n/a    0.10000000
293217    2014-02-19 07:25:07    Debit_AP    Confirmed    9fyYnT5r...6x9rrD5a               n/a    16.94979336
293212    2014-02-19 07:22:06    TXFee    Confirmed    9fyYnT5r...6x9rrD5a                 n/a    0.10000000
293211    2014-02-19 07:22:06    Debit_AP    Confirmed    9fyYnT5r...6x9rrD5a                n/a    58.35606648

Confirmed transactions with no transactions and no corresponding block numbers.

What the fuck is going on.

Yo amarian we join your P2P node and it's you and the 7kh/s that's pretty much it.  Last mined I just got from a recent block was .5, you didn't catch a block for 2 days prior since I had last hopped on it.

Also, your DOA/orphan is near 30% why even point a card toward that.

I let some coins pay out few hours ago, didn't notice any problems?

This happen when people do not use p2pool network.

Mine on p2pool and you get your coins instantly

What the fuck is up with coinium and when are they going to pay out?

Is Coinex paying out?

Thanks!  Credit for this goes to Maverickthenoob. 

The page is down temporarily - that was a 'quick and dirty' link for some overnight exploring.  The permanent link will be at blocks.catstat.info.

One step at a time.

coinex switchpool was on cat