status-im/EIPs
2
0
Fork 0
mirror of https://github.com/status-im/EIPs.git synced 2025-02-23 20:28:21 +00:00
Code Issues Projects Releases Wiki Activity

Change EIP-2718 status from "Draft" to "Review" (#3232)

Browse Source 
Moves to review.
This commit is contained in:
Pooja Ranjan 2021-01-30 21:46:49 -05:00 committed by GitHub
parent 28c7a61f51
commit a9eae63736
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
EIPS/eip-2718.md
View File

@ -3,7 +3,7 @@ eip: 2718
title: Typed Transaction Envelope title: Typed Transaction Envelope
author: Micah Zoltu (@MicahZoltu) author: Micah Zoltu (@MicahZoltu)
discussions-to: https://ethereum-magicians.org/t/eip-2718-typed-transaction-envelope/4355 discussions-to: https://ethereum-magicians.org/t/eip-2718-typed-transaction-envelope/4355
status: Draft status: Review
type: Standards Track type: Standards Track
category: Core category: Core
created: 2020-06-13 created: 2020-06-13
@ -73,14 +73,8 @@ Clients can differentiate between the legacy transactions and typed transactions
If it starts with a value in the range `[0, 0x7f]` then it is a new transaction type, if it starts with a value in the range `[0xc0, 0xfe]` then it is a legacy transaction type. If it starts with a value in the range `[0, 0x7f]` then it is a new transaction type, if it starts with a value in the range `[0xc0, 0xfe]` then it is a legacy transaction type.
`0xff` is not realistic for an RLP encoded transaction, so it is reserved for future use as an extension sentinel value. `0xff` is not realistic for an RLP encoded transaction, so it is reserved for future use as an extension sentinel value.
## Test Cases
TBD
## Implementation
TBD
## Security Considerations ## Security Considerations
TBD When designing a new 2718 transaction type, it is **STRONGLY** recommended to include the transaction type as the first byte of the signed payload. If you fail to do this, it is possible that your transaction may be signature compatible with transactions of another type which can introduce security vulnerabilities for users.
## Copyright ## Copyright
Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/). Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).