Differences & Limitations
This page lists the opcodes that are not fully supported by Zircuit networks at this time.
Last updated
This page lists the opcodes that are not fully supported by Zircuit networks at this time.
Last updated
A hash of the blob’s KZG commitment. Since blobs themselves are not stored on the execution layer, this is used to validate a blob belonging to a transaction. If the blob data is altered in any way, its hash will change as well, so the actual hash found on-chain will no longer match.
Provides the blob base fee for the current block. This opcode helps with accounting for blob data usage costs, similar to the existing opcode BASEFEE
.
Zircuit's Garfield networks do not support SELFDESTRUCT
in any form. The opcode is handled the same as the INVALID
opcode.
The opcode PREVRANDAO
returns the mixHash
field of the block. However, it will always be 0
.
The circuits used by Zircuit Garfield currently restrict the number of calls possible to precompiles. Transactions that exceed these limits will be dropped.
keccak256
3157
ecRecover
119
modexp
23
ecAdd
50
ecMul
50
ecPairing
2