From a9eae6373679d374b63a7791f99b5c284e988552 Mon Sep 17 00:00:00 2001
From: Pooja Ranjan <29681685+poojaranjan@users.noreply.github.com>
Date: Sat, 30 Jan 2021 21:46:49 -0500
Subject: [PATCH] Change EIP-2718 status from "Draft" to "Review" (#3232)

Moves to review.
---
 EIPS/eip-2718.md | 10 ++--------
 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/EIPS/eip-2718.md b/EIPS/eip-2718.md
index 65c8fe9a..bd21c473 100644
--- a/EIPS/eip-2718.md
+++ b/EIPS/eip-2718.md
@@ -3,7 +3,7 @@ eip: 2718
 title: Typed Transaction Envelope
 author: Micah Zoltu (@MicahZoltu)
 discussions-to: https://ethereum-magicians.org/t/eip-2718-typed-transaction-envelope/4355
-status: Draft
+status: Review
 type: Standards Track
 category: Core
 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.
 `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
-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 and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).