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

[seattletu]

Wow nice job scryptographer

[duazo]

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).

Good stuff. What's the exact nature of the issue?

[organizer]

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).

Good news... we only post b/c we care.

[rusty_coin]

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).

Awesome, thanks for the hard work thekidcoin. 

[thekidcoin]

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)

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

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

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

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

thanks for the info, good stuff

Bitember actually found the block...  Without their log data I had no real leg to stand on.  Its something being interpreted wrong causing the block to be rejected (nice info too thanks I just added so many printf's to my test binary I nearly filled up my drive LOL)...

Which means likely that someone else needs to solve it.

OK OK I can't post anymore need to work on this LOL

[bullus]

Very good kidcoin.

[thekidcoin]

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).

Good stuff. What's the exact nature of the issue?

its something with how POB/POT checking is being interpreted by the pools.

Remember, before BTER most mining was solo-mining.

I had no clue it could be this because no one provided any error logs or stated their pool was seeing errors - so then we just assume its some other issue - how could anyone know without seeing the mining daemon's logs (I stated numerous times that without logs or rejects mining the chain is fine).

Trying still determine the calculation that is off, then I will get a fix built today sometime and binaries released.  Its not POB/POT itself, but the block checking thats screwing up somehow.

[organizer]

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).

Good stuff. What's the exact nature of the issue?

its something with how POB/POT checking is being interpreted by the pools.

Remember, before BTER most mining was solo-mining.

I had no clue it could be this because no one provided any error logs or stated their pool was seeing errors - so then we just assume its some other issue - how could anyone know without seeing the mining daemon's logs (I stated numerous times that without logs or rejects mining the chain is fine).

Trying still determine the calculation that is off, then I will get a fix built today sometime and binaries released.  Its not POB/POT itself, but the block checking thats screwing up somehow.

I know i'm not a programmer, but I will say I did think the problem was in some of the innovations!

Anyways, some pre-fork questions:

- To get the coin moving again, should we throw hash power on pools that aren't Bitember to re-solve it?
- What will happen to coins in mid transfer.... I have a transaction in progress...what happens if the fork comes before all necessary confirms?

[bullus]

Will the net-hashrate also be right again, after the fix or was it already right?

[moonpool]

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).

Good stuff. What's the exact nature of the issue?

its something with how POB/POT checking is being interpreted by the pools.

Remember, before BTER most mining was solo-mining.

I had no clue it could be this because no one provided any error logs or stated their pool was seeing errors - so then we just assume its some other issue - how could anyone know without seeing the mining daemon's logs (I stated numerous times that without logs or rejects mining the chain is fine).

Trying still determine the calculation that is off, then I will get a fix built today sometime and binaries released.  Its not POB/POT itself, but the block checking thats screwing up somehow.

The error that keeps happening on my pool over at flutter.miningwith.us :

ThreadRPCServer method=submitblock
ERROR: CheckCoinbaseTx() : calculated coinbase, desination, or address do not match the actual block at height 11649
InvalidChainFound: invalid block=0000000001afdd00a420  height=11649  trust=155052  blocktrust=124  date=03/17/14 21:02:49
InvalidChainFound:  current best=00000000022bebb5fd28  height=11648  trust=154928  blocktrust=123  date=03/17/14 15:12:57
ERROR: SetBestChain() : SetBestChainInner failed
ERROR: AcceptBlock() : AddToBlockIndex failed
ERROR: ProcessBlock() : AcceptBlock FAILED

[CrunchHarder]

OP, just sent you a message re: checking the logs, please confirm I've checked the correct ones, drop me a PM and let me know.


https://flt.crunchharder.net

https://crunchharder.net/images/logo-sm.jpg

Peace of mind FlutterCoin mining with CrunchHarder:

*UK-Based Pool
*High End Dedicated Servers
*Fully Redundant, Fault-Tolerant Architecture
*Automatic Backup of Wallets and Databases
*Technical Support from Experienced Coin Devs and Pool Owners
*Dedicated Support Ticketing System
*4096 Bit SSL Security with SHA256

https://flt.crunchharder.net

[seattletu]

Well done crunchharder.net and miningwith.us for providing the log info.

[Trujillo]

Thank you Fluttercoin community for collaborating to help solve this issue! If any of you are interested in joining the FLT Community Development Team please contact me by DM if you have not already. We already have completed some of our first few projects and next is our website, Fluttercoin.info which should be releasing quite soon.

[niothor]

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)

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

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

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

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

Well , you did put some work in it , it deserves to be praised.

[thekidcoin]

lol that was loooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo ooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong

[seattletu]

And now the blocks will start mining really fast.

Kidcoin is there any hint as to what finally gets the next block to start going again?

[thekidcoin]

And now the blocks will start mining really fast.

Kidcoin is there any hint as to what finally gets the next block to start going again?

Exactly?  no generally? yes.  They are passing the block checking routine while the others aren't.  Why is a great question.  few pools reported it, but provided no actual found block data.

I know how to stop it, but there will need to later updates following to finalize some things when there is more data gathered.

Getting ready with final testing then will start to build binaries and contact bter (will track down pools too some already know to look out)

anyone know WHO found the block??

[thekidcoin]

also FYI this block will be stuck too LOL how long is anyone's guess

[organizer]

If you fork the coin, can you explain what might happen to transactions that are still in progress?

[seattletu]

also FYI this block will be stuck too LOL how long is anyone's guess

That one was fast