I added new pool.
http://tag.coin-pool.org/
PPLNS 1% Fee, with stratum + vardiff
Topic: [ANN] TagCoin - Multi Token Wallet and Trading Platform - page 59. (Read 301292 times)
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..
Well I'm still mining tag at least lol. But I am trying out that new 42coin..
altcoin overload....no idea who, why, what, how. i guess i better get em all 
I could sync a few mins ago.
I just checked... it's just your luck lol.
-Fuse
-Fuse
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.
"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.
"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.
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.
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"...
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"...
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
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.
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
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
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 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...
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
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
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
Rename to ORPHANCoin maybe???
Transaction also went through to Cryptsy.
My wallet shows:
http://tag.cryptominer.net/ pool shows:
[edit]
Code:
"blocks" : 28777,
"connections" : 12,
http://tag.cryptominer.net/ pool shows:
Code:
"blocks" : 28777,
"connections" : 35,
[edit]
Code:
"difficulty" : 105.05757923,
^
You, sir, are a scholar and a gentleman.
And also my hero...
You, sir, are a scholar and a gentleman.
And also my hero...
Haha, glad I could make that smiley happen.
hey devs - please have a look after that scamming pool: http://tag.botpool.net/
yesterday i saw many orphaned blocks at my account after ich saw them 15 mins. before confirmed...
though in the last days i have seen always orphaned blocks at that pool - but TAG has no standard-15-seconds-block-time with many orphans
hey miners at that botpool have a look at your stats!
i have chosen for now the TAG-PPS-pool http://tag.cryptopools.com
pay per share - thats good!
i will never mine again with that stinky botpool!
yesterday i saw many orphaned blocks at my account after ich saw them 15 mins. before confirmed...
though in the last days i have seen always orphaned blocks at that pool - but TAG has no standard-15-seconds-block-time with many orphans
hey miners at that botpool have a look at your stats!
i have chosen for now the TAG-PPS-pool http://tag.cryptopools.com
pay per share - thats good!
i will never mine again with that stinky botpool!
Have you read the last couple of pages here? There have been two forks with orphans everywhere. Botpools high hashrate may or may not be the cause of the issue but the orphans are not just a problem on Botpool. Yes right now the percentages are very high on Botpool, but other pools have had bad runs too.
sorry, so i have to offer an excuse for my lack of the TAG-fork-informations and the orphans around this
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 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...
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!
As of right now, 15 of 53 are orphans, 1 in the last hour. That's almost a third. That's indicative of an ongoing issue with the chain(s). While it may be sorting itself out over time, if there were any more catalysts introduced I'm concerned it would get far worse. My uneducated opinion believes there needs to be some smoothing out to handle the waves of hash.
Jump to: