diff --git a/EIPS/eip-3074.md b/EIPS/eip-3074.md
index 781bb00268a996..8a0d225b27fca0 100644
--- a/EIPS/eip-3074.md
+++ b/EIPS/eip-3074.md
@@ -245,6 +245,10 @@ Using `commit` as a hash of values allows for invokers to implement arbitrary co
 
 ![multi-call auth message](../assets/eip-3074/auth-msg-multi-call.png)
 
+Another interesting use is to delegate control of the EOA to other key(s). This would mean the EOA signs a `commit` message with the address of the key(s) and an access policy, if applicable. When the delegate wants to make a call as the EOA it will construct a signature over the invoker-specified call format and relay it (with the actual call data) onto chain with the signature and commit that granted it access to the account. The invoker will then be able to determine that the EOA has allowed this alternative key to make calls on its behalf.
+
+![delegate auth message](../assets/eip-3074/auth-msg-delegate.png)
+
 
 ### Invoker Contracts
 
diff --git a/assets/eip-3074/auth-msg-delegate.png b/assets/eip-3074/auth-msg-delegate.png
new file mode 100644
index 00000000000000..84b59a58b07954
Binary files /dev/null and b/assets/eip-3074/auth-msg-delegate.png differ
diff --git a/assets/eip-3074/auth-msg-multi-call.png b/assets/eip-3074/auth-msg-multi-call.png
index 55da8359ef97f7..f4e414ca39b64d 100644
Binary files a/assets/eip-3074/auth-msg-multi-call.png and b/assets/eip-3074/auth-msg-multi-call.png differ
diff --git a/assets/eip-3074/auth-msg.png b/assets/eip-3074/auth-msg.png
index 2fc38d62fb501c..b70c4446dd9904 100644
Binary files a/assets/eip-3074/auth-msg.png and b/assets/eip-3074/auth-msg.png differ