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
The latest version of btcd master broke an existing API, by taking a value that was a bool and making it an int (or the other way around). Similar to what we've done in the past w.r.t probing to see which versions are supported, we also need to patch in this change. Ideally we can prevent things like this on the btcd end, by just adding the new field if possible under a distinct name. The call in question is GetBlockVerboseTx: btcsuite/btcd#1529
The text was updated successfully, but these errors were encountered:
The latest version of
btcd
master broke an existing API, by taking a value that was a bool and making it an int (or the other way around). Similar to what we've done in the past w.r.t probing to see which versions are supported, we also need to patch in this change. Ideally we can prevent things like this on thebtcd
end, by just adding the new field if possible under a distinct name. The call in question isGetBlockVerboseTx
: btcsuite/btcd#1529The text was updated successfully, but these errors were encountered: