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

bug: sendrawtransaction discrepancy #9056

Open
4 tasks
conradoplg opened this issue Nov 23, 2024 · 3 comments
Open
4 tasks

bug: sendrawtransaction discrepancy #9056

conradoplg opened this issue Nov 23, 2024 · 3 comments
Labels
C-bug Category: This is a bug S-needs-triage Status: A bug report needs triage

Comments

@conradoplg
Copy link
Collaborator

What happened?

I expected to see this happen: Ywallet hasn't updated its consensus branch ID. When submitting a tx via sendrawtransaction, zcashd returns

error code: -26
error message:
16: bad-tx-consensus-branch-id-mismatch

Instead, this happened: zebra returned a transaction ID. However, later calls to getrawmempool did not list that txid. Trying to submit the tx again returns

error code: 0
error message:
any transaction with the same effects will be rejected from the mempool until the next chain tip block

Look into it to check if it's just an error handling issue or if there is any bigger issue there.

(TODO: check my logs to see if there are more details)

What were you doing when the issue happened?

No response

Zebra logs

No response

Zebra Version

No response

Which operating systems does the issue happen on?

  • Linux
  • macOS
  • Windows
  • Other OS

OS details

No response

Additional information

No response

@conradoplg conradoplg added C-bug Category: This is a bug S-needs-triage Status: A bug report needs triage labels Nov 23, 2024
@github-project-automation github-project-automation bot moved this to New in Zebra Nov 23, 2024
@mpguerra mpguerra moved this from New to Sprint Backlog in Zebra Dec 2, 2024
@mpguerra
Copy link
Contributor

mpguerra commented Dec 2, 2024

Related to #9063 Need to check that this is still happening after it merges

@mpguerra
Copy link
Contributor

@conradoplg is it possible to test this now that #9064 is closed? Otherwise, if you can confirm that this is the same issue, we can close this one also

@conradoplg
Copy link
Collaborator Author

I didn't manage to test this today, but I'm pretty sure it was fixed by #9064. I think we can close this, but I can test it later if you prefer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug S-needs-triage Status: A bug report needs triage
Projects
Status: Sprint Backlog
Development

No branches or pull requests

2 participants