Stratum – Configure block templates to prevent mining “empty” blocks

From my understanding, Stratum V2 can help avoid “empty” blocks (reference A, reference B) as most of the information can be distributed in advance, i.e. before the next block is mined.

To avoid confusion, I’d like to make some assumptions:

• The “next block” is the block that comes after the end of the current chain. It has not been mined yet, but will be mined soon.
• Block templates are created for the blocks that follow the “next block”.
• The template block will be named “Grandchild Block” since it is the grandchild of the current chain tip. The “next block” can then also be viewed as a “sub-block”.

I don’t know how the template for the grandchild block is calculated, i.e. what transactions it contains. In theory, the next block could contain arbitrary transactions, including transactions that conflict with whatever the new template intends to use.

Is the grandchild block template only used if the next block is found in the same pool? Once mining pool However, you must assume that if someone else discovers the next block, they will not know its contents.

Do miners create grandchild block templates that already contain “secure” transactions? For example, are transactions previously spent on time-locked outputs or transactions created directly by miners that can be considered non-conflicting?