For each UTXO notification batch, pass virtual blue score at the time (should be named accepting_blue_score_upper_bound). This should propagate through notifications and RPC layers. Wallets should use this upper bound to compute a lower bound to the number of confirmations (with sink_blue_score - accepting_blue_score_upper_bound, since it is <= sink_blue_score - actual_accepting_blue_score_for_specific_entry)
Note that the expression sink_blue_score - accepting_blue_score_upper_bound might be negative which means zero confirmations
For each UTXO notification batch, pass virtual blue score at the time (should be named
accepting_blue_score_upper_bound). This should propagate through notifications and RPC layers. Wallets should use this upper bound to compute a lower bound to the number of confirmations (withsink_blue_score - accepting_blue_score_upper_bound, since it is<= sink_blue_score - actual_accepting_blue_score_for_specific_entry)Note that the expression
sink_blue_score - accepting_blue_score_upper_boundmight be negative which means zero confirmations