You can try to reset your peer database too (move all peers* files away to a temp folder) and make sure you've included the mentioned addnode lines in your tigercoin.conf file.

I was totally wrong about the cause of your mining issue. I just took a short look at your error message and jumped to conclusions. Apologies.

I took a closer look and found out the problem is some buggy code in the way cgminer calculates the serialized block height. This results in faulty block height data in your mined blocks.

As a last resort you could also set queue to 0 but I doubt you need this with expiry and scantime set to 1..
Unless you really need to, keep it at default (1).

In fact, I'd advise to try setting both expiry and scantime to 1. As long a you run solo and local, there's no harm in doing so, and it will minimize the risk on working on expired work due to new found blocks on the network.

It looks like you are finding blocks just fine, the only thing is your miner is finding them after their height already have been mined by somebody else.
This means your miner keeps working on the work it got dispatched for too long before checking whether it is still relevant.

Try to set the upper limit for new work to for example 20 seconds using the expiry argument:


Also, if your port is open and the client running, you will be acting as a full node.

You can also check this with:

After running the client for a while, you should see some inbound peers coming up ("inbound" : true).

You're definitely having connection issues to the internet. Something is blocking the client. Your log states it can't even 'surf' to http://91.198.22.70 to check your current IP at DynDNS.

Your firewall or anything like that is probably blocking the client from having access to the internet.

fred96002001, do you see any errors in your debug.log?

Can you telnet to:

telnet 194.135.91.150 15660

?

Exactly. So don't throw an irrational high amount of power into the network or you'll be wasting some of your mining power. ;-)

Difficulty will pick up. Don't worry about that. In the meantime. If you mine, you earn rewards / fees. Just like always. If you mine with too much power, you'll mine less efficient. Just like always.
The fact that the network generates a few more blocks evey now and then doesn't really hurt you, does it? ;-) See it as a temporary extra insentive for miners if you will.

There is nothing wrong with the coin. All this is by design. The difficulty is adjusting just fine each block.  No worries.
The difficulty algorithm has a long term component built in which ensures block generation to keep on track. Also, this protects the network against known difficulty attacks.
Because block generation has been quite sluggish over the past few years, this long term component can have quite an intense result every once in a while. This will become less and less over time.

The main objective here is continued and uninterrupted block generation. This ensures TX capacity at any time you want. Consider this: if the network would have been steadily minting blocks every 45 seconds, it would have been at over 1.75 million blocks by now. We're close to 1 million..

An exchange would be very nice indeed. I'm sure this won't be a problem in the long run though. The coin won't die, so I guess it's just a matter of time.

iSpace has run into the 1.2.0.2 bug and is on a forked chain. I've told them multiple times months ago they should upgrade but unfortunatly they did not.

As long as you are running the latest version you are on the main chain.

There is no need to fork. Everything is just fine. The network is healthy and very resilient.  Tigercoin has plenty of TX capacity to process a lot more TXs per second than Bitcoin can at the moment.

Besides that, a new update is being built with very powerful new features.

Could you give a bit more information please?

- What client version do you run?
- Besides these error messages in your log file, is your client functioning normally?
- Are your seing only these three txid's giving errors in your logs? Or others as well?
- Do these error messages (so basically the same tc IDs) repeat themselves?

I noticed a bug that could render a client unable to download new valid blocks from it's peers.
This only happenness in a very specific situation on clients with a (temporary) bad connection receiving multiple valid chains.
Nonetheless, I advise to update your clients asap to guarantee stability of both your daemon and network.
The risk of running into this bug is higher when you are actively mining on your client. Especially when this is combined with slow network connections / slow block synchronising.

So I released a new client (version 1.2.0.3) on Github and updated the link to the Windows binary as well.


For your convenience, here is the link to github:
https://github.com/TigerCoinDev/Tigercoin
And the new Windows binary:
https://mega.nz/#!J99mUJ6B!2OVZY-Cz8O4MgS7FP7YOP-rQFijjZIfQ0UPcxetcOy4

Good luck & enjoy!

Bitnodes actually seems to be lagging behind at the moment.
The best thing to do is to use:

So as predicted block generation was quite fast for a while due to the new algo adjusting the sluggish network of the past few months (/year). I'll have to admit this went a bit less smooth than I anticipated. Still, I did mention upfront that block generation would be faster for a while. Thanks to all involved in throwing 55+ TH into the mix ;-)

Now, the algo will take care of stable block generation.
Of course it would help a lot to have more than one pool up and running. And maybe some solo miners. That would greatly help network stability.

But either way. Considering the current situation, from now on Tigercoin will be the most stable coin out there. :-)
No more waiting for multiple days for a new block to be generated.
No more malicious miners messing with the difficulty.
Just the most stable block generation possible. Maybe it will sometimes take longer than 45 seconds. Maybe sometimes less. But as long as there is hashing power, it will be the most stable you'll ever see.
You can transfer coins at any time without ages of waiting.

Also, max block size is 2MB.
So throughput is max 2MB every 45 seconds.
Which is over 26 times the throughput on the bitcoin network.

This might be a problem if the network gets really busy and you are on a 64 kpbs internet connection while you really need to be up to date (for example to be able to mine). But as long as you have solid hardware and connections you should be fine. ;-)

As a final note. It probably won't surprise you that I am working on a nice feature for the future.

I'm not that familiar with P2Pool to be honest. But blocks are being generated on the network just fine.
There are no known issues with mining on the 1.2.0.2 client.

Have you tried solo mining?

UPDATE: By the way the message you mentioned normally means you mined blocks that were orphaned.

FYI; I updated the addnodes to two nodes that seem to work well at the moment:

Finding blocks depends on your hash rate. Also, make sure your system time (clock) is accurate.

Difficulty should be around 1690 at the moment and is adjusted every block.
Block height is around 491652 now.

Yes. As mentioned before:


Or, put another way: Block 482297 on the iSpace chain has an invalid difficulty value and thus is invalid. None of the other clients in the network will ever accept this block, or any blocks generated/built upon it.
So I am afraid that client has to resync with the network in order to be on a valid chain.