This is the complete reference implementation of the ERC-721 non-fungible token standard for the Ethereum blockchain. This is an open source project, complete with Specron testing.
Purpose of this implementation is to provide a good starting point for anyone who wants to use and develop non-fungible tokens on the Ethereum blockchain. Instead of re-implementing the ERC-721 yourself you can use this code which has gone through multiple audits and we hope it will be extensively used by the community in the future.
If you are looking for a more feature-rich and advanced ERC721 implementation.
All contracts and tests are in the src folder. There are multiple implementations and you can select between:
nf-token.sol
: This is the base ERC-721 token implementation (with support for ERC-165).nf-token-metadata.sol
: This implements optional ERC-721 metadata features for the token contract. It implements a token name, a symbol and a distinct URI pointing to a publicly exposed ERC-721 JSON metadata file.nf-token-enumerable.sol
: This implements optional ERC-721 support for enumeration. It is useful if you want to know the total supply of tokens, to query a token by index, etc.
Other files in the tokens and utils directories named like erc*.sol
are interfaces and define the respective standards.
- NodeJS 9.0+ is supported
- Windows, Linux or macOS
This is the recommended installation method if you want to use this package in your own JavaScript project.
This project is released as an npm module. You must install it using the npm
command:
$ npm install @0xcert/ethereum-erc721@2.0.0-rc1
This is the recommended installation method if you want to improve the 0xcert/ethereum-erc721
project.
Clone this repository and install the required npm
dependencies:
$ git clone github.com/wooriapt/ethereum-erc721
$ cd ethereum-erc721
$ npm install
Make sure that everything has been set up correctly:
$ npm run test
To interact with this package's contracts within JavaScript code, you simply need to require this package's .json
files:
const contract = require("@0xcert/ethereum-erc721/build/nf-token-enumerable.json");
console.log(contract);
You can quickly deploy a contract with this library using Remix IDE. Here is one example.
You have created and have possession of unique glass-blown artwork (each having a serial number / lot number) which you would like to sell using Ethereum mainnet. You will sell non-fungible tokens and the buyers would be able to trade those to other people. One token per piece of artwork. You commit to anybody holding these tokens that they may redeem there token and take physical posession of the art.
To do this, simply paste the code belowe into Remix and deploy the smart contract. You will "mint" a token for each new piece of artwork you want to see. Then you will "burn" that token when you surrender physical possession of the piece.
pragma solidity 0.5.2;
import "https://github.com/wooriapt/ethereum-erc721/src/contracts/tokens/nf-token-metadata.sol";
import "https://github.com/wooriapt/ethereum-erc721/src/contracts/ownership/ownable.sol";
/**
* @dev This is an example contract implementation of NFToken with metadata extension.
*/
contract MyArtSale is
NFTokenMetadata,
Ownable
{
/**
* @dev Contract constructor. Sets metadata extension `name` and `symbol`.
*/
constructor()
public
{
nftName = "Frank's Art Sale";
nftSymbol = "FAS";
}
/**
* @dev Mints a new NFT.
* @param _to The address that will own the minted NFT.
* @param _tokenId of the NFT to be minted by the msg.sender.
* @param _uri String representing RFC 3986 URI.
*/
function mint(
address _to,
uint256 _tokenId,
string calldata _uri
)
external
onlyOwner
{
super._mint(_to, _tokenId);
super._setTokenUri(_tokenId, _uri);
}
/**
* @dev Removes a NFT from owner.
* @param _tokenId Which NFT we want to remove.
*/
function burn(
uint256 _tokenId
)
external
onlyOwner
{
super._burn(_tokenId);
}
}
You should contact a lawyer before holding an auction, or selling anything really. Specifically, laws for auctions vary wildly by jurisdiction. This application is provided only as an example of the technology and is not legal advice.
See CONTRIBUTING.md for how to help out.
See LICENSE for details.