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

allow padding of GAS / specifying GAS amount for invoke TX #196

Open
ixje opened this issue May 17, 2023 · 1 comment
Open

allow padding of GAS / specifying GAS amount for invoke TX #196

ixje opened this issue May 17, 2023 · 1 comment

Comments

@ixje
Copy link

ixje commented May 17, 2023

There are use-cases in which you would like to attach more GAS than required to just execute the main code path or exactly specify the attached GAS. This can be for example to allow the contract to burn the remaining GAS to the benefit of the NEO community (here is an example of such a contract that does this), or simply to debug insufficient GAS scenario's.

At this time all invocations seem to default to 20 GAS (as defined by TestModeGas)

: base(TriggerType.Application, container, new SnapshotCache(checkpointStore), persistingBlock, settings, TestModeGas, witnessChecker)

@ixje
Copy link
Author

ixje commented Jun 20, 2023

Another real use-case is when you want to test/debug the fixing of storage on a contract and the cost of that exceeds 20 GAS.

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

No branches or pull requests

1 participant