You know the historical block header that a private tx references? It's always cumbersome to describe it. We should give it a name. Something like:
reference_block_header (and reference_block)
anchor_block_header (and anchor block and anchor_archive_tree_root etc etc). <-- I like this one best, because "reference" is still ambiguous, because a private tx is still able to "refer" to multiple blocks.
So... Please can we agree to universally adopt the term "anchor block"?
We can then update a lot of names which have caused confusion for people.
E.g. context.historical_header -> context.anchor_block_header
E.g. context.get_block_header() -> context.get_anchor_block_header()
E.g. all over the place in the kernel circuits.
You know the historical block header that a private tx references? It's always cumbersome to describe it. We should give it a name. Something like:
reference_block_header(andreference_block)anchor_block_header(andanchor blockandanchor_archive_tree_rootetc etc). <-- I like this one best, because "reference" is still ambiguous, because a private tx is still able to "refer" to multiple blocks.So... Please can we agree to universally adopt the term "anchor block"?
We can then update a lot of names which have caused confusion for people.
E.g.
context.historical_header->context.anchor_block_headerE.g.
context.get_block_header()->context.get_anchor_block_header()E.g. all over the place in the kernel circuits.