The full output with tx data is here:
block.txtThis only contains transaction hashes no the full tx data that is needed to verify the block manually and see what the problem is.
Is this something I can extract from my node, and if so, can you tell me how, and I'd be happy to post anything that helps?
I checked a couple of transactions in the block, the first being coinbase is obviously not found anywhere else but also the second transaction is not found either.
Yes, some of the transactions I looked for are missing, but the few I found did come back as being confirmed in the real block
784121, such as these randoms transactions (
1) (
2) (
3) I selected.
P.S. I noticed something in the previous block's coinbase transaction, the signature script contains the word "F2Pool" in it. Could it be the F2Pool that messed up or is it someone else using that name?
If we had the full block of this new one we could speculate if this is from the same miner/pool.
It's curious that it's happened more than once over the previous days. If indeed this is a configuration error, which seems likely, someone is losing a fair amount of mining rewards I think. I wonder, would it be possible for a competing miner to capture these blocks and insert their own (valid) transactions in place for broadcast? Maybe a dumb question, lol. In my log there were several minutes seperation from valid blocks on either side on the bogus block.
What would be the goal or take away from a malicious node broadcasting these intentionally?