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

chore: Expose tokens_burnt #168

Merged
merged 1 commit into from
Jul 20, 2022
Merged

Conversation

ChaoticTempest
Copy link
Member

Expose tokens_burnt field in ExecutionOutcome

Comment on lines 88 to 94
logs: Vec::new(),
receipt_ids: Vec::new(),
gas_burnt: 0,
tokens_burnt: 0,
executor_id: "testnet".parse()?,
status: ExecutionStatusView::SuccessValue(String::new()),
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wait, I'm so confused. Why are we even adding in a blank execution outcome here? Seems like a footgun

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yup, certainly not ideal. This was just mocked out at the time to get testnet going, but let's revisit it in a future issue/PR since it's going to require finding the actual transaction details themselves which the Helper Contract AFAIK does not provide additional details for when creating an account

@ChaoticTempest
Copy link
Member Author

@austinabell any other concerns for this one? Trying to get a release soon, and this will be nice to have in there as well

@ChaoticTempest ChaoticTempest merged commit e96ff0f into main Jul 20, 2022
@ChaoticTempest ChaoticTempest deleted the chore/expose-tokens-burnt branch July 20, 2022 01:32
@frol frol mentioned this pull request Oct 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants