From f3b52124ebed60c1c4614563fd0f65825a46157f Mon Sep 17 00:00:00 2001
From: Javier Arcenegui Almenara
 <81355285+Hardblock-IMSE-CNM@users.noreply.github.com>
Date: Tue, 15 Nov 2022 15:31:34 +0100
Subject: [PATCH] Update EIP-4519: Move to last call (#5908)

* Update eip-4519.md

* Update eip-4519.md
---
 EIPS/eip-4519.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/EIPS/eip-4519.md b/EIPS/eip-4519.md
index 8a25ddf698dd0..f12a3a2ece8c2 100644
--- a/EIPS/eip-4519.md
+++ b/EIPS/eip-4519.md
@@ -4,7 +4,8 @@ title: Non-Fungible Tokens Tied to Physical Assets
 description: Interface for non-fungible tokens representing physical assets that can generate or recover their own accounts and obey users.
 author: Javier Arcenegui (@Hardblock-IMSE-CNM), Rosario Arjona (@RosarioArjona), Roberto Román <roman@imse-cnm.csic.es>, Iluminada Baturone (@lumi2018)
 discussions-to: https://ethereum-magicians.org/t/new-proposal-of-smart-non-fungible-token/7677
-status: Review
+status: Last Call
+last-call-deadline: 2022-11-30
 type: Standards Track
 category: ERC
 created: 2021-12-03
@@ -45,7 +46,7 @@ $$K_A = SK_A*PK_{O_{-}A}$$
 
 If everything is correctly done, $K_O$ and $K_A$ are the same since:
 
-$$K_O=PK_A*SK_{O_{-}A}=(SK_A*P)\*SK_{O_{-}A}= SK_A*(SK_{O_{-}A}*P)=SK_A*PK_{O_{-}A}$$
+$$K_O=PK_A\*SK_{O_{-}A}=(SK_A\*P)\*SK_{O_{-}A}= SK_A\*(SK_{O_{-}A}\*P)=SK_A\*PK_{O_{-}A}$$
 
 Using the function `ownerEngagement`, the asset sends the hash of $K_A$, and if it is the same as the data in `hashK_OA`, then the state of the token changes to `engagedWithOwner` and the event `OwnerEngaged` are sent. Once the asset receives the event, it changes its operation mode to `engagedWithOwner`. This process is shown in `Figure 4`. From this moment, the asset can be managed by the owner and they can communicate in a secure way using the shared key. 
 
@@ -59,7 +60,7 @@ $$K_A = SK_A*PK_{U_{-}A}$$
 
 If everything is correctly done, $K_U$ and $K_A$ are the same since:
 
-$$K_U=PK_A*SK_{U_{-}A}=(SK_A*P)\*SK_{U_{-}A}= SK_A*(SK_{U_{-}A}*P)=SK_A*PK_{U_{-}A}$$
+$$K_U=PK_A\*SK_{U_{-}A}=(SK_A\*P)\*SK_{U_{-}A}= SK_A\*(SK_{U_{-}A}\*P)=SK_A\*PK_{U_{-}A}$$
 
 Using the function `userEngagement`, the asset sends the hash of $K_A$ obtained and if it is the same as the data in `hashK_UA`, then the state of the token changes to `engagedWithUser` and the event `UserEngaged` is sent. Once the asset receives the event, it changes its operation mode to `engagedWithUser`. This process is shown in `Figure 5`. From this moment, the asset can be managed by the user and they can communicate in a secure way using the shared key.