-
Notifications
You must be signed in to change notification settings - Fork 232
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
one big risk that tx result from omnicore rpc is different from omniexplorer.info #1255
Comments
@kiddx01 from your local node can you provide the output of can you also please provide the output of |
Hello @kiddx01, thanks a lot for reporting! Can you please restart Omni Core with Please let me know, how it went. |
|
thank i will have a try . |
@kiddx01 make sure to provide the consensushash output before restarting |
omnicore/bin/omnicore-cli -datadir=/data/data -conf=/data/data/omnicore.conf omni_getcurrentconsensushash |
@kiddx01 thanks, please proceed with Dexx's recommendation next and report back after. Also can you provide a little more detail about your setup. if you can, also save a copy of your omnicore.log and debug.log from the data directory before restarting and attach them here if possible |
2022-05-18T00:11:07Z init message: Still scanning.. at block 548102 of 736810. I'm surprised. It's getting longer and longer.
|
Hi @kiddx01, the update takes a long time, however, I would recommend using the latest version of Omni Core. |
using version:
omnicore-0.11.0
tx: 9633206b86437bdedbc0efa8aef39887c1666a92d14e6f75b6af02991d18cf2e
query from rpc:
result:
query from omniexplorer:
result:
please check the key: "valid"
now i found actual the tx is fail . so why node rpc tell me the tx is valid ?
The text was updated successfully, but these errors were encountered: