recently I noticed some inaccuracies on some diagrams that I added to the spec
Mining Protocol
On the current Extended Extranonce Layers diagram, we're implying that Extended Extranonces are allocated across Group Channels, which is not true.
Group Channels have no Extranonce Prefix.
Job Declaration Protocol
On the current message flow diagram of Full-Template mode, we're implying that JDC only sends a RequestTransactionData to TP if JDS sends a ProvideMissingTransactions (in a process we're calling "potential template verification").
That's not true.
NewTemplate only contains a merkle_path, which is not sufficient information for JDC to craft DeclareMiningJob.tx_ids_list.
Therefore, JDC needs to send RequestTransactionData after each NewTemplate.
recently I noticed some inaccuracies on some diagrams that I added to the spec
Mining Protocol
On the current Extended Extranonce Layers diagram, we're implying that Extended Extranonces are allocated across Group Channels, which is not true.
Group Channels have no Extranonce Prefix.
Job Declaration Protocol
On the current message flow diagram of Full-Template mode, we're implying that JDC only sends a
RequestTransactionDatato TP if JDS sends aProvideMissingTransactions(in a process we're calling "potential template verification").That's not true.
NewTemplateonly contains amerkle_path, which is not sufficient information for JDC to craftDeclareMiningJob.tx_ids_list.Therefore, JDC needs to send
RequestTransactionDataafter eachNewTemplate.