[TGC][ANN] Relaunch Tigercoin - Official thread

[vlgafox]

its problem in my account(((
your account is valid and show pool alive... but my account show dead

[1714609982]

1714609982

[1714609982]

1714609982

[1714609982]

1714609982

[vlgafox]

I'm confused now, are you using GPU to mine or Ant S5...lol

I'm check this pool on my PC. But I have 30 Ant S5

[Marty19]

its problem in my account(((
your account is valid and show pool alive... but my account show dead

PM your iSpace username and I'll check it out.

[vlgafox]

its problem in my account(((
your account is valid and show pool alive... but my account show dead

PM your iSpace username and I'll check it out.

PM sent

[peteabdo]

Since it changed to 16 per a block everything has orphaned.

[DaCheese]

This coin is such a fail.

This "DEV" has destroyed the original TGC.

[DaCheese]

To ISpace, Cryptsy and all major stakeholders.

This "DEV" released a coin which has been modified to destroy it.

This guy is a TROLL and he has done it successfully to TGC.

Please rollback to the original TGC client and take caution to people pretending to be "DEV" of a coin with honest intentions.

We need you guys to save TGC. Because 5 blocks per second with no difficulty adjustment is destroying this coin.

A concerned miner....

[mastermvi]

Something going wrong. today all work stoped client dond sync. Whats going on?

[mastermvi]

Whats Happening?

[mastermvi]

where everyone?

[TomInVa57]

GL, People are mining TGC at over 54 TH/s on iSpace, that's the problem. The confirmation are also screwed up again, required confirmation on the pool show lover blocks still needing 119 confs, where some more current blocks have already confirmed and also up to 119 confs pending. Same thing happened after the update before this last one. I think DEV needs to rethink the block times, it's just too quick.

Plus, there is no place to trade that I can find anyways, only exchange I know that has TGC is Cryptsy, and it's been in maint since the first fork.

[Marty19]

GL, People are mining TGC at over 54 TH/s on iSpace, that's the problem. The confirmation are also screwed up again, required confirmation on the pool show lover blocks still needing 119 confs, where some more current blocks have already confirmed and also up to 119 confs pending. Same thing happened after the update before this last one. I think DEV needs to rethink the block times, it's just too quick.

Plus, there is no place to trade that I can find anyways, only exchange I know that has TGC is Cryptsy, and it's been in maint since the first fork.

Blocks are being found so fast that the background process is struggling to keep pace. As the diff increases or the hashrate drops this will sort itself out and catch up. No rewards will be lost.

[peteabdo]

ispace.co.uk how do you set up a worker and where do I put in my wallet address. there is no FAQ

[Marty19]

There is no need to setup a worker in advance simply use a worker name prefixed with your username, e.g. username.worker1
Password can be any value.

Wallet address are entered on the My Mining Dashboard under the My Payouts option.

[mastermvi]

Can someone to contact with ispace administration, to stop there minig , what reason to mine if no one can sync his wallet with net?

[Marty19]

Can someone to contact with ispace administration, to stop there minig , what reason to mine if no one can sync his wallet with net?

Our wallet is syncing fine, here is our peerinfo details:

Code:

    {
        "addr" : "193.192.37.135:65225",
        "services" : "00000001",
        "lastsend" : 1444816386,
        "lastrecv" : 1444816386,
        "bytessent" : 1536789,
        "bytesrecv" : 213015,
        "conntime" : 1444801495,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.2/",
        "inbound" : true,
        "startingheight" : 589626,
        "banscore" : 0,
        "syncnode" : true
    },
    {
        "addr" : "5.19.208.202:43464",
        "services" : "00000001",
        "lastsend" : 1444816386,
        "lastrecv" : 1444816386,
        "bytessent" : 2543263,
        "bytesrecv" : 323478,
        "conntime" : 1444801607,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.2/",
        "inbound" : true,
        "startingheight" : 589676,
        "banscore" : 0
    },
    {
        "addr" : "37.123.223.229:55169",
        "services" : "00000001",
        "lastsend" : 1444816386,
        "lastrecv" : 1444816386,
        "bytessent" : 2454760,
        "bytesrecv" : 311817,
        "conntime" : 1444802139,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.2/",
        "inbound" : true,
        "startingheight" : 589877,
        "banscore" : 0
    },
    {
        "addr" : "204.11.237.233:51233",
        "services" : "00000001",
        "lastsend" : 1444816386,
        "lastrecv" : 1444812595,
        "bytessent" : 73598,
        "bytesrecv" : 127,
        "conntime" : 1444812595,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.1/",
        "inbound" : true,
        "startingheight" : 6500,
        "banscore" : 0
    },
    {
        "addr" : "91.236.140.149:64595",
        "services" : "00000001",
        "lastsend" : 1444816386,
        "lastrecv" : 1444816300,
        "bytessent" : 81002384,
        "bytesrecv" : 5295970,
        "conntime" : 1444813880,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.2/",
        "inbound" : true,
        "startingheight" : 558375,
        "banscore" : 0
    },
    {
        "addr" : "91.236.140.149:64594",
        "services" : "00000001",
        "lastsend" : 1444816384,
        "lastrecv" : 1444816300,
        "bytessent" : 65521572,
        "bytesrecv" : 4137731,
        "conntime" : 1444813880,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.2/",
        "inbound" : true,
        "startingheight" : 558375,
        "banscore" : 0
    },
    {
        "addr" : "82.161.253.248:55570",
        "services" : "00000001",
        "lastsend" : 1444816386,
        "lastrecv" : 1444816386,
        "bytessent" : 1200264,
        "bytesrecv" : 153622,
        "conntime" : 1444814135,
        "version" : 70001,
        "subver" : "/Satoshi:1.2.0.2/",
        "inbound" : true,
        "startingheight" : 581446,
        "banscore" : 0
    }

[mastermvi]

91.236.140.149:64594 and 91.236.140.149:64595 this mine. one stoped syncing  at 516* second at 558* and what is fine.

[greengo]

bfgminer.exe -S antminer:all  --set-device antminer:clock=x0881 -o stratum+tcp://ispace.co.uk:3337 -u green.tiger -p x
What wrong?

 bfgminer version 5.3.0 - Started: [2015-10-14 13:17:40] - [  0 days 00:50
 [M]anage devices [P]ool management Settings [D]isplay options  [H]elp [
 Pool 0: ispace.co.uk        Diff:32  +Strtm  LU:[14:07:49]  User:greeny
 Block: ...2480ff89bb40e660  Diff:2.55k (18.24Gh)  Started: [14:07:49]  I:
 ST:3  F:3  NB:1035  AS:0  BW:[169/  1 B/s]  E:5.22  BS:111k
 1            |  1.82/ 1.80/ 1.62Gh/s | A:26 R:2+0( 11%) HW:0/none
--------------------------------------------------------------------------
 CBM 0:       |  1.80/ 1.80/ 1.62Gh/s | A:26 R:2+0( 11%) HW:0/none
--------------------------------------------------------------------------
 [2015-10-14 14:07:35] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:35] Stratum from pool 0 detected new block
 [2015-10-14 14:07:38] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:38] Stratum from pool 0 detected new block
 [2015-10-14 14:07:40] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:40] Stratum from pool 0 detected new block
 [2015-10-14 14:07:41] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:41] Stratum from pool 0 detected new block
 [2015-10-14 14:07:44] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:44] Stratum from pool 0 detected new block
 [2015-10-14 14:07:45] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:45] Stratum from pool 0 detected new block
 [2015-10-14 14:07:46] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:46] Stratum from pool 0 detected new block
 [2015-10-14 14:07:49] Network difficulty changed to 2.55k (18.24Gh)
 [2015-10-14 14:07:49] Stratum from pool 0 detected new block

and nothing more/

[logictense]

Whats Happening?

Nothing, there have been multiple insights into important truths of this project that i might have had duty to share with the world if u had asked me but i would not do that for one simple reason: i have inside knowledge and u dont.

[TigercoinDev]

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.