I think it will not be too difficult to fix up whatsonchain such that it returns the number of confirmations and can therefore be compatible with bitsv's Unspents dataclass.
I think 2 function calls should be acceptable for this purpose...
One to get current block height and another for the utxos --> calculate number of confirmations.
Once this is fixed we can finally add whatsonchain to main / test and stn as a second-line API for redundancy. Which I see as quite important.
I think it will not be too difficult to fix up whatsonchain such that it returns the number of confirmations and can therefore be compatible with bitsv's Unspents dataclass.
As per previous discussion...https://github.com/AustEcon/bitsv/pull/39#issuecomment-513504148
I think 2 function calls should be acceptable for this purpose... One to get current block height and another for the utxos --> calculate number of confirmations.
Once this is fixed we can finally add whatsonchain to main / test and stn as a second-line API for redundancy. Which I see as quite important.