add: tag for extra transactions that would have been a good fit for the block; but we didn't know about

[0xB10C]

No description provided.

[joostjager]

Do you mean transactions that showed up in a mined block that in retrospect would have been included in the template?

[0xB10C]

Yes, for example, these three transactions right after the coinbase transaction in this AntPool block: https://miningpool.observer/template-and-block/000000000000000000006b45497499ba62079e4525a12ceda27f1b39b68697b5

If they would have been in my mempool at the time of building the template, my node would probably have included them. They were good candidates (in this case a good candidate-package).

[joostjager]

I think including them in the template would be valuable. It shows what the miner could have earned in fees given publicly available transactions and anything relayed to them in private.

But technically, I suppose it is difficult? You are using core's getblocktemplate, so when the block comes in, the template will change immediately and there is no opportunity anymore to see what the mempool would've looked like if the block txes were already known.