主页EIPs
EIPsERC-7561
ERC-7561

Simple NFT, Simplified ERC-721

Designed for contract wallet, removes safeTransferFrom, approve, setApprovalForAll, getApproved, isApprovedForAll functions from ERC-721
DraftStandards Track: ERC
创建时间: 2023-10-29
关联 EIP: EIP-721
Xiang (@wenzhenxiang), Ben77 (@ben2077), Mingshi S. (@newnewsms)
社区讨论原文链接编辑
1 分钟了解
欢迎补充好内容
去提交
相关视频
欢迎补充好内容
去提交
正文

Abstract

This ERC is a new NFT asset designed based on the user contract wallet (including account abstraction), and is forward compatible with ERC-721. To keep NFT assets simple, this ERC removes the approve, setApprovalForAll, getApproved, isApprovedForAll and safeTransferFrom functions of ERC-721.

Motivation

ERC-721 defines Ethereum-based standard NFT that can be traded and transferred, but the essence of ERC-721 is based on the externally-owned account (EOA) wallet design. An EOA wallet has no state and code storage, and the smart contract wallet is different.

Almost all ERCs related to NFTs are add functions, but our opinion is the opposite. We think the NFT contract should be simpler, with more functions taken care of by the smart contract wallet.

Our proposal is to design a simpler NFT asset based on the smart contract wallet.

It aims to achieve the following goals:

  1. Keep the NFT contract simple, only responsible for the transferFrom function.
  2. approve, getApproved, setApprovalForAll and isApprovedForAll functions are not managed by the NFT contract. Instead, these permissions are managed at the user level, offering greater flexibility and control to users. This change not only enhances user autonomy but also mitigates certain risks associated with the ERC-721 contract's implementation of these functions.
  3. Remove the safeTransferFrom function. A better way to call the other party's NFT assets is to access the other party's own contract instead of directly accessing the NFT asset contract.
  4. Forward compatibility with ERC-721 means that all NFT can be compatible with this proposal.

Specification

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.

Compliant contracts MUST implement the following interface:

pragma solidity ^0.8.20; /** * @title ERC7561 Simple NFT interface * @dev See https://ercs.ethereum.org/ERCS/erc-7561 */ interface IERC7561 { /** * @notice Used to notify transfer NFT. * @param from Address of the from * @param to Address of the receive * @param tokenId The transaction token id */ event Transfer( address indexed from, address indexed to, uint256 indexed tokenId ); /** * @notice Count all NFTs assigned to an owner * @param owner Address of the owner * @return The number of NFTs owned by `owner`, possibly zero */ function balanceOf(address owner) external view returns (uint256); /** * @notice Find the owner of an NFT * @param tokenId The identifier for an NFT * @return The address of the owner of the NFT */ function ownerOf(uint256 tokenId) external view returns (address); /** * @notice Transfer ownership of an NFT * @param from Address of the from * @param to Address of the to * @param tokenId The NFT to transfer */ function transferFrom(address from, address to, uint256 tokenId) external; }

Rationale

The proposal is to simplify NFT standards by removing approve, setApprovalForAll, getApproved, isApprovedForAll and safeTransferFrom functions. This simplification aims to enhance security, reduce complexity, and improve efficiency, making the standard more suitable for smart contract wallet environments while maintaining essential functionalities.

Backwards Compatibility

As mentioned in the beginning, this ERC is forward compatible with ERC-721, ERC-721 is backward compatible with this ERC.

Reference Implementation

forward compatible with ERC-721

pragma solidity ^0.8.20; import "./IERC7561.sol"; import "../../math/SafeMath.sol"; /** * @title Standard ERC7561 NFT * @dev Note: the ERC-165 identifier for this interface is 0xc1b31357 * @dev Implementation of the basic standard NFT. */ contract ERC7561 is IERC7561 { // Token name string private _name; // Token symbol string private _symbol; mapping(uint256 tokenId => address) private _owners; mapping(address owner => uint256) private _balances; uint256 private _totalSupply; function totalSupply() external view returns (uint256) { return _totalSupply; } function balanceOf(address owner) public view returns (uint256) { require (owner != address(0)); return _balances[owner]; } function ownerOf(uint256 tokenId) public view returns (address) { return _requireOwned(tokenId); } function transferFrom(address from, address to, uint256 tokenId) public { require(from == msg.sender); require (to != address(0) ); address previousOwner = _update(to, tokenId); require(previousOwner == from); } function _ownerOf(uint256 tokenId) internal view virtual returns (address) { return _owners[tokenId]; } function _requireOwned(uint256 tokenId) internal view returns (address) { address owner = _ownerOf(tokenId); require(owner != address(0)); return owner; } function _update(address to, uint256 tokenId) internal virtual returns (address) { address from = _ownerOf(tokenId); // Execute the update if (from != address(0)) { unchecked { _balances[from] -= 1; } } if (to != address(0)) { unchecked { _balances[to] += 1; } } _owners[tokenId] = to; emit Transfer(from, to, tokenId); return from; } }

Security Considerations

It should be noted that this ERC is not backward compatible with ERC-721, so there will be incompatibility with existing dapps.

Copyright and related rights waived via CC0.

扩展阅读
欢迎补充好内容
去提交
相关项目
欢迎补充好内容
去提交

不想错过最新的 EIP 动态?

订阅 EIPs Fun 周刊以跟进相关更新,建⽴你与 EIP 之间的连接 ,更好地建设以太坊。

详情
支持以太坊贡献者,推动生态建设
资源
GitHub
支持社区