[ANN] TagCoin - Multi Token Wallet and Trading Platform

[torzsy]

My wallet shows:

Code:

"blocks" : 28777,
"connections" : 12,

http://tag.cryptominer.net/ pool shows:

Code:

"blocks" : 28777,
"connections" : 35,

[edit]

Code:

"difficulty" : 105.05757923,

[torzsy]

Transaction also went through to Cryptsy.

[TehLuNaTiC]

Rename to ORPHANCoin maybe???

[ny2cafuse]

Fork again.  Tagmining, Hashfaster, and Botpool are on same block ahead of the explorer and Cryptopools.

Unless Tagmining falls behind the explorer, we will be operation with business as usual.  However, we have had another 6 orphans in a row for the last hour.

Mark, I seriously think this needs to be investigated by your developer staff.  I'm not sure if it would help, but perhaps you should really consider changing the difficulty re-target to every 10-20 blocks.  This would be a fast re-target time(every few hours) and would not only help even out the difficulty swings, but would help stabilize miners' payouts over time.  Yes it would mean that multipools would hammer TAG longer, but when they stop mining TAG we would have an equally long period of low difficulty.

Vesper had mentioned graphing out some comparisons on re-target times.  Not sure if he has preliminary data yet, but it would be worth investigating.

-Fuse

[Steam20]

TAG seems to be sorting itself out but I will try to spread the message to spread the hash power. If it means creating a few pools as joint ventures with others then I can do that as well. I cannot demand that Botpool, or any pool for that matter, refuse new miners..:-) I can only ask them to throttle back...

As for which chain anyone should be on, I suggest going with the block explorer at explorer.tagcoin.org, which should always have the highest block...

If TAG "is sorting itself out" why is the block explorer reporting the last blocks with Difficulty: 0.00417864?

As I'm typing this blocks 28706, 28705, 28704, 28703 and 28702 all have stupid low diff on block explorer.

Block #28702
Time: 2014-01-14 14:31:33
Hash: b8c580b4d6a000f87fec2ed2c3b97533a5521272179d321acc0da31fbd7b617f
Total Coins: 29.99939400
Size: 489
Merkle Root: e4848436b153b202c233fcebe3d79f2c9bc2d36302043107971e0d0e48f012a4
Nonce: 0
Version: 4
Confirmations: 1
Difficulty: 0.00531907

Previous Block Hash: 00000000006df51e7252af09e4386d675ae36b577f21147edded56432354c98e
Next Block Hash:

Total Transactions: 2
0 97060a895b3ffdb2059179b324fd99042090f1f4abf2b450374ec3d00a4cd741 0
1 b9eac10c0844ac4814a7109f34bad136d8f84dd95171e5a11e4eee32f0ab539a 29.999394



Edit: A quick flick through shows a large proportion of blocks on the block explorer with a sub 0.006 diff.

Edit 2: Blocks 28702 through to 28713 all done at sub 0.006 diff, blocks 28714 @ 141 diff, 28715 @ 105 diff, then back to sub 0.006 diff on block 28716. It looks like all these low diff blocks are going to some solo miner.

Edit 3: Block 28716 found by Botpool but turned out as an orphan ends up on the blockexplorer with diff 0.00576075 who needs hashpower lol!

Tell me about it lol

[canopus]

1780808 canopus 2014-01-14 22:59:25 Fee Orphaned   28871
1780807 canopus 2014-01-14 22:59:25 Credit Orphaned   28871
1780445 canopus 2014-01-14 22:59:20 Fee Orphaned   28870
1780444 canopus 2014-01-14 22:59:20 Credit Orphaned   28870
1779916 canopus 2014-01-14 22:51:14 Fee Orphaned   28869
1779915 canopus 2014-01-14 22:51:14 Credit Orphaned   28869
1779390 canopus 2014-01-14 22:35:18 Fee Orphaned   28863
1779389 canopus 2014-01-14 22:35:18 Credit Orphaned   28863
1778856 canopus 2014-01-14 22:09:14 Fee Orphaned   28859
1778855 canopus 2014-01-14 22:09:14 Credit Orphaned   28859
1778383 canopus 2014-01-14 22:07:14 Fee Orphaned   28858
1778382 canopus 2014-01-14 22:07:14 Credit Orphaned   28858
1777891 canopus 2014-01-14 21:56:17 Fee Orphaned   28856
1777890 canopus 2014-01-14 21:56:17 Credit Orphaned   28856
1777396 canopus 2014-01-14 21:37:13 Fee Orphaned   28853
1777395 canopus 2014-01-14 21:37:13 Credit Orphaned   28853
1776924 canopus 2014-01-14 21:30:38 Fee Orphaned   28851
1776923 canopus 2014-01-14 21:30:38 Credit Orphaned   28851


 

[Morning-Star]

Fork again.  Tagmining, Hashfaster, and Botpool are on same block ahead of the explorer and Cryptopools.

Unless Tagmining falls behind the explorer, we will be operation with business as usual.  However, we have had another 6 orphans in a row for the last hour.

Mark, I seriously think this needs to be investigated by your developer staff.  I'm not sure if it would help, but perhaps you should really consider changing the difficulty re-target to every 10-20 blocks.  This would be a fast re-target time(every few hours) and would not only help even out the difficulty swings, but would help stabilize miners' payouts over time.  Yes it would mean that multipools would hammer TAG longer, but when they stop mining TAG we would have an equally long period of low difficulty.

Vesper had mentioned graphing out some comparisons on re-target times.  Not sure if he has preliminary data yet, but it would be worth investigating.

-Fuse

Edit: Marks response below answers the doubts I had. Thanks.

[tagbond]

We had a look at it and we will add a couple of changes in the next fix, along with the change in percentage for PoS (which is set at .015% instead of 1.5%).

The coins generated at .006 diff are the PoS coins that are mined by the clients, not by PoW...so right now there are 2 diffs shown, depending on what was mined. That's how hybrids work.

@Morning-Star - can you define "huge security hole" in more detail rather than throwing it out there. And please be technical about it so we all understand...

As for changing difficulty algo, no, we will leave it as it is, for various reasons.

I would like to remain diplomatic, but please will people making comments on TAG, understand what they are talking about before they throw out "solutions"...

[Morning-Star]

My "huge security hole" comment was mostly in reference to a previous comment you made about preference to the highest blockchain, and noticing a block mined and orphaned on Botpool show us on the explorer as a diff 0.006 block.

[Dabs]

"blocks" : 29070,
"difficulty" : 178.79404054,

hehehe... dang, I thought I saw it as low as 28 just a few hours ago.

I think it's relatively easy to identify the PoS blocks on the explorer. You just check the block hash, and if it does not have a bunch of zeroes at the beginning, then it is a PoS mined block.

The PoW blocks have a bunch of zeroes.

[vesperwillow]

This is probably just my luck, but, I can't sync my wallet anymore. Others are working fine. It worked yesterday but not as of this morning. I tried addnoding tagmining but that isn't helping either.

[ny2cafuse]

I just checked... it's just your luck lol.

-Fuse

[torzsy]

I could sync a few mins ago.

[bitcoingeo1]

altcoin overload....no idea who, why, what, how. i guess i better get em all

[vesperwillow]

Stupid nearly offworld disruptive network I'm on right now probably.

Well I'm still mining tag at least lol. But I am trying out that new 42coin..

[gjerek]

I added new pool.

http://tag.coin-pool.org/

PPLNS 1% Fee, with stratum + vardiff

[Silez]

With such hashrate it feels like mining ltc in early days. Don't sure will it be worth like ltc.

[zccopwrx]

Other than Botpool, anyone else out of sync with Hashfaster and tagmining?  We seem to be ahead of botpool.... again.

[Dabs]

Woot, someone beat me to the dice game. I've always wanted to put one up.

[ny2cafuse]

The Devil Has Been Summoned!

Looks like Botpool is the source of the issues here.

Time to take out Botpool it seems.


~BCX~

Did someone say his name 3 times... quick, go back and check!



Honestly though, BCX... Botpool is just trying to push through the issues as much as the rest of us.  I think there was some incorrect speculation with regards to were the blame lies.  Now, if you want someone to blame for the crazy difficulty spikes... I'm pretty sure we all know where the blame lies there.

But I beg you to go easy with the legitimate community members and pools.  As much as we've been concerned about Botpool's hashrate, I think they are really trying to do the right thing with the pool.

-Fuse

EDIT- Also, I can, with almost 100% certainty, say that the forks and orphans are not a result of one pool's hashrate, or even the difficulty fluctuations like I had thought.  I will not go into specifics, as it is not my place to say, but I have discussed the issue with Mark, and he and his developers have identified the cause and are working towards the resolution.  I will put my rep on the line and say that I believe the next patch will fix our issues.