BIP34 requires coinbase transactions to begin with a data push of the block's height.
The coinbase transaction in block
3aa03753fc) happens to start with
OP_PUSHBYTES_3 d6441e which is the value
Is it possible for the miner of block
1983702 to use the exact same coinbase transaction from block
If so, would this be a supply inflation bug?
Or is this mitigated by BIP30?
Blocks are not allowed to contain a transaction whose identifier matches that of an earlier, not-fully-spent transaction in the same chain.
Currently that transaction is not yet fully spent, but that could change before block
If this is still a possible issue, how could it be resolved before then?