From f065ea17884c4932882696d2b7df1cb6bef65782 Mon Sep 17 00:00:00 2001 From: Dexaran Date: Wed, 25 Oct 2023 17:11:30 +0400 Subject: [PATCH] Update EIPS/eip-7915.md Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com> --- EIPS/eip-7915.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/EIPS/eip-7915.md b/EIPS/eip-7915.md index 682bb3784f0257..94ad7e412aef06 100644 --- a/EIPS/eip-7915.md +++ b/EIPS/eip-7915.md @@ -18,7 +18,7 @@ The following describes a security flaw in the transferring workflow of [ERC-20] ### [ERC-20](./eip-20.md) design overview -[ERC-20](./eip-20.md) standard declares two methods of transferring tokens: (1) `transfer` function and (2) `approve` & `transferFrom` pattern. `approve` & `transferFrom` is supposed to be used to deposit tokens to contracts. The `transfer` function is supposed to be used for transfers between externally owned addresses however this is not directly written in the specification. If the tokens are sent to a contract address via the `transfer` function then the recipient contract will not recognize the depoist. +[ERC-20](./eip-20.md) standard declares two methods of transferring tokens: (1) `transfer` function and (2) `approve` & `transferFrom` pattern. `approve` & `transferFrom` is supposed to be used to deposit tokens to contracts. The `transfer` function is supposed to be used for transfers between externally owned addresses however this is not directly written in the specification. If the tokens are sent to a contract address via the `transfer` function then the recipient contract will not recognize the deposit. ### Security flaw