-
Notifications
You must be signed in to change notification settings - Fork 9
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
Compatibility with Oasis Core 21.2 #211
Comments
The current version of the Rosetta gateway (v1.1.1) has only been tested with Oasis Core 21.1.x. Can you reproduce the issue with that version? |
There is no problem with oasis core 21.1. X |
There are also many block problems, 3610570 is just one of them |
This is expected due to some breaking event changes in Oasis Core 21.2. As mentioned, Rosetta gateway v1.1.1 targets Oasis Core 21.1 and if you need to use Rosetta, you should currently use Oasis Core 21.1 until a new version of the Rosetta gateway is released. We'll use this issue to track the necessary changes. |
Actually what you describe may be caused by the issue fixed in oasisprotocol/oasis-core#4033. The fix is planned to be released as part of Oasis Core 21.2.2, but will require a node re-sync from scratch since the problematic events have been incorrectly stored. |
I used oasis core 21.2.7 and resynchronized the nodes But there will be problems. Can I only use 21.1.X? |
@lougon, the latest |
Oasis Core Rosetta Gateway 1.2.0 has been released. |
use oasis_core 21.2 version
oasis-core-rosetta-gateway 1.1.1
rpc:block
block:3610570
post body
{
"network_identifier": {
"blockchain": "Oasis",
"network": "53852332637bacb61b91b6411ab4095168ba02a50be4c3f82448438826f23898"
},
"block_identifier": {
"index": 3610570
}
}
Returned result
{
"code": 14,
"message": "unable to get transactions",
"retriable": true
}
The text was updated successfully, but these errors were encountered: