diff --git a/EIPS/eip-721.md b/EIPS/eip-721.md index 097abdda..65ac35b6 100644 --- a/EIPS/eip-721.md +++ b/EIPS/eip-721.md @@ -1,7 +1,7 @@ --- eip: 721 title: Non-Fungible Token Standard -author: William Entriken , Dieter Shirley , Jacob Evans , Nastassia Sachs +author: William Entriken (@fulldecent), Dieter Shirley , Jacob Evans , Nastassia Sachs discussions-to: https://github.com/ethereum/eips/issues/721 type: Standards Track category: ERC @@ -287,7 +287,7 @@ Additionally, an authorized operator may set the approved address for an NFT. Th The transfer and accept functions' documentation only specify conditions when the transaction MUST throw. Your implementation MAY also throw in other situations. This allows implementations to achieve interesting results: - **Disallow transfers if the contract is paused** — prior art, CryptoKitties deployed contract, line 611 -- **Blacklist certain address from receiving NFTs** — prior art, CryptoKitties deployed contract, lines 565, 566 +- **Blocklist certain address from receiving NFTs** — prior art, CryptoKitties deployed contract, lines 565, 566 - **Disallow unsafe transfers** — `transferFrom` throws unless `_to` equals `msg.sender` or `countOf(_to)` is non-zero or was non-zero previously (because such cases are safe) - **Charge a fee to both parties of a transaction** — require payment when calling `approve` with a non-zero `_approved` if it was previously the zero address, refund payment if calling `approve` with the zero address if it was previously a non-zero address, require payment when calling any transfer function, require transfer parameter `_to` to equal `msg.sender`, require transfer parameter `_to` to be the approved address for the NFT - **Read only NFT registry** — always throw from `unsafeTransfer`, `transferFrom`, `approve` and `setApprovalForAll`