-
Notifications
You must be signed in to change notification settings - Fork 106
dev: add a way to dynamically set the kakarot block gas limit in the hive chain binary #838
Comments
<!--- Please provide a general summary of your changes in the title above --> <!-- Give an estimate of the time you spent on this PR in terms of work days. Did you spend 0.5 days on this PR or rather 2 days? --> Time spent on this PR: 0.1 day ## Pull request type <!-- Please try to limit your pull request to one type, submit multiple pull requests if needed. --> Please check the type of change your PR introduces: - [x] Bugfix - [ ] Feature - [ ] Code style update (formatting, renaming) - [ ] Refactoring (no functional changes, no api changes) - [ ] Build related changes - [ ] Documentation content changes - [ ] Other (please describe): ## What is the current behavior? The timestamp for anvil is set to the genesis block timestamp. <!-- Please describe the current behavior that you are modifying, or link to a relevant issue. --> Resolves #NA ## What is the new behavior? Set the timestamp to the current block timestamp.
@Eikix this needs scoping |
I don't remember the context / need; are you able to scope this issue if it is still needed? |
The idea is that we don't have a way to set the gas limit in the contract dynamically, meaning it will just be fixed to a certain value, without taking into account L1 gas fluctuations. The initial idea was to have a service update this value but this was never further scoped |
What does it unlock that is currently locked? Test accuracy? Some tests fail because of it? |
No just better transaction cost on chain. If you don't do this and we charge a base fee of 1 Gwei while L1 cost is 1000Gwei, it will cause a big missprice between the Starknet cost the relayer pays on Sepolia and the actual cost which is paid to the coinbase. |
But this is for hive chain binary |
oh my bad, then is more a tracking issue then, in case we ever need to dynamically set the block gas limit in the hive tests. For now since hive tests are locked to a specific commit because of this issue, there is nothing to do. |
#833 (comment)
The text was updated successfully, but these errors were encountered: