-
Notifications
You must be signed in to change notification settings - Fork 137
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
[Proposal] Increase min gas price #92
Comments
The reasoning behind block cost in NEAR being too low is not clear. Isn't it our intention to have low fees, what is the reason for increasing it? We should compute the lower bound on storage cost, but deriving the cost of maintaining EC on AWS for one year and use our inflation rate to connect it with NEAR. If the proposed storage fee is lower than that then we cannot decrease it. |
@ilblackdragon then you are assuming that 1 shard = 100 TB storage, which seems ridiculous. |
I don't have strong preference for storage (naturally most of NEAR will not be used for storage, and attempting to obuse it will be pretty expensive). For gas fees an insight into why you want to change it would be helpful :) |
Do you have comparable numbers for AWS on one side and ETH on the other for both storage and tx's for reference? Can't find the post and the economics blog doesn't have hard numbers. |
Current prices are 40-70 GWei Ethereum:
One major point is that contracts on Ethereum are only max 24KB with usually way smaller. Our contracts average at 300kb and sometimes go to 1MB. Our simple transfer: 446 Ggas. Current gas price is 100,000 yN -> 0.0000000446 N (https://explorer.near.org/transactions/AbVHgMH85zTVKZGNY2VhG55apWhVMdbMrC8YbB4M1ibk) Reasoning for min gas price increase is mostly around few things:
|
Re: gas prices, agree with all the points except "We can always decrease but won't be able to increase it later IMO", I don't think there's anything specific that prevents us from later bumping the minimum gas price. This sounds like a very strong reason in support of this idea:
Storage should be extracted into a separate issue, so that we can discuss each issue separately. |
We can indeed increase if we are ok with some applications breaking. |
What happens if the gas price increases to that level organically via usage? |
@SkidanovAlex aren't we always pre-charging according to max price and then refunding (after #67)? Maybe I'm misunderstanding how that works though. |
@vgrichina it is not according to max price but rather some pessimistic gas price computed from current gas price. |
Update gas price to 1_000_000_000 according to near/NEPs#92. Test plan --------- * `upgradable.py` with transactions. * spin up a node with this change and verify that it can sync to testnet and process blocks without any issue.
After near/NEPs#92, the min gas price was set to 100M yoctoNEAR. But the genesis file we get from the state viewer dump-state command copies the 1B min gas price from the genesis file. This results in a network with 10x the gas fees as mainnet when we launch mocknet testing networks, and many transactions sent by the mirror run command fail with too little balance. So this PR allows setting the min/max gas prices in the mocknet genesis file so we can fix that. It might also be worth changing the behavior of `view-state dump-state` to set the min gas price, but this will work for now and lets us get the right gas price in all cases
After near/NEPs#92, the min gas price was set to 100M yoctoNEAR. But the genesis file we get from the state viewer dump-state command copies the 1B min gas price from the genesis file. This results in a network with 10x the gas fees as mainnet when we launch mocknet testing networks, and many transactions sent by the mirror run command fail with too little balance. So this PR allows setting the min/max gas prices in the mocknet genesis file so we can fix that. It might also be worth changing the behavior of `view-state dump-state` to set the min gas price, but this will work for now and lets us get the right gas price in all cases
After near/NEPs#92, the min gas price was set to 100M yoctoNEAR. But the genesis file we get from the state viewer dump-state command copies the 1B min gas price from the genesis file. This results in a network with 10x the gas fees as mainnet when we launch mocknet testing networks, and many transactions sent by the mirror run command fail with too little balance. So this PR allows setting the min/max gas prices in the mocknet genesis file so we can fix that. It might also be worth changing the behavior of `view-state dump-state` to set the min gas price, but this will work for now and lets us get the right gas price in all cases
After near/NEPs#92, the min gas price was set to 100M yoctoNEAR. But the genesis file we get from the state viewer dump-state command copies the 1B min gas price from the genesis file. This results in a network with 10x the gas fees as mainnet when we launch mocknet testing networks, and many transactions sent by the mirror run command fail with too little balance. So this PR allows setting the min/max gas prices in the mocknet genesis file so we can fix that. It might also be worth changing the behavior of `view-state dump-state` to set the min gas price, but this will work for now and lets us get the right gas price in all cases
Currently:
The suggestion to:
Reasoning: storage right now ends up being very expensive for contracts like multsig and we want to reduce it to manageable. Tx fees are way too low at this point and we should leave more room to reduce it later.
The text was updated successfully, but these errors were encountered: