Topic: [ANN] FlutterCoin FLT Proof Of Transaction Cash Back for Sending & Recieving - page 274. (Read 368097 times)

So, I have spent a little time browsing through blocks on the block chain to see if there was any patterns in the blocks that are "stuck", and there is.

I can with some confidence say that block 11649 will have the following characteristics

The coinbase transaction will have 2 output transactions of equal size
The coinbase sig will be 26-28 characters long, and the last 14 characters of the sig will be 062f503253482f
The block will not be found by either of the pools mention in OP (Crunchharder, Bitember, Miningwithus or Cloudminers)


Coinbase sig for the latest block found by each of the pools for comparison:

I have no idea how to interpret the information above as I have very little technical insight to the inner workings of crypto coins and how blocks are generated.
But, assuming some of the information for the next block is known to the entire network (besides transactions), may guess is there could be some parameter or information in the upcoming block that the pools are unable to process correctly, and thus we have to wait for a non-pool miner to solve the block.


Edit: Of course thekidcoin found the problem while I was typing all this up

ALL: I believe I have found a few issues - thank you for sending me the error log!  The block IS being solved.  As I said before there was no way to tell this without the error logs. 

I am working on a fix (several), we will need to fork within 24 hours of its release and I will need to coordinate with all pools and BTER.

Few things I need to work out as to the exact cause, but I should have a fix tonight, with a work by tomorrow later in the day/night (central time).

ALL: I believe I have found a few issues - thank you for sending me the error log!  The block IS being solved.  As I said before there was no way to tell this without the error logs. 

I am working on a fix (several), we will need to fork within 24 hours of its release and I will need to coordinate with all pools and BTER.

Few things I need to work out as to the exact cause, but I should have a fix tonight, with a work by tomorrow later in the day/night (central time).

ALL: I believe I have found a few issues - thank you for sending me the error log!  The block IS being solved.  As I said before there was no way to tell this without the error logs. 

I am working on a fix (several), we will need to fork within 24 hours of its release and I will need to coordinate with all pools and BTER.

Few things I need to work out as to the exact cause, but I should have a fix tonight, with a work by tomorrow later in the day/night (central time).

March 17, 2014, 08:47:45 - Found after 1h 29m
Block 11352
Coinbase   02582c02700d062f503253482f
2x 545.5 output
FAvrAQn2cpYFaowSwYiJvuQrwT7PSGp4Rc
FTkUQFwLKW8mWbdks6j2p6UxDdHY49qhkx

March 17, 2014, 06:42:02 - Found after 6h 14m
Block 11303
Coinbase 02272c03fe9a00062f503253482f
2x 1340 output
F6jNAcmpdPVP4CCZWRUZXmocbj5zcjowyN
FNG4aSWm5x6Wa8tsz8hK3XJy2itQeB8fTJ

March 16, 2014, 23:09:08 - Found after 2h 3m
Block 11214
Coinbase 02cf2b0349ae00062f503253482f
2x 2051 output
FDrYFMuhDgRJjRu72EQ7aK6rsYdZMg3L94
F88MAHkFJFX1yEKnB5faMXp11EQJj1rHL5

March 16, 2014, 20:06:49 - Found after 47m
Block 11171
Coinbase   02a32b02f034062f503253482f
2x 4632 output
FQCPgk19Ayax4wg8Sjv3jeMgrmZeQYB7jD
FHPhyaH5FcN3c3csNRGxc7KYS4NQUUxUxE

March 16, 2014, 17:20:48 - Found after 1h 27m
Block 11079
Coinbase   02472b02cf3c062f503253482f
2x 1319.5 output
FBU7EV9RacSCAKmiMnsuem4WHP2u2u82nq
F79mS72WxdQjHQLpZXm2EC5hrrLc24grH3

March 16, 2014, 09:33:52 - Found after 2h 58m
Block 10870
Coinbase   02762a02737d062f503253482f
2x 2487.5 output
FBU7EV9RacSCAKmiMnsuem4WHP2u2u82nq
FJ9ihcwZ7Lcf2JuwKZ6cmoUDc3YFYxc9UC

March 15, 2014, 19:00:29 - Found after 1h 9m
Block 10436
Coinbase   02c428027e66062f503253482f
2x 2054 output
FDrYFMuhDgRJjRu72EQ7aK6rsYdZMg3L94
FJ9ihcwZ7Lcf2JuwKZ6cmoUDc3YFYxc9UC

March 15, 2014, 17:37:15 - Found after 1h 33m
Block 10406
Coinbase 02a6280390af00062f503253482f
2x 4104 output
FMf3Y9hLxsSuotSUsYqeCQyu4FQZENkGyp
FQCXJjAjEhwKgwLHyG9DxKCgLaPPz3hVAt

11648   02802d062f503253482f04f910275308100004840f0000000d2f7374726174756d506f6f6c2f   Cruncharder
11647   027f2d062f503253482f04a310275308980178fa150000000d2f7374726174756d506f6f6c2f   Bitember
11646   027e2d062f503253482f041410275308f8003861490000000d2f7374726174756d506f6f6c2f   Miningwithus
11644   027c2d062f503253482f04790f275308f800368fa50000000d2f7374726174756d506f6f6c2f   Cloudminers

ALL: I believe I have found a few issues - thank you for sending me the error log!  The block IS being solved.  As I said before there was no way to tell this without the error logs. 

I am working on a fix (several), we will need to fork within 24 hours of its release and I will need to coordinate with all pools and BTER.

Few things I need to work out as to the exact cause, but I should have a fix tonight, with a work by tomorrow later in the day/night (central time).

ALL: I believe I have found a few issues - thank you for sending me the error log!  The block IS being solved.  As I said before there was no way to tell this without the error logs. 

I am working on a fix (several), we will need to fork within 24 hours of its release and I will need to coordinate with all pools and BTER.

Few things I need to work out as to the exact cause, but I should have a fix tonight, with a work by tomorrow later in the day/night (central time).

Maybe the guys from fedoracoin (TIPS) can help?

They also had very long block times now and then but thats solved somehow

I wanted to share this, maybe this can help.

I've tried using 3 different pools (bitember, cloudminers and crunchharder) and switched over from one to another because I was having issues.

First was bitember. I turn on my miners and went to the dashboard to check on my total hash rate. When I click over to "workers", I see them active. Few minutes later (10-20 mins) I see several of my miners "Not Active" but when I check my miners, they are still hashing. Very weird. Ran it for a day long, This kept happening so I didn't see many coins, but when I check the "Pool Stats" it was saying I should of received a good amount. It was no where near that. (could of been difficulty as well)

Moved over to cloudminer and was running my miner and the same thing was happening. I see the blocks rewarded but it seems like my rig was not active during those times. Same issue. (Ran it for a day, didn't get much coins.)

Moved it over to crunchharder and I haven't had issues with my miners being NON Active. It has been hashing away for about 24 hrs and I've received a few coins, but no where near what the pool stat says. Seems the most promising but, the last autopayout I did was sent to BTER. It's been stuck saying "processing" since 2014-03-18 02:50:35. I feel like there have been no confirmation and that's why It's just stuck.

I also, purchased a few coins via BTER and sent it to my wallet but It's had ZERO confirmation and under "Unconfirmed" for about 3 hours now, maybe even longer.

Hope some of this information helps.

I stand by my point.  They are found quickly because difficulty is too low after the block is solved because difficulty adjusts.  Then hashrate skyrockets again for another cycle of this.  Again, are these miners just jumping right back on board next block?  I guess I am the only one that finds it curious that the coin worked issue free save for forking once that entire week when bitember was using 75% of the hasrate.

Well, you keep mentioning the fact there's a pool with over 50%. That should have no effect, so I don't know why you keep mentioning it.


As of the last block, net hashrate was at 2GH/s. Looking at the pools right now, there is at least 600MH/s there. Assuming that no one is solo mining (which isn't the case), that puts the absolute minimum net hashrate at 30% of what it was at the last block, and is probably much more like 60-70%. That's not enough to cause blocks to be stuck for such a long period.

So the problem is not people actively dropping their hashrate during stuck blocks. That's certain. So what other causes for dropped hashrate could there be? All I can think is with the stratum implementation - did you compile this or did one of the pool operators?


I already mentioned that a few pages back, that as soon as a stuck block is solved, several more follow immediately, and you questioned whether I knew how mining works to say such a thing, lol?

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.

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)

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.

how?