[TGC][ANN] Relaunch Tigercoin - Official thread

[ComputerGenie]

Blockexplorer http://tgc.explorer.bitnodes.net "502 Bad Gateway"...

Yeah, a working explorer would be nice. 

[1714649793]

1714649793

[1714649793]

1714649793

[1714649793]

1714649793

[BitcoinNational]

Blockexplorer http://tgc.explorer.bitnodes.net "502 Bad Gateway"...

Yeah, a working explorer would be nice.  

agree.
bitnodes one has been non-functional for +1year.
you can pull addnodes from cryptopia still, @coininfo section.
we need to raise $120/year for one.
any strong hands willing to lend a hand?

[GrinZ]

TGC added to cryptoguru.tk 
http://cryptoguru.tk/CurrencyInfo/index.php?Currency=TGC

[hammers400]

My wallet has 11 active connections and still downloading the blocks only about half way after 8 hours. Am I right in think that by leaving my wallet running 24/7 it will act as a full node once all blocks downloaded? Id like to give somthing back after Ive managed to download all of those blocks.. Ive checked and can access my ip and port 15660 via bitnodes checker so presume its working.

[hammers400]

Hi I could really do with some help solo mining TGC. Complete neewbie at this so bear with me.
I have my wallet synced and upto date and 9 active connections. I am using cgminer and so far have solved over 100 blocks!! but not one share has been accepted and I have made no progress on mining any TGC. Surley I am doing something wrong. Heres my cgminer config. Im guessing that my solved blocks are reaching the network too late?

cgminer -o http://127.0.0.1:15661 -s all --expiry 5 --queue 0 -u myusername -p mypassw --btc-address myTGCwalletaddress

Cgminer runs great and I am finding blocks just not getting any confirmed shares or TGC

Any help would be great and I will send some TGC to anyone that can help me solo mine my first block

[ComputerGenie]

...Any help would be great and I will send some TGC to anyone that can help me solo mine my first block

First, what are you mining with (CPU, USB, etc.)?
Second, what OS are you using?
Next, are you sure that you're "solving blocks" (i.e., actually over the 100-200k difficulty that the network has?
Lastly, is there anything in your "debug.log" that indicates anything about blocks found/submitted?

[hammers400]

I am using a gekko usb asic miner running at about 30GH slow I know, and using windows 10.
I can pool mine no issues with cgminer. I just wanted to try solo mining TGC. The difficulty is low according to my wallet blocks and cgminer reports a difficulty of anywhere between 14k to 40k as the blocks come in.
just left cgminer running for a couple of hours and got this.


A:0  R:105430  HW:0  WU:378.2/m
Connected to (null) diff 18.9K without LP as user tigercoinrpc
Block: 1212a2a1...  Diff:18.9K  Started: [17:06:55.844]  Best share: 120K

SOLVED 4 BLOCKS!
Does not have own long-poll support
 Work templates received: 0
 Share submissions: 4
 Accepted shares: 0
 Rejected shares: 4
 Accepted difficulty shares: 0
 Rejected difficulty shares: 105430
 Reject ratio: 100.0%
 Items worked on: 7387
 Discarded work due to new blocks: 5479
 Stale submissions discarded due to new blocks: 0
 Unable to get work from server occasions: 0
 Submitting work remotely delay occasions: 0



I cant find any log file for cgminer.exe but have a titanic log file for tigercoinqt in my roaming dir?

[hammers400]

I would be curious as to what nodes the pools are using as it would seem theres a delay for me..?

[hammers400]

looking through the debug.log I am getting this for said solved blocks


ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : block height mismatch in coinbase
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=getblockcount

any ideas on whats going wrong?

[ComputerGenie]

looking through the debug.log I am getting this for said solved blocks


ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : block height mismatch in coinbase
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=getblockcount

any ideas on whats going wrong?

You may need to close your wallet and rerun it with the -reindex switch. If that doesn't work, then it's possible that cgminer will not work directly with this coin.

[hammers400]

reindexing seems to be taking ages its just sitting at 438 weeks behind no progress I dont think reindexing is working correctly. debug.log growing rapidly with

Former block not found so NULL -> Not using strict timer for now since block received out-of-order
ProcessBlock: ORPHAN BLOCK, prev=00000000002448583ba9c6bc45b31f81e674a3602e07aa3da036f33ae6b9a683

similar entries over and over.

I ll leave it running for a few hours and see if any progress is made


Glad i have a back up..

[TigercoinDev]

looking through the debug.log I am getting this for said solved blocks


ThreadRPCServer method=submitblock
ERROR: AcceptBlock() : block height mismatch in coinbase
ERROR: ProcessBlock() : AcceptBlock FAILED
ThreadRPCServer method=getblockcount

any ideas on whats going wrong?

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:

Code:

--expiry|-E <arg>   Upper bound on how many seconds after getting work we consider a share from it stale (default: 120)

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

You can also check this with:

Code:

getpeerinfo

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

[hammers400]

 reindexing was a no go..

ok i will set expiry to 20 seconds. I appear to be running a full node as have a total of 10 connections and 3 showing as inbound..

I will leave running for 24 hours mining and see if I get any success

Thanks for the help

[TigercoinDev]

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.

[hammers400]

ok I am restarting cgminer with those settings as still solving old blocks..

Thanks

[TigercoinDev]

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

[ComputerGenie]

If all else fails, try a different program, like BFGMiner.

Edit: this thread might help (or might not): https://bitcointalk.org/index.php?topic=1173963.0

[hammers400]

Still no joy solo mining just solving blocks too late shame the node i was running had 15 connections.. bfgminer wont work with my gekko 2pac which is a shame I would have liked to have given that option a try. Thanks for the help though its given me some insight.

I am back to the pools for the time being.

[TigercoinDev]

Still no joy solo mining just solving blocks too late shame the node i was running had 15 connections.. bfgminer wont work with my gekko 2pac which is a shame I would have liked to have given that option a try. Thanks for the help though its given me some insight.

I am back to the pools for the time being.

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.

[hammers400]

Ok
Shame about the buggy code in cgminer hope it gets fixed.
I am solving blocks successfully via pooled mining just not getting the full rewards as shared with the pool. Shame my hardware wont work with bfgminer.

Thanks