mirror of https://github.com/status-im/EIPs.git
Correct whitespace
This commit is contained in:
parent
438c09e436
commit
19a5f63ea1
|
@ -37,7 +37,7 @@ Differences between this standard and EIP-20 are examined below.
|
|||
|
||||
## Specification
|
||||
|
||||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
|
||||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.
|
||||
|
||||
**Every ERC-721 compliant contract must implement the `ERC721` and `ERC165` interfaces** (subject to "caveats" below):
|
||||
|
||||
|
@ -47,7 +47,7 @@ pragma solidity ^0.4.20;
|
|||
/// @title ERC-721 Non-Fungible Token Standard
|
||||
/// @dev See https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md
|
||||
/// Note: the ERC-165 identifier for this interface is 0x6466353c
|
||||
interface ERC721 /* is ERC165 */ {
|
||||
interface ERC721 /* is ERC165 */ {
|
||||
/// @dev This emits when ownership of any NFT changes by any mechanism.
|
||||
/// This event emits when NFTs are created (`from` == 0) and destroyed
|
||||
/// (`to` == 0). Exception: during contract creation, any number of NFTs
|
||||
|
@ -287,7 +287,7 @@ The transfer and accept functions' documentation only specify conditions when th
|
|||
|
||||
- **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
|
||||
- **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)
|
||||
- **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`
|
||||
|
||||
|
|
Loading…
Reference in New Issue