 Show Posts
|
|
Pages: [1] 2 »
|
Mandatory Update to Version 1.3
You must update before Feb 2 00:00:00 GMT
Changes:
-Trust system has been overhauled to deal with the orphans issue
-Stake reward fixed, now is properly 1.5%
-PoW subsidy reduction has been altered to be more granular. This change will take effect at block 41000. Pool operators, update your config file accordingly.
 |
|
|
|
Right now the explorer shows "no block found" for almost 9 hours, for blocks 29414 through to 29605. 2014-01-16 09:21:32 29609 4b7de2f60e38b5d26e6993c21e80bfd4a34356d20b17789018288f387be20708 489 2 2014-01-16 09:20:28 29608 159f3460bfcaf332e46be2e62079c089d0378971edb72936fb693f6d6858156f 915 4 2014-01-16 09:18:12 29607 cf9966f49800636b5d9018a63e63e5a0fd653af5d174eb005ed1ca4c6d985cef 488 2 2014-01-16 09:17:46 29606 a20b3a74efdb32be6ea208e6ac4078834b9a08dd965a1b79c79f6932f19d4732 947 4 1970-01-01 00:00:00 1970-01-01 00:00:00 1970-01-01 00:00:00 1970-01-01 00:00:00 1970-01-01 00:00:00 1970-01-01 00:00:00 1970-01-01 00:00:00 Edit: Looks like that huge run of POW blocks I commented on earlier have disappeared off the explorer, and prior to the <9 hour gap blocks 29370 to 29413 are all POS. I've got my own thoughts on what I think the problem is but I'll keep them to myself this time. Looking forward to the fix |
|
|
|
|
and countless POW blocks all in a row.
|
|
|
|
|
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.
|
|
|
|
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. |
|
|
|
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.00531907Previous 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! |
|
|
|
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.compay 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. |
|
|
|
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...
The highest block isn't always the fork with the highest or lowest or good or evil hash, it's just pure chance. Correct me if I'm wrong: No need for a 51% attack here, just mine your own fork until it gets to a point where it overtakes everyone else, defaulting everything to your new high block fork. Or is this where POS comes in and saves the day? Am I missing something? |
|
|
|
What happens when withdrawals from an exchange go into thin air?
You lose the coins. Generally a good idea not to exchange coins during a fork. You never know what's going to happen. Now if you were to exchange coins to another coin, you're basically walking away with free coin. Which is what BCX claimed he was going to do to cryptsy... like revenge for something bigvern did. He had it out for him for some reason. -Fuse Yes I might lose coins but people will lose confidence in Tag. I might know when a fork going on, but there isn't a warning sign that pops up on exchanges or wallets warning users if there is currently a fork. We've had 2 forks within 48 hours (I'm guessing) with orphans left right and center and no changes even getting thought about. A fork prone coin is hardly going to be taken seriously when people start losing coins depositing and withdrawing from exchanges. Having said that I know it's important to not rush into a fix, better to get it right than to create other different problems. Re. BCX well I hope his motivation was justified. I went back over that section of the thread, he told people what he was doing, mining all the forks then later strengthening one fork while killing off others, and told everyone which fork to throw hash onto. Bad goodguy or good badguy? He never did clear up what he had against Bigvern, just that they had settled their disagreement. |
|
|
|
All the action happens when I am up in the air, and the weekend to boot.. ... as usual the blockchain sorted itself out...I think you all sorted the network out without my help - in any case all I can do is direct to the longest blockchain.. And if anyone had my direct connection info, no use when I am 30,000 feet up... No plans at this stage to change anything in the coin regarding difficulty changes as for the link at https://www.hashco.ws/stats/, I think they just stopped mining... Currently in Detroit airport waiting flight to fly to Washington.. I let HashCows know last night that there was a fork, and they got back to me letting me know they suspended TAG mining. I haven't notified them yet that it's resolved  That's a reason the difficulty is under 150 right now lol. I still think there needs to be some investigation into the orphans. I'm sitting at about 10% orphans on the pool for the week. All of this mess with possible forks/actual forks and the occurrence of all the orphans this week seem too coincidental. Whether it's a direct relation to the difficulty swings or the increased hashrate, or whatever... it needs to be looked at. Does anyone have any empirical evidence of other coins having high orphan rates for comparison? -Fuse Well one could argue the issue is not resolved. At one point the diff was a touch over 200 after HashCows suspended Tag, and as I type this the diff jumped from approx 150 to 109, so I think at least one other multipool still mines. There are still orphans showing up here and there, and the occasional block find time over 1000% seem strange too. I had some autopayments from Botpool go into into the ether (coins mined before the fork) but as a miner I accept the risk. What happens when withdrawals from an exchange go into thin air? |
|
|
|
solely based off the stats of the top miners in the pool I am in, it seems like lots of people are bailing  I'm not a big miner but I mined on 2 pools minimum 24 hours each and the both paid out approx 50-65% of what was expected so I'm mining something else for now. I don't have time to test every pool out to find one that acyually pays approx what is expected, so may I ask which one are you using? Hi, I run https://www.megamineros.com/CSC and its a small pool. In the long run it does not matter that much if you mine on a big or a small pool. Short term a small pool can be more erratic but on longer time spans like a week or more there is no or little difference. The last two weeks did have large fluctuations and there are higher spikes in finding blocks, that is all caused by the coinhoppers. They really impact difficulty and are damaging the stability of coins. Also this complicates the calculations on which the predictions are based. What can be a danger is having one pool getting too big and getting more than 50% of the network hashrate. That can really endanger a coin and miners should spread out over the various pools and not all stick to the same. Mining is not only about finding coins but also in handling transactions, ... if the network goes down the coin dies with it! In cgminer you can load balance your mining power over various mining pools and thus helping the network stability and its future. Yes It should average out, I'd be happy at 110% block find rate, but huge swings over 24hrs don't seem right, especially when those swings carry on for more than 24hrs and are always in the negative. I just looked at block percentage totals for three CSC pools, all are between 140% and 180%, indicating much longer than expected average block find times. I know that is over a very short time frame but that is indicative of the actual payment I was getting over longer 24hr + windows. I was on one pool for approx 72 hours before I realized I was wasting my time there. Without going to every CSC pool to find one that has a block find time least 110%, I'm assuming something is wrong with the hash/diff/block payout or something. If it is all attributed to coin hoppers then fair enough but a real shame. As a comparison the pool I am on now, mining a different coin, (that has a larger hashrate but still has +- 25% diff swings) the pool is at 102% block find percentage now and paid roughly 100% of expected coins for 2 weeks straight with only minimal daily payment swings, and has been since I last posted in this thread. I think the coin retargets diff every 4 mins. Edit: BTW if you see GhettoMiningCo pop up, that's me. That is an interesting conclusion. I am running for little over a month now and if i look at the block find over that period it is now at about 115%. If i look at the biggest pools like csc.hash.so and csc.dedicatedpool.com they are too high as well. So you are right in that in general it is too high and should be lower. How do solominers perform? Do you guys have high percentages as well? In that case, what could be wrong with the network? I can imagine that if one pool gets too big (50% or more) that it will hurt other pools as well moving all miners in the end to one pool which is NOT good. So i stay with my previous suggestion, either all big miners (hash power of 5MHash or more) do solo mining or they spread out their hashpower over all available pools to flatten out block find percentages and make the network more stable. Well I was mining Tag and it has forked twice with lots of orphans. The CSC pools I was bitching about seem pretty good now lol! |
|
|
|
Hmm, timing is suspicious. Mark is away and publicised the fact, it's late Sunday in the Philippines and there would be no one in the office. Is BCX playing around with us again?
What's BCX got against Tag??? There's purported evidence that in the past, he intentionally forked the coin for profit, and then helped fix it later on. That's what I've heard at least. Very interesting. I was lurking this thread when all that happened. I seemed to me that BCX was using a fork of Tag to make a point to Cryptsy at the time or something, I guess there is more to it. |
|
|
|
BOTpool is now the same the same as TAG, IT and HASH... and the Explorer on 27573 as well...
All pools and explorer are on 27574 at the moment with matching matching difficulty of 70.
Have look at the orphans on all the pools... BOT got hammered... even Scryptmining had an orphan... the only reason IT has no orphans is because there is only 5Mh/s there at the moment.
Fuse... here is the orphan problem exposed.
EDIT - Both times I have seen this... it started with BOT getting hit with literally double hash-rate... 2500Mh/s and 1900Mh/s... the only reason I picked it up either time is because I have miners spread across several pools and notice that 'current block' and 'difficulty' does not match... and each time BOT was holding massive hash-rate, then lagged out and then taken off-line and restarted. Last time BOT was offline for quite a while and TAG was the fail over as the hash-rate doubled quickly... but each time the difficulty drops dramatically and there are lots of orphans.
If this is in fact a difficulty issue, maybe the devs need to rethink the way the difficulty adjusts. Instead of having a retarget every block, maybe set it to 10-20 blocks or even higher. IDK. It just seems like there are a lot of issues lately with the increased hashrate. I just want to go to sleep and wake up knowing things aren't going to explode when I'm asleep. Damn sleep messing everything up lol. The Block Explorer just reset to 27536?!?!?!
Now to 27572!!!!
OK what's the deal with that? Last time Tagmining was on the same fork as the block explorer and stayed safe. This time Botpool was on the same fork as the block explorer, but this time the explorer gets reset, and Botpool lost out both times. Is there a preference for what happens based on what any or all of the exchanges are on or something? I think someone reset the block explorer, and it just synced with the majority of the pools that we on the higher block height. If there was a preference to what pools or exchanges it follows, that would be a huge loophole that everyone would be bidding on to be "the one". I would sell my wife for it just so I didn't have to worry that when go to sleep the pool is going to follow the wrong fork. That's nerve-wracking. Yeah I'm probably just reading too much into it all. |
|
|
|
Hmm, timing is suspicious. Mark is away and publicised the fact, it's late Sunday in the Philippines and there would be no one in the office. Is BCX playing around with us again?
What's BCX got against Tag??? |
|
|
|
The Block Explorer just reset to 27536?!?!?!
Now to 27572!!!!
OK what's the deal with that? Last time Tagmining was on the same fork as the block explorer and stayed safe. This time Botpool was on the same fork as the block explorer, but this time the explorer gets reset, and Botpool lost out both times. Is there a preference for what happens based on what any or all of the exchanges are on or something? |
|
|
|
There have been some really cool coins the last few weeks. Sadly some of them had technical issues, but otherwise they have looked good and had ace names.
But does anyone else really dislike this fcuking stuipid Coinye bag of shite?
Honestly, it makes DOGE look good.
Please ignore it and perhaps it will slither away.
I think you are getting Kanye West and Coinye mixed up  |
|
|
|
|
My wallet, the blockchain explorer, and botpool seem to be on the same block. coinwaz looks to have the same diff at botpool
As I type this tagmining caught up to the same block no as the others.
|
|
|
|
|
tag has at least 2 forks right now!
|
|
|
|
|
tagming diff 47 @ block 27551 botpool diff 98 @ block 27553
|
|
|
|
Tagcoin fork? Will those shares ever mature?
Yeah Botpool and some other pools went off on their own fork for a while. Even though their "wrong" fork had a higher diff, indicating the highest hashpower they all eventually reverted back to the other fork. I was mining on Botpool with my wallet on the correct fork for a while before I realized what was goin on.  Even as a small time miner and speculator, I've noticed my techniques that worked for me last month do not work this month. The algo might need to be redesigned for profitability to surpass Litecoin comfortably. There is no point in doing what everyone else does, that just evens out the playing field. Just 2c. |
|
|
|
|
