You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using bitcore == 2.0.0, insight-api == 0.3.1 and bitcore-node == 1.0.1, I am unable to get the spending txid for a P2SH address. In all of the following calls, the address to keep track of is 3MeZDtTzXmrGxxRgcs51CJdbeUesPHnNkd.
This should be resolved in bitcore@4.0.0 (with insight-api@0.4.0 and bitcore-node@3.0.0). In summary, the spent info is now indexed based on the address of the previous output script instead of determining the address from the input script which only works in standard p2sh cases. Indexes are now a part of bitcoin itself, see: https://github.com/bitpay/bitcoin/tree/0.12-bitcore
Using
bitcore == 2.0.0
,insight-api == 0.3.1
andbitcore-node == 1.0.1
, I am unable to get the spending txid for a P2SH address. In all of the following calls, the address to keep track of is3MeZDtTzXmrGxxRgcs51CJdbeUesPHnNkd
.Similarly, if I look up transactions for the address in question, I only see the funding transaction:
However, insight clearly knows about the spending txn:
What's interesting is that it seems older versions of the insight-api (at least that running on https://insight.bitpay.com) do get it correct:
For completeness:
Is there some sort of bug in newer versions preventing P2SH addresses from being correctly indexed?
The text was updated successfully, but these errors were encountered: