Skip to content

Typo key chance -> key change in L1 Scaling post #126

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.

Sign up for GitHub

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

Open
JoshOrndorff wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Typo key chance -> key change in L1 Scaling post #126

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eb0e019
typo `key chance` -> `key change` in l1scaling.md
JoshOrndorff Feb 14, 2025
ddee6fc
Typo `but` -> `by` in l1scaling.md
JoshOrndorff Feb 14, 2025
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
2 changes: 1 addition & 1 deletion posts/l1scaling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,7 @@ If we give ourselves the goal of eg. bringing [Polymarket](https://polymarket.co

Suppose that each user needs to do a key change or account upgrade operation once a year, and we have 3.1 billion users. If each operation costs 50,000 gas, then we get a gas consumption per slot of `50000 * 3100000000 / (31556926 / 12) ~= 59 million` , about 3.3x the current target.

We _could_ optimize very hard, but making key chance operations _initiated_ on L2, but _stored_ on L1 (credit [the Scroll team](https://scroll.io/blog/towards-the-wallet-endgame-with-keystore) for this idea). This would reduce gas consumption to potentially a storage write and a little more (let’s once again say 7500 gas), which would allow keystore updates to be made with about half of Ethereum’s current gas capacity.
We _could_ optimize very hard, by making key change operations _initiated_ on L2, but _stored_ on L1 (credit [the Scroll team](https://scroll.io/blog/towards-the-wallet-endgame-with-keystore) for this idea). This would reduce gas consumption to potentially a storage write and a little more (let’s once again say 7500 gas), which would allow keystore updates to be made with about half of Ethereum’s current gas capacity.

We can also estimate the cost of a keystore operation:

Expand Down