-
Notifications
You must be signed in to change notification settings - Fork 385
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
[Deployments] Batch relayer V4 preparation. #1706
Conversation
jubeira
commented
Sep 6, 2022
- Binaries, scripts and fork test (same as in V3).
- Deprecating V3.
- Updating README.
- Binaries, scripts and fork test. - Deprecating V3. - Updating README.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Marking as do-not-merge since we don't yet have the final build info.
Can you do a goerli deployment of the current version however, so that the SDK team can test it?
Done: 34e5a7e |
- No return values for gauge actions. - Chained reference slot fix (same for temp / read-only).
@johngrantuk the new deployment for the batch relayer in Goerli is ready; you can see more info here 2cda6a7. |
When building 2d310c3 I get the same build-info as committed |
We're looking into an issue that seems to cause for the build info file to not be identical on every run - the file id is different, and some fields are in different order. But the actual contents of the source code, bytecode, etc., are all the same. |
* master: Upgrade ignore-warnings (#1789) Expose getter for expected compression error on ValueCompression.sol (#1793) Remove `_getTotalTokens` internal getter (#1794) Remove unused imports (#1795) Make base pool better (#1790) Update readme.md Deploy relayer v4 (#1791) [Deployments] Batch relayer V4 preparation. (#1706) refactor: remove BaseWeightedPool (#1788) Move ManagedPool swap, join, exit logic to ManagedPoolAMMLogic (#1787)