Skip to content
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

bisq-statsnode fails to dump JSON for a valid BSQ transaction #6165

Closed
wiz opened this issue Apr 26, 2022 · 4 comments
Closed

bisq-statsnode fails to dump JSON for a valid BSQ transaction #6165

wiz opened this issue Apr 26, 2022 · 4 comments

Comments

@wiz
Copy link
Member

wiz commented Apr 26, 2022

I created a compensation request proposal DAO transaction and it was mined into a block.
However, bisq-statsnode does not create a <txid>.json file for this transaction. This causes the following issue:

Layer 1: https://mempool.space/tx/e92376b61e76dc59961b9d570cc6700603c37c1a58ff5330847782db5a949b47
Layer 2: https://bisq.markets/tx/e92376b61e76dc59961b9d570cc6700603c37c1a58ff5330847782db5a949b47

The comp req TX is valid on other bisq nodes, so I'm not sure why this TX fails to appear on my bisq-statsnode instances.
I am running v1.8.4 - any idea?

@Emzy
Copy link
Contributor

Emzy commented Apr 26, 2022

For what it's worth the transaction shows up on my explorer:

Layer 2: https://bisq.mempool.emzy.de/tx/e92376b61e76dc59961b9d570cc6700603c37c1a58ff5330847782db5a949b47

@wiz
Copy link
Member Author

wiz commented May 2, 2022

@chimp1984 was this the issue you said was caused by the state getting out of sync between DAO and JSON objects?

@github-actions
Copy link

github-actions bot commented Sep 5, 2023

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions
Copy link

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants