diff --git a/EIPS/eip-6384.md b/EIPS/eip-6384.md
index 247ff604df8fe7..4b42bebabf7ea5 100644
--- a/EIPS/eip-6384.md
+++ b/EIPS/eip-6384.md
@@ -8,7 +8,7 @@ status: Draft
 type: Standards Track
 category: Interface
 created: 2023-01-08
-requires: 712
+requires: [EIP-712](./eip-712.md)
 ---
 
 ## Abstract
@@ -21,24 +21,24 @@ This is a standard for making a proposed to be signed typed structured data huma
 
 ## Motivation
 
-The use case of Web3 off-chain signatures intended to be used within on-chain transaction is gaining traction and being used in multiple leading protocols (e.g. OpenSea) and standards EIP-2612, mainly as it offers a fee-less experience.
+The use case of Web3 off-chain signatures intended to be used within on-chain transaction is gaining traction and being used in multiple leading protocols (e.g. OpenSea) and standards [EIP-2612](./eip-2612.md), mainly as it offers a fee-less experience.
 Attackers are known to actively and successfully abuse such off-chain signatures, leveraging the fact that users are blindly signing off-chain messages, since they are not humanly readable.
-While EIP-712 originally declared in its title that being ”humanly readable” is one of its goals, it did not live up to its promise eventually and EIP-712 messages are not understandable by an average user.
+While [EIP-712](./eip-712.md) originally declared in its title that being ”humanly readable” is one of its goals, it did not live up to its promise eventually and EIP-712 messages are not understandable by an average user.
 
 The example below shows the user exprience of victims that browse an actual phishing website. The phishing website requests the victims to sign a message that will put their NFT token for sale on OpenSea platform for a virtually zero price.
 
-![](../media/MiceyMask.gif)
+![](../assets/eip-6384/media/MiceyMask.gif)
 
 As this example shows, the user interface for some popular wallet implementations is not coveying the actual meaning of signing such transactions.
 
 In this proposal we offer a secure and scalable method to bring true human readability to EIP-712 messages by leveraging their binded smart contracts.
 As a result, once implemented this EIP wallets can upgrade their user experience from current state:
 
-![](../media/MiceyMask%20non-compliant.png)
+![](../assets/eip-6384/media/MiceyMask-non-compliant.png)
 
 to a much clearer user experience:
 
-![](../media/ZenGo%20EIP%20compliant%20.png)
+![](../assets/eip-6384/media/ZenGo-EIP-compliant.png)
 
 ## Specification
 
diff --git a/assets/eip-6384/media/MiceyMask-non-compliant.png b/assets/eip-6384/media/MiceyMask-non-compliant.png
new file mode 100644
index 00000000000000..b1cc4bba9608be
Binary files /dev/null and b/assets/eip-6384/media/MiceyMask-non-compliant.png differ
diff --git a/assets/eip-6384/media/Offline-signature-EIP-before-and-after.png b/assets/eip-6384/media/Offline-signature-EIP-before-and-after.png
new file mode 100644
index 00000000000000..c3d99e9e98391a
Binary files /dev/null and b/assets/eip-6384/media/Offline-signature-EIP-before-and-after.png differ
diff --git a/assets/eip-6384/media/ZenGo-EIP-compliant.png b/assets/eip-6384/media/ZenGo-EIP-compliant.png
new file mode 100644
index 00000000000000..eef608bc6d1d73
Binary files /dev/null and b/assets/eip-6384/media/ZenGo-EIP-compliant.png differ