3610 | @@ -3641,7 +3611,8 @@ return RPCMethod{
3611 | data.pushKV("bits", strprintf("%08x", tip->nBits));
3612 | data.pushKV("target", GetTarget(*tip, chainman.GetConsensus().powLimit).GetHex());
3613 | data.pushKV("difficulty", GetDifficulty(*tip));
3614 | - data.pushKV("verificationprogress", chainman.GuessVerificationProgress(tip));
3615 | + data.pushKV("verificationprogress", cs.TargetBlock() ? chainman.GetBackgroundVerificationProgress(*tip)
I feel like this change better aligns the assumeutxo.md documentation (accurate monitoring)
After the snapshot has loaded, the syncing process of both the snapshot chain and the background IBD chain can be monitored with the getchainstates RPC.
2e2deb8262f2297af61b152aa7646e3cabcc4f40: rpc: report background validation progress in getchainstates
data.pushKV("verificationprogress", cs.TargetBlock().has_value() ? chainman.GetBackgroundVerificationProgress(*tip)
nit
Thanks for the review! TargetBlock() returns a const CBlockIndex* rather than a std::optional, so I don't think .has_value() would work here.
ahh, you're right. my mistake!