[ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving

[seattletu]

Wow I guess I didn't understand how it worked. I thought each pool had a block that they worked on separately from other pools.

[1714019134]

1714019134

[1714019134]

1714019134

[1714019134]

1714019134

[1714019134]

1714019134

[1714019134]

1714019134

[captin crunch]

wallet stuck on block 11302. tried restarting it, but no go. any suggestions? 

it's not your wallet. everyone is stuck there

[seattletu]

Is the problem with the difficulty though? Difficulty's only at 32 right now, but this block's been stuck for 90 minutes...

that's what we are trying to figure out. what's weird, is you will see ALL OF THE POOLS solve their block at right about the same time.

Do you guys even know how mining works LOL??? (no offense) - all of the pools DO NOT solve the block at the same time - 1 pool or solo miner finds the block.

Dude... seriously? The guy didn't say that the pools solve the same block, he was saying that all of the pools solve a block within a short time of one of the pools solving the stuck block. Probably not a good idea to be rude to your own community.

And anyway, why exactly do you think the problem is to do with difficulty? Difficulty is 32 right now and the block's stuck again. There's a 2GH/s net hashrate... no way is 90% of the network hopping off during a single block. Do you even know how mining works LOL?

No I legit didn't know, I thought each pool worked on a block, so when the block was finally solved, I thought it was odd that everybody solved at around the same time. Now I get it, but yet more confused than ever.

[captin crunch]

just curious, has anyone seen a best share on their miner that would have solved the block?

[hashbrown9000]

damn. our butterfly blocks are getting stuck in a crypto-spiderweb

[thekidcoin]

What everyone is failing to realize also is the blockchain is solving more than the expected # of blocks

block 10000 Block Time: March 15, 2014, 4:38 am
block 10811 Block Time: March 16, 2014, 4:31 am
expected blocks per 24 hours = 720
actual blocks=811

block 9871 Block Time: March 15, 2014, 12:29 am
block 11302 ("stuck" block were at) Block Time: March 17, 2014, 12:28 am
expected blocks per 24 hours = 720
actual blocks=1431

The blockchain is working.  Looking at these stuck blocks, difficulty is fine.

These are the possible issues:

- pool issue - pool with most of the hashrate stops mining correctly, possibly someone is exploiting the stratum exploit, they are setting them to a higher difficulty, and the block doesn't get solved, the other pools are having bad luck, and can't find the block (these smaller pools don't find blocks as often)

- The block interval is being calculated incorrectly.  In PPC it is said a POW block can be spaced between 10 minutes and 2 hours (would equate to 2 minutes and 24 minutes here) - but i can't see how this could ever be true even in PPC looking at the code where it does a min to determine the interval.  I am seeing no issue.

- Some party is pointing enormous hashrate and then dropping off on purpose to in effect stall the blockchain - this is doubtful though

- A major pool is having issues where it looks like they are mining, yet  their work is invalid for some reason - I really need pools to check their logs for rejected blocks - search for CheckBlock or ConnectBlock or if you see rejected shares.

Whats strange is that when block 11303 is found the hashrate will be far lower (understandable some people dropped off - but no way its 3/4 of the network) - then suddenly a little while later difficulty will rise.   There's no way this 3/4 of the network that supposedly dropped off just starts mining again within 15 minutes.  

This will drive me insane LOL

[seattletu]

What everyone is failing to realize also is the blockchain is solving more than the expected # of blocks

block 10000 Block Time: March 15, 2014, 4:38 am
block 10811 Block Time: March 16, 2014, 4:31 am
expected blocks per 24 hours = 720
actual blocks=811

block 9871 Block Time: March 15, 2014, 12:29 am
block 11302 ("stuck" block were at) Block Time: March 17, 2014, 12:28 am
expected blocks per 24 hours = 720
actual blocks=1431

The blockchain is working.  Looking at these stuck blocks, difficulty is fine.

interesting. but there is the variable of hashrate that might change those numbers right? i guess what i'm saying is, lets say the entire net hashrate stayed perfect consistent at 2 gh/s, and we had a really long block like the one now, 5+ hours, would there still be about 720 blocks in that 24 period? i get that it's about 720/day now, but it might be skewed a bit because of varying hashrates. i really don't know though.

[seattletu]

is it possible that a miner could solve the block, yet the coin server isn't getting the info that the block has been solved? i might be grasping at straws at this point.

[thekidcoin]

Is the problem with the difficulty though? Difficulty's only at 32 right now, but this block's been stuck for 90 minutes...

that's what we are trying to figure out. what's weird, is you will see ALL OF THE POOLS solve their block at right about the same time.

Do you guys even know how mining works LOL??? (no offense) - all of the pools DO NOT solve the block at the same time - 1 pool or solo miner finds the block.

Dude... seriously? The guy didn't say that the pools solve the same block, he was saying that all of the pools solve a block within a short time of one of the pools solving the stuck block. Probably not a good idea to be rude to your own community.

And anyway, why exactly do you think the problem is to do with difficulty? Difficulty is 32 right now and the block's stuck again. There's a 2GH/s net hashrate... no way is 90% of the network hopping off during a single block. Do you even know how mining works LOL?

Yes, I do know how it works - and theres no way there miners are suddenly jumping right back on after a stuck block is found.  And yes, that's exactly what he thought - he even said so LOL.  And I wasn't being rude, I was joking with the guy.

What your saying, that the blocks are being solved close together is because the hashrate is high enough to mine faster because the difficulty is low.  Look at the next block after the stuck block is solved - note the difficulty.  Note then how fast blocks are solved indicating the hashrate is HIGH and difficulty steadily rises.

If hashrate didn't drop off, then difficulty would remain high for the next block after the solved block - but its doesn't - but yet it is fast enough to mine blocks super fast.

I would like to have one of the pools shutdown for 1 day, and see if it happens.  Whichever has been having the most hashrate when the block gets stuck.  Just to rule that out, because as of now I can see nothing concrete that could possibly be the issue.

[thekidcoin]

is it possible that a miner could solve the block, yet the coin server isn't getting the info that the block has been solved? i might be grasping at straws at this point.

only if its rejected I think...

[tabnk]

We are getting rich

[thekidcoin]

What everyone is failing to realize also is the blockchain is solving more than the expected # of blocks

block 10000 Block Time: March 15, 2014, 4:38 am
block 10811 Block Time: March 16, 2014, 4:31 am
expected blocks per 24 hours = 720
actual blocks=811

block 9871 Block Time: March 15, 2014, 12:29 am
block 11302 ("stuck" block were at) Block Time: March 17, 2014, 12:28 am
expected blocks per 24 hours = 720
actual blocks=1431

The blockchain is working.  Looking at these stuck blocks, difficulty is fine.

interesting. but there is the variable of hashrate that might change those numbers right? i guess what i'm saying is, lets say the entire net hashrate stayed perfect consistent at 2 gh/s, and we had a really long block like the one now, 5+ hours, would there still be about 720 blocks in that 24 period? i get that it's about 720/day now, but it might be skewed a bit because of varying hashrates. i really don't know though.

It should be only 720 blocks yes, but its skewed as fast mining happens when difficulty is low.

Note also for a little over a week we never had this issue until it was traded on bter.  It could be a pool that can't handle the hashrate?  I'm grasping for straws now too LOL

This is insane

[thekidcoin]

time for bed will hit this in the morning

[seattletu]

What everyone is failing to realize also is the blockchain is solving more than the expected # of blocks

block 10000 Block Time: March 15, 2014, 4:38 am
block 10811 Block Time: March 16, 2014, 4:31 am
expected blocks per 24 hours = 720
actual blocks=811

block 9871 Block Time: March 15, 2014, 12:29 am
block 11302 ("stuck" block were at) Block Time: March 17, 2014, 12:28 am
expected blocks per 24 hours = 720
actual blocks=1431

The blockchain is working.  Looking at these stuck blocks, difficulty is fine.

interesting. but there is the variable of hashrate that might change those numbers right? i guess what i'm saying is, lets say the entire net hashrate stayed perfect consistent at 2 gh/s, and we had a really long block like the one now, 5+ hours, would there still be about 720 blocks in that 24 period? i get that it's about 720/day now, but it might be skewed a bit because of varying hashrates. i really don't know though.

It should be only 720 blocks yes, but its skewed as fast mining happens when difficulty is low.

Note also for a little over a week we never had this issue until it was traded on bter.  It could be a pool that can't handle the hashrate?  I'm grasping for straws now too LOL

This is insane

it is interesting that the crazy long blocks didn't start until it went on bter, and the high spike in hashrate that came with it.

the algorithm that affects difficulty, is it similar to other coins, or is it your own that you created? is that one of the factors that could be adjusted with this fork you plan on doing?

[seattletu]

time for bed will hit this in the morning

the network plans on mining about 1200 blocks before you wake up 

[thekidcoin]

I don't think it's the difficulty itself anymore (unless we are being hit by a pool that's trying to pick and choose block values (lot of the stuck blocks are less than 5000) - it has to be something else IMHO.  

What??? No clue I am adding more stuff to debug this, but if anyone else knows any other good coin devs, if you can see if they can take a look, 2nd set of eyes.

Oh and no, difficulty algorithm is same as NVC and I think PPC.  Just changed the re target times etc... Nothing major.

[thekidcoin]

time for bed will hit this in the morning

the network plans on mining about 1200 blocks before you wake up 

Lol that's too many

[bullus]

What about the nethashrate vs total poolshashrate?

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

Still don't understand why the nethashrate isn't the same as the total poolshashrate.
If a pool can be offline and the nethashrate isn't drops than that pool isn't registered to the nethashrate?

http://explorer.litecoin.net/block/11302

http://explorer.litecoin.net/block/00000000019c7d2d21bcbe9d7ff2d9d5715c734229e13dc613b15ab63644a3b5

Pool Hash Rate491.136 MH/s
Pool Efficiency99.07 %
Current Active Workers339
Next Network Block11303    (Current: 11302)
Last Block Found11302
Est. Avg. Time per Round (Network)1 minute 5 seconds
Est. Avg. Time per Round (Pool)4 minutes 41 seconds
Est. Shares this Round32,932 (done: 9,441.60 %)
Time Since Last Block5 hours 31 minutes 47 seconds

again block was found by bitember but we are still finding block 11302.

[thekidcoin]

What about the nethashrate vs total poolshashrate?

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

Still don't understand why the nethashrate isn't the same as the total poolshashrate.
If a pool can be offline and the nethashrate isn't drops than that pool isn't registered to the nethashrate?

http://explorer.litecoin.net/block/11302

http://explorer.litecoin.net/block/00000000019c7d2d21bcbe9d7ff2d9d5715c734229e13dc613b15ab63644a3b5

Pool Hash Rate491.136 MH/s
Pool Efficiency99.07 %
Current Active Workers339
Next Network Block11303    (Current: 11302)
Last Block Found11302
Est. Avg. Time per Round (Network)1 minute 5 seconds
Est. Avg. Time per Round (Pool)4 minutes 41 seconds
Est. Shares this Round32,932 (done: 9,441.60 %)
Time Since Last Block5 hours 31 minutes 47 seconds

again block was found by bitember but we are still finding block 11302.

This pool could be the issue if it's not updating...

[thekidcoin]

What about the nethashrate vs total poolshashrate?

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

Still don't understand why the nethashrate isn't the same as the total poolshashrate.
If a pool can be offline and the nethashrate isn't drops than that pool isn't registered to the nethashrate?

http://explorer.litecoin.net/block/11302

http://explorer.litecoin.net/block/00000000019c7d2d21bcbe9d7ff2d9d5715c734229e13dc613b15ab63644a3b5

Pool Hash Rate491.136 MH/s
Pool Efficiency99.07 %
Current Active Workers339
Next Network Block11303    (Current: 11302)
Last Block Found11302
Est. Avg. Time per Round (Network)1 minute 5 seconds
Est. Avg. Time per Round (Pool)4 minutes 41 seconds
Est. Shares this Round32,932 (done: 9,441.60 %)
Time Since Last Block5 hours 31 minutes 47 seconds

again block was found by bitember but we are still finding block 11302.

This pool could be the issue if it's not updating...

It's per new block - it's a calculation