-
Notifications
You must be signed in to change notification settings - Fork 39
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
Emulator Feature: Report gas used #12
Comments
Hi 👋 I'll keep an eye on your progress and will be reviewing your code. You can comment here or find me on Discord (I'm sideninja#1970). Join the Flow Discord server if you're not there already! |
Hi
|
Hi @sideninja |
@avcdsld Your PR has been accepted and merged, since this was a task that has obvious correct implementation it has been merged. Existing PR here: onflow/flow-emulator#87 -- If you believe you have a revolutionary better idea on how to implement this you are always free to do so, but we believe this task is too small to have many other approaches. |
Good day @avcdsld! Thanks so much for all your hardwork & participation. In order to finalize winners & prepare for prize payout, we'll need the following actions from your end. Please provide the following information by Nov 17, 2021, (in this GH Issue is fine): 1. Team Information
🎖IMPORTANT: We will only proceed with prize payouts once all members have confirmed with 👍 on the post. 2. Video Demo (optional)
We will be hosting Closing Ceremonies on November 23rd, 8AM PT where we'll having closing remarks from Dete & will be announcing the winners! I'll share the details here before Nov 17. |
Hey folks, We've received and reviewed over 82 submissions! What an amazing community on Flow! To commemorate all the hard work done, we have finalized winners and will be announcing them during our Closing Ceremony on Nov 23rd, 8AM PT. Be sure to join us - there may be some attendance prizes & a keynote from our CTO, Dete 😉! RSVP here so you don't miss out! See you then! |
Description (Problem Statement)
There should be a way to see transaction gas (computation) usage.
Gas usage is not the same as transaction fees. Transaction fees are currently static, but in the future they will depend on the gas used by the transaction.
Executed transactions are currently logged like this (when in verbose mode):
The transaction executed line should also include gas usage.
To get the gas usage of the transaction, you can get started here. This field gets filled after the transaction is run. This information should be intercepted on the emulator.
Experience Required
Minimum Feature Set (Acceptance Criteria)
Software Requirements
Maintainability
Testing
Other Requirements
Documentation
Code standards or guidelines
Judging Criteria
Resources
The text was updated successfully, but these errors were encountered: