-
Notifications
You must be signed in to change notification settings - Fork 30
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
01e5e98
commit f145998
Showing
1 changed file
with
42 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
--- | ||
CIP No.: 119 | ||
Title: PUSH0 instruction | ||
Author: Chenxing Li (@ChenxingLi) | ||
Status: Draft | ||
Type: Spec Breaking | ||
Created: 2023-07-21 | ||
--- | ||
|
||
## Simple Summary | ||
Introduce the `PUSH0 (0x5f)` instruction, which pushes the constant value 0 onto the stack. | ||
|
||
## Abstract | ||
Introduce the `PUSH0 (0x5f)` instruction as [EIP-3855](https://eips.ethereum.org/EIPS/eip-3855). | ||
|
||
## Motivation | ||
|
||
Currently, the Solidity compiler generates bytecode for EVM after EIP-3855. Supporting this opcode can achieve maximum compatibility with Ethereum. | ||
|
||
## Specification | ||
Same as [EIP-3855](https://eips.ethereum.org/EIPS/eip-3855). | ||
|
||
## Rationale | ||
N/A | ||
|
||
## Backwards Compatibility | ||
This CIP is Spec Breaking. | ||
|
||
## Test Cases | ||
<!--Test cases for an implementation are mandatory for CIPs that are affecting consensus changes. Other CIPs can choose to include links to test cases if applicable.--> | ||
N/A | ||
|
||
## Implementation | ||
<!--The implementations must be completed before any CIP is given status "Final", but it need not be completed before the CIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.--> | ||
N/A | ||
|
||
## Security Considerations | ||
<!--All CIPs must contain a section that discusses the security implications/considerations relevant to the proposed change. Include information that might be important for security discussions, surfaces risks and can be used throughout the life cycle of the proposal. E.g. include security-relevant design decisions, concerns, important discussions, implementation-specific guidance and pitfalls, an outline of threats and risks and how they are being addressed. CIP submissions missing the "Security Considerations" section will be rejected. a CIP cannot proceed to status "Final" without a Security Considerations discussion deemed sufficient by the reviewers.--> | ||
N/A | ||
|
||
## Copyright | ||
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). |