-
Notifications
You must be signed in to change notification settings - Fork 124
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle bitcoin core 220 rpc output change #57
Conversation
read "address" instead of "addresses" as core 22.0 changes the rpc output data structure.
keep 'multisig' type and make the address as nonstandard address
@medvedev1088 can you help review? We verified the code change on bitcoin core 22.0. It works as expected. |
Thank you, It would be ideal if this PR included unit tests. It seems like it should be possible to make it backward compatible by checking the addresses field first, and if it's empty, checking the address field. Is my understanding correct? |
@medvedev1088 I will take a look on the backward compatibility and update the PR. |
@veronicavero will this merge help to resolve the 'nonstandard' address type issue? Let me know if we (team of crypto analysts and developers) can assist in any way to escalate this merge. |
We tested with aforementioned changes and its working. Below attached the JSON response for a Before
After
|
re-appended more fixes for taproot from upstream (rather merged) PR blockchain-etl#57
This PR along with #59 has been deployed to |
it works for bitcoin core 22.0. It does not support backward compatibility for bitcoin core prior to core 22.0.
We can either use bitcoin version to support backward compatibility.