Compare
Four documents, the same five questions.
No throughput league table and no yield. The cells are what this library is willing to say about the text.
| Question | New opcodes: RETURNDATASIZE and RETURNDATACOPY |
|---|---|
| What the text proposes | EIP 211, New opcodes: RETURNDATASIZE and RETURNDATACOPY. A mechanism to allow returning arbitrary-length data inside the EVM has been requested for quite a while now. |
| Who may write | Christian Reitwiessner |
| What is settled | A mechanism to allow returning arbitrary-length data inside the EVM has been requested for quite a while now. |
| Load-bearing assumption | A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule. |
| What this library says afterwards | Status in the source: Final. A reading of the public specification, not a copy of it and not a certification. |
| Rights | Official external source only |