digest verify chain information does not provide enough relevant block details

[jrick]

It only provides the timestamp encoded in the block header and the total number of confirmations.

The confirmation count is completely useless because it can change at any point and different nodes can different views of the current best chain.

The timestamp encoded in the block header is moderately useful, but securely verifying the accuracy requires cross checking this against a trusted/local dcrd instance, and doing so would require the block header or hash to query the block. (This cross checking is also required to verify that the block really does contain the anchor transaction.)

The API should instead include the block hash which mines the anchor at a minimum, and probably the block height as well.

While the block could be looked up by the anchor tx hash, this requires tx indexing and is not enabled by default by dcrd.

[amass01]

will work on this next, will add block hash and height