-
Notifications
You must be signed in to change notification settings - Fork 127
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
tx responses can not be deserialized #2905
Comments
Additionally, attempting to retrieve the raw transaction using old transaction hashes results in a |
I debugged recent Iris releases and can confirm that this issue started with v2.1.0-rc0 release. Everything works smoothly with the v2.0.3 release. |
@onur-ozkan Sorry, I cannot reproduce this problem, the transaction [5BBF9D0C95765675281921789AD973CA480799ED4B44EEBD43D75FDEAF246053] no longer exists in nyancat testnet. If you still have questions later, please continue to add the content of the question. |
How does it appear in the explorers? Also, my main question was this:
|
Tx broadcasting is currently failing most likely due to the last release, resulting in a deserialization error.
In komodo-defi-proxy, we have implemented the Cosmos protocol which also supports IRIS (including HTLCs). However, we are encountering difficulties in broadcasting SEND and HTLC transactions. While we can still broadcast them to the network, it appears that IRIS nodes are now providing a different response compared to before that leads to deserialization errors.
Our tests and transaction functionalities had been functioning smoothly for almost 2 years, but suddenly we began experiencing deserialization errors. Has there been any intentional change in the response formats from IRIS nodes (specially in the last release)?
Error:
Sample dump of the returned data from SEND tx broadcast that fails with deserialization:
The text was updated successfully, but these errors were encountered: