I am testing, do you think I'm sitting here blaming pools without good reason?
The problem IS difficulty related - just not too high of difficulty, I believe someone is dropping their hashrate - who or why is the question of the day.
If there were any other issues pools would report rejected blocks.
The next block will be worth 4689.00 - most of these stuck blocks seem to be below 5000. That is what i am now looking at.
While I work on what the cause is ask yourself why after the next long block is solved hashrate will skyrocket again (as identifiable by the fast mining that will occur)
Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 275. (Read 368097 times)
March 17, 2014, 01:18:22 PM
March 17, 2014, 12:56:36 PM
maybe we should message them and let them know people are being disgruntled about their pool service because of the hash issue. might be enough reason for them to pause it for a day.
I mean maybe I'm insane, but my only theory is that they, with most of the hashrate get stuck for whatever reason (its there difficulty adjusted on these pools??), maybe a miner exploiting stratum, maybe a config issue, and because they usually find the most blocks, they essentially halt the network as no one else has the hashrate or luck to find blocks.Everything needs to be vetted at this point.
I still believe this to be an incorrect approach to start at the pools. Why? I'm no programmer, but logic tells me that pools (in general) are tried and tested when it comes to scrypt coins. They behave as expected and are using software for the pools that (at this point) has been pretty well vetted. I believe the stalling on the pools when the hashrate spikes is a symptom.
We presume you used a "proven" coin for the foundation of FLT. Hopefully a coin that was (at least at one point) heavily mined. If so, you should check the forums for any similar issues the coin might have had.
If there are none that are similar, you have to look at your code and what you've added to it. To me, this is the most obvious starting point because again, pools & mining are pretty well tested and this isn't some weird DDOS to stall out the coin, no one is getting coins when it's stuck.
Again, I don't even know if what i'd propose is plausible, but if this was my project team and they were stuck i'd start trying to troubleshoot with big, broad strokes.
- Go into the coin, "turn off" the POB stuff altogether (if possible), release a patch, see if it gets stuck
- If same thing happens, do the same with the POS stuff, release patch, see if it gets stuck
I just don't see how you're not starting at what you've added to the coin as the potential problem.
You said it yourself - your not a programmer. You don't realease patches to test things number 1, number 2 POB has no bearing - it's not even considered until a block is mined, POS will not be active for weeks. Pools kill coins all the time. If these things were the issue we would have seen it before.
The base for this coin as you say is NVC and PPC.
I find it hard to believe how people find it OK that a pool had 50% of the hashrate.
You've got to stop just pointing the finger at the pools. It's lazy. Anyone can start a pool - you can't control that, so stop blaming that.
Yes, it's not healthy for a pool to have over 50% hashrate, but only in terms of a 51% attack. What's happening here is nothing to do with that.
After insisting that the problem was difficulty-related (which it 100% is not), you've now conceded that it's not, because with the net hashrate being over 1GH/s, there's absolutely no chance that this is caused by people hopping off during stuck blocks. And yet you're still blaming pools?
Something else is going on here, and you need to do some unit testing to figure it out. Rather than just blaming the pools.
March 17, 2014, 12:20:38 PM
What is happening to the coin?? 
no surprise here. it's been like this since launch, although there was a good period where there were no problems.
March 17, 2014, 12:15:58 PM
What is happening to the coin??
March 17, 2014, 11:49:29 AM
Someone note the coinbase value of the next block when it hits.
how?
March 17, 2014, 11:32:33 AM
Someone note the coinbase value of the next block when it hits.
March 17, 2014, 11:16:34 AM
its a bad idea to mine the coin in general at this state...
March 17, 2014, 11:12:51 AM
Is it to high of diff to solomine this with 1.7m hash?
March 17, 2014, 10:38:26 AM
Bitember
Net Hashrate
2029.79 MH/s
Another stuck block incoming
Net Hashrate
2029.79 MH/s
Code:
Pool Hash Rate 1,025.962 MH/s :o
Pool Efficiency 99.65%
Current Active Workers 660
Current Difficulty 42.06122295
Est. Next Difficulty 28.35588064 (Change in 1 Blocks)
Est. Avg. Time per Round (Network) 1 minute 28 seconds
Est. Avg. Time per Round (Pool) 2 minutes 56 seconds
Est. Shares this Round 43071 (done: 879.33%)
Next Network Block 11649 (Current: 11648)
Last Block Found 11647
Time Since Last Block 26 minutes 45 seconds
Pool Efficiency 99.65%
Current Active Workers 660
Current Difficulty 42.06122295
Est. Next Difficulty 28.35588064 (Change in 1 Blocks)
Est. Avg. Time per Round (Network) 1 minute 28 seconds
Est. Avg. Time per Round (Pool) 2 minutes 56 seconds
Est. Shares this Round 43071 (done: 879.33%)
Next Network Block 11649 (Current: 11648)
Last Block Found 11647
Time Since Last Block 26 minutes 45 seconds
Another stuck block incoming
March 17, 2014, 09:50:04 AM
Guys, you got to balance out the hash power. Last time the coin forked, I believe the dev used the cloudminers fork over bitember, which you can see here:
https://bitcointalksearch.org/topic/m.5667953
If you all want to risk losing coins on a fork, go ahead.
https://bitcointalksearch.org/topic/m.5667953
If you all want to risk losing coins on a fork, go ahead.
March 17, 2014, 09:47:31 AM
So, what is the exact problem at this moment?
The problem is that bitmember has had 50% and somtimes over of total hashrate. If everyone would start using a different pool that would be great. Kidcoin has repeatedly asked that this happen
March 17, 2014, 09:44:11 AM
Cloudminers Orphaning blocks now
They seem to be fine. I'm not sure if 3 orphans in a row is the sign of a problem, or just something that can happen. Possibly the network hash rate fluctuating makes orphans more likely? What you will notice is that the difficulty from 3 hours ago was as low as 17, and now it is 43, so we are getting a lot of new traffic in the past few hours.
March 17, 2014, 09:24:10 AM
Cloudminers Orphaning blocks now
March 17, 2014, 09:09:44 AM
So, what is the exact problem at this moment?
No ones knows for sure 
March 17, 2014, 09:02:50 AM
So, what is the exact problem at this moment?
March 17, 2014, 08:54:57 AM
Now my coins at Bitember are back in balance........WTF is happening guys?
One of the cronjobs was stuck. Everything is running fine now. Enjoy your coins and keep mining
Thanks.
BTW, don't you think 3% fee is insane? I know, I'm free to mine somewhere else....just wondering.
March 17, 2014, 08:53:56 AM
Now my coins at Bitember are back in balance........WTF is happening guys?
One of the cronjobs was stuck. Everything is running fine now. Enjoy your coins and keep mining
March 17, 2014, 08:53:31 AM
Quote
At stuck block 11302 it says 2092mH/s but the total poolshashrate is now about 926mH/s.
Shouldn't the nethashrate also be adjusted or is it fixed when started a new block?
http://explorer.fluttercoin.us/block_crawler.php
Shouldn't the nethashrate also be adjusted or is it fixed when started a new block?
http://explorer.fluttercoin.us/block_crawler.php
Woah, are these number right?
http://explorer.fluttercoin.us/block_crawler.php?block_hash=00000000019c7d2d21bcbe9d7ff2d9d5715c734229e13dc613b15ab63644a3b5
http://explorer.fluttercoin.us/block_crawler.php?block_hash=0000000004cee733879832cb3d8e517600cb3772882a86ae633ac6ec8aa9bb4c
Block Height: 11302 Block Time: March 17, 2014, 00:28:12
Block Height: 11303 Block Time: March 17, 2014, 06:42:02
6 hours for one block?
March 17, 2014, 08:52:38 AM
Nevermind payout just went through
March 17, 2014, 08:47:55 AM
Which pool is the best please?
Take cloudminers for now.
TY
Jump to: