Feat/add test build #29
Open
Conversation
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
Co-authored-by: Yunjong Jeong (ollie) <[email protected]>
Co-authored-by: Yunjong Jeong (ollie) <[email protected]>
Co-authored-by: Lewis <[email protected]>
Co-authored-by: Lewis <[email protected]>
Co-authored-by: Lewis <[email protected]>
Sotatek-TinnNguyen
requested review from
aidan-kwon,
blukat29,
ian0371 and
scott-klaytn
as code owners
Fix wrong kip number
[KIP-223] Calldata gas reduction
[KIP-228] SetCode transaction for Kaia
[KIP-223] File name changed to KIP number
kip-228: SetCodeTx updates CodeInfo as well
…feat/add-test-build
Contributor
|
@Sotatek-TinnNguyen Could you rebase against latest dev? This some changes are irrelevant to build scripts. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Types of changes
Please put an x in the boxes related to your change.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
I have read the CLA Document and I hereby sign the CLAin first time contributionRelated issues
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you proposed and what alternatives you have considered, etc.