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

Calldata over memory #551

Open
hensha256 opened this issue Apr 3, 2024 · 1 comment
Open

Calldata over memory #551

hensha256 opened this issue Apr 3, 2024 · 1 comment
Labels

Comments

@hensha256
Copy link
Contributor

Component

No response

Describe the suggested feature and problem it solves.

A number of the parameters used in core are passed in using memory, but are never written to only read, so we should try to move them to calldata and see if it saves gas. This includes the unlockCallback should be parsing in calldata not memory to save it being passed back and forth between the 2

I spent a few mins doing a first pass on calldata-not-memory but things are failing and this isnt my priority right now

Describe the desired implementation.

No response

Describe alternatives.

No response

Additional context.

No response

@nishim3
Copy link
Contributor

nishim3 commented Apr 4, 2024

On an initial attempt with making the PoolKey calldata instead of memory, the gas only seems to be increasing. The addLiquidity snap goes up by 2000.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants