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

Adding new topic for gas in Sui #10245

Merged
merged 19 commits into from
Apr 5, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update gas-in-sui.md
  • Loading branch information
econmysten authored Apr 3, 2023
commit da549dadf1f4d1ccefac59729f085efc90ac3ae6
5 changes: 0 additions & 5 deletions doc/src/learn/tokenomics/gas-in-sui.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,11 +45,6 @@ Using coarse bucketing accomplishes two important goals:
| 1,000,001 | 5,000,000 | 5,000,000 |
| 5,000,001 | Infinity | transaction will abort |

Coarse bucketing has important benefits relative to more fine grained gas schedules in that it accomplishes two important goals:

- Frees developers from optimizing their smart contracts to deliver marginal gains in gas costs via "gas golfing" – instead, can focus on step-function improvements in their products and services.
- Gives Sui protocol developers the freedom to adjust per-instruction gas costs and experiment with new gas metering schemes without creating significant disruption for builders. We expect this will happen frequently, so it's important that builders do not rely on per-instruction gas costs remaining stable over time.

**Storage Units**

Similarly, Sui transactions vary depending on the amount of new data written into on-chain storage. The variable Storage Units captures these difference by mapping the amount of bytes held in storage into storage units. Sui’s current schedule is linear and maps each byte into 100 storage units. So, for example, a transaction that stores 25 bytes will cost 2500 Storage Units while a transaction that stores 75 bytes will cost 7500 units.
Expand Down