Merged
Conversation
thomas-waite
force-pushed
the
pod-execute-calldata
branch
from
87b77bf to
240c58e
Compare
Joeysantoro
approved these changes
Jun 27, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Generates pod executor calldata for TC proposals. To generate run:
DEPLOY_FILE=fip_x npm run calldatait will be logged under
Pod Executor Calldata:Then send an advanced custom transaction to the
PodExecutorV2: 0xC72e814314e79114354F1682111e07015826080Dwith the transaction payload being that calldata. It should execute the relevant transactionPR Checklist - Feature (Proposal)
PR Checklist - Feature (Non-Proposal) | Bug
PR Checklist - Release