* Switch EOF EIPs to Review
* Add the description header to the EOF
* Add test cases to 3540
* Add security considerations
* Add reference code validation implementation to EIP-3540
* Fix the simplified validator in 3540
* Turn the simplified validator into python too
* Validate static JUMPSUB using immediate data
Ethereum object format allows immediate data, which https://github.com/ethereum/evmone/pull/351 uses to provide static, relative jumps. This allows for static, validated subroutines.
* Update eip-2315.md
* Add description field to the EIP header
* Update 2718
* Move description rendering to below the title
* Remove the simple summary from the template
This has been removed from EIP-1 on 15-09-2019 in the PR https://github.com/ethereum/EIPs/pull/2186.
* Update title/description/abstract with new recommendation
* Mention length limit of description
* eip-225: additionally label ethash header field with original miner field name for easier association
* eip-225: added fille-with-zeros-on-genesis note to EXTRA_SEAL definition
* eip-225: added ascending-byte-order note to extraData signer section description to avoid ascending-time-order confusion
* eip-225: better differentiate between sighash and final block hash
* eip-225: added note on transaction fee and block reward attribution
* eip-225: added zero-based note to SIGNER_INDEX
* EIP-225: changed block reward distribution must -> should after review
* eip-225: removed block rewards note and corrected typo (from code review)
Co-authored-by: Micah Zoltu <micah@zoltu.net>
Co-authored-by: Micah Zoltu <micah@zoltu.net>
Co-authored-by: Alita Moore <alita.moore805@gmail.com>
The industry standard is to encode signatures as `(bytes32 r, bytes32 s, uint8 v)` in 65 bytes, which is evident here: d3c5bdf4de/contracts/utils/cryptography/ECDSA.sol (L32)
But also in the implementation code which reads the first 32 bytes as r, then the next as s, and the last byte as v
However, it checks if the signature is 66 bytes long, rather than the 65 which it reads. As such I believe this is an error in the example.
* Renames `tip` to `gas premium` in non-normative content.
* Update EIPS/eip-1559.md
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
* 1559: Use snakecase throughout the spec
* 1559: Update ReceiptPayload to also use snakecase (plus ensure cumulative_transaction_gas_used matches the code)
