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

feature: Specify why a transaction did not pass consensus validation #8961

Open
mpguerra opened this issue Oct 23, 2024 · 0 comments
Open

feature: Specify why a transaction did not pass consensus validation #8961

mpguerra opened this issue Oct 23, 2024 · 0 comments
Labels
C-enhancement Category: This is an improvement I-usability Zebra is hard to understand or use S-needs-triage Status: A bug report needs triage

Comments

@mpguerra
Copy link
Contributor

Motivation

It would be useful to understand why exactly a transaction might not pass consensus validation.

It can be confusing to users to not know this: https://discord.com/channels/809218587167293450/809251029673312267/1298396993273597992

Specifications

Zebra should expose the underlying reason to the user in the logs:

pub enum TransactionError {

Complex Code or Requirements

No response

Testing

No response

Related Work

No response

@mpguerra mpguerra added C-enhancement Category: This is an improvement I-usability Zebra is hard to understand or use S-needs-triage Status: A bug report needs triage labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Category: This is an improvement I-usability Zebra is hard to understand or use S-needs-triage Status: A bug report needs triage
Projects
Status: New
Development

No branches or pull requests

1 participant