Ratimon
commented
1 year ago Hi, I have a project idea to propose to the ecosystem.
It would be great if you guys have some feedback from developer perspective. Do you think it will be useful? Will you use it? What’s missing for you to use it?. Here is the full detail
Project Proposal
Title: a cli that goes along with building blocks of smart contract and front-end snippets to reduce L2 gas cost by encoding calldata for DApp development to use fewer bytes of calldata as much as possible.
Contribution Category: 🔴 Ecosystem Project Ideas
Tags: Devs Tool , Contracts
Estimated Effort: Large
Estimated Impact: Large
Summary
Gas optimization on layer 2 requires different paradigm and design from layer 1. The execution of layer 2 is brought out of Ethereum layer, so that the most part of total gas cost is batch submission to layer 1. In other words, either the fewer bytes of call data sent or the tighter packed call data, the lower gas users will pay on layer 2.
However, this paradigm is quite new and there is no standard to adopt this seriously. In order to push forward the cutting edge of crypto scalability even more, new design and paradigm should be standardized.
Potential Features
- Current Milestone:
- Wrapper snippet to encode the data, This can encode various input arguments into single tightly compressed calldata, There are two options to implements these:
- This can be encode off-chain by written in typescript, published as npm package.
- This can be encode on-chain by written in solidity, with read-only function. Together with another front-end wrapper, the appropriate compressed calldata can be forward to decode in later step.
- Solidity Helper Library to decode the encoded call data on chain
- AddressTable to store the mapping between addresses and indexes, allowing:
- The address can be registered to the contract, then the index is generated.
- The generated id can then be used to look up the registered address during the compressed call data decoding process
- Data Serialization
- The encoded calldata could be deserialized into the correct type. For example, if we choose to reduce the calldata by sending the time period as arguments with type of uint40 (5 bytes) instead of uint256, the calldata should be sliced at the correct offset and the result can be correctly used in the next steps.
- AddressTable to store the mapping between addresses and indexes, allowing:
- Test suites and measurements how much gas is saved
- Technical Writing/ Examples to integrate with popular front-end libraries & frameworks (eg. ether.js, viem, wagmi)
- Wrapper snippet to encode the data, This can encode various input arguments into single tightly compressed calldata, There are two options to implements these:
Impact
- On layer 1, calldata optimization is not impactful, as the gas costs to decode the calldata is costly. However, it save a tons of gas on layer 2 where calldata is expensive while computation is cheaper.
- Standardization and practice on calldata optimization paradigm is important to ensure security in web3 development on layer 2. This optimisation practice will be still relevant, even after EIP4844.
- Metrics to Measure Impact
- Number of code repo forks
- Number of external contributors’ issues and PRs submitted
- Number of npm package downloaded
Resources
- Me ( Rati Montreewat, Smart Contract Developer)
- Audit resources
Sergogogogo
tishinatyt
amirhabibzadeh
Surfacing new ideas
The power of the Optimism Ecosystem Contributions Dashboard is in its ability to surface potentially valuable tasks from all over the Optimism Collective ecosystem. As the Collective becomes increasingly decentralized, it'll be important to create a system that allows anyone to highlight new contribution opportunities that might be valuable.
We created this dashboard as a stepping stone towards a more decentralized system. GitHub isn't ideal for a free-for-all system because its limited filtering capabilities could potentially drown out high-quality projects. We have a top-priority project in works to move this dashboard to a standalone interface that would make entirely permissionless project proposals easy. We expect this interface to be live within the next 1-2 months.
We would still love to surface your project ideas and contribution opportunities within this dashboard. While we wait for the standalone dashboard interface, we'll be using this GitHub issue as the staging ground for new project proposals. If you have an idea of a task that someone could take on to improve the Optimism and Ethereum ecosystems, please feel free to drop that idea here.
Ideal project proposals
The ideal proposal is well-defined, highly detailed, and clearly impactful. A potential contributor should be able to easily understand the proposed task and start work with the resources that you've provided. Contributors should also be able to understand why the project is important and the potential impact that the project might have.
Proposed projects should generally positively impact the Optimism and Ethereum ecosystems, but this is a loose definition. Some projects might clearly benefit the ecosystem as a whole (see 🔴 Ecosystem Project Idea: List of Crypto Legal Public Goods) but projects can also be proposed that help specific efforts within the Optimism ecosystem. For example, an application deployed to OP Mainnet may wish to propose that users review the user experience of their application.
When in doubt, propose! If specific aspects of a proposed project are confusing or may not be perfectly appropriate for this dashboard, someone will help you make modifications.
Using the proposal template
Please use the following template when proposing a project idea or contribution opportunity. This helps keep proposals uniformly digestible by potential contributors and speeds up the process of turning your proposal into a live task. Please also make sure to include as much detail as possible so that a potential contributor knows exactly what to do with your project.
Project Proposal Template
Metadata
Summary
Include a detailed summary of your proposed project idea or contribution opportunity. The more detail here, the better. A contributor should be able to clearly understand what your project is about and what needs to get done.
Potential Features
Impact
Resources