The Program Counter of this Opcode.
The index in the Opcode[] where this Opcode is inserted.
Any byte number, i.e., between 0 and 255 representing the opcode byte.
The opcode may not be a valid opcode.
Represents a valid opcode.
In https://www.evm.codes/ you can find an overview of each EVM opcode.
If the opcode given is not a valid opcode,
you can provide INVALID as mnemonic.
A PUSHn opcode only permits a PUSHn opcode.
A Unary opcode does not include any data. For these opcodes data is null.
If this Opcode is a PUSHn instruction or contains any operand data,
then it contains the data attached to this instruction.
Readonly dataA Unary opcode does not include any data. For these opcodes data is null.
If this Opcode is a PUSHn instruction or contains any operand data,
then it contains the data attached to this instruction.
Readonly mnemonicRepresents a valid opcode.
In https://www.evm.codes/ you can find an overview of each EVM opcode.
If the opcode given is not a valid opcode,
you can provide INVALID as mnemonic.
A PUSHn opcode only permits a PUSHn opcode.
Readonly opcodeAny byte number, i.e., between 0 and 255 representing the opcode byte.
The opcode may not be a valid opcode.
Readonly pcThe Program Counter of this Opcode.
The index in the Opcode[] where this Opcode is inserted.
Where the next opcode should be located at.
Generated using TypeDoc v0.25.2
Represents an opcode found in the bytecode augmented with offset and operand information as defined by the EVM.
It can be either a unary opcode, which does not take any operand data, or either a
PUSHnmnemonic augmented with its pushdata. That is, all butPUSHnn >= 1opcodes are unary opcodes.PUSHnn >= 1opcodes takes ann-byte argument from the bytecode. Note thatPUSH0^1 does not take any data argument from the bytecode (just pushes0onto theStack). Thus it can be considered as an unary opcode.