Node 8 'tx' endpoint doesn't return the number of confirmations about bitcore-node HOT 3 CLOSED

The confirmations is a derived value from localChainTip.height-tx.height

I believe we may be doing that in insight.

from bitcore-node.

Yeah that's true, but I think it would be faster and more convenient if the tx API endpoint returns the confirmations.

If the API user needs to derive the confirmations, the user will need to make two API calls per transaction (one to get the current chain tip, and another to get the tx.height) to calculate the confirmations, instead of only one if the API provides it.

All the node has to do is to locally compute the confirmations when a transaction is requested by the API (or multiple transactions.) Hence, not increasing the storage, but slightly impacting the response time (not by a lot compared to the user making two API calls to compute the same value).

from bitcore-node.

Fixed, check bitpay/bitcore#1692

from bitcore-node.