-
Notifications
You must be signed in to change notification settings - Fork 206
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
Constructed transaction does not parse correctly #1119
Comments
getting this error for other CP API transactions as well API REQUEST
API Response
The error message has an address (1GzasG2hy7Zaad5SvM5pFWpg6wbfqXqJxJ) which is entirely not related to the original transaction... perhaps this is an internal issue with getting results from addrindexrs in counterparty? Have Javier look into it a bit deeper |
We're still running into this, I think:
|
able to reproduce the issue/error consistently on testnet via the following request. TESTNET
|
Fixed with #1647
|
It seems that we have an issue with transferring asset ownership to segwit (bech32) addresses, as the API throws an error indicating that the constructed transaction does not parse properly.
API Request:
API Response:
The text was updated successfully, but these errors were encountered: