This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0721 [2020/05/07 18:56] nick ↷ Page moved from dido:public:xapend.stds:defact:ethereum:eip:erc_0721 to dido:public:ra:xapend.stds:defact:ethereum:eip:erc_0721 |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0721 [2021/08/18 11:18] (current) murphy |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ======== EIP 721: ERC-721 Non-Fungible Token Standard ========= | + | ==== EIP 721: ERC-721 Non-Fungible Token Standard ==== |
- | [[dido:public:xapend.stds:defact:ethereum| Return to Ethereum ERCs ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip| Return to Ethereum ERCs ]] |
- | : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a connivence and is not authoritative. Refer to the original document as the authoritative reference. | + | : **Note**: The following is an excerpt from the official Ethereum site. It is provided here as a convenience and is not authoritative. Refer to the original document as the authoritative reference. |
<table> | <table> | ||
- | <caption>Data sheet for TTTTT</caption> | + | <caption>Data sheet for Non-Fungible Token Standard</caption> |
| Title | Non-Fungible Token Standard | | | Title | Non-Fungible Token Standard | | ||
| Author | William Entriken, Dieter Shirley, Jacob Evans, Nastassia Sachs | | | Author | William Entriken, Dieter Shirley, Jacob Evans, Nastassia Sachs | | ||
Line 13: | Line 13: | ||
| Specification | [[http://eips.ethereum.org/EIPS/eip-721#Specification]] | | | Specification | [[http://eips.ethereum.org/EIPS/eip-721#Specification]] | | ||
| Category | ERC | | | Category | ERC | | ||
- | | Requires | [[dido:public:xapend.stds:defact:ethereum:eip:erc_0165| ERC-165 ]] | | + | | Requires | [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0165|ERC-165]] | |
</table> | </table> | ||
+ | === Abstract === | ||
+ | //The following standard allows for the implementation of a standard [[dido:public:ra:xapend:xapend.a_glossary:a:api|API]] for [[dido:public:ra:xapend:xapend.a_glossary:n:nft]] within smart contracts. This standard provides basic functionality to track and transfer NFTs.// | ||
- | ====== Abstract ====== | + | //We considered use cases of NFTs being owned and transacted by individuals as well as consignment to third party brokers/[[dido:public:ra:xapend:xapend.a_glossary:w:wallet|wallets]]/auctioneers (“operators”). NFTs can represent ownership over digital or physical assets. We considered a diverse universe of assets, and we know you will dream up many more:// |
- | : //The following standard allows for the implementation of a standard API for Non-Fungible Tokens (NFTs) within smart contracts. This standard provides basic functionality to track and transfer NFTs.// | + | |
- | + | ||
- | : //We considered use cases of NFTs being owned and transacted by individuals as well as consignment to third party brokers/wallets/auctioneers (“operators”). NFTs can represent ownership over digital or physical assets. We considered a diverse universe of assets, and we know you will dream up many more:// | + | |
* //Physical property — houses, unique artwork// | * //Physical property — houses, unique artwork// | ||
Line 26: | Line 25: | ||
* //“Negative value” assets — loans, burdens and other responsibilities// | * //“Negative value” assets — loans, burdens and other responsibilities// | ||
- | : //In general, all houses are distinct and no two kittens are alike. NFTs are distinguishable and you must track the ownership of each one separately.// | + | //In general, all houses are distinct and no two kittens are alike. NFTs are distinguishable and you must track the ownership of each one separately.// |
- | ====== Motivation ====== | + | === Motivation === |
- | : //A standard interface allows wallet/broker/auction applications to work with any NFT on Ethereum. We provide for simple ERC-721 smart contracts as well as contracts that track an arbitrarily large number of NFTs. Additional applications are discussed below.// | + | //A standard [[dido:public:ra:xapend:xapend.a_glossary:i:interface|interface]] allows wallet/broker/auction applications to work with any NFT on Ethereum. We provide for simple ERC-721 smart contracts as well as contracts that track an arbitrarily large number of NFTs. Additional applications are discussed below.// |
- | : //This standard is inspired by the [[dido:public:xapend.stds:defact:ethereum:eip:erc_0020| ERC-20 ]] token standard and builds on two years of experience since EIP-20 was created. EIP-20 is insufficient for tracking NFTs because each asset is distinct (non-fungible) whereas each of a quantity of tokens is identical (fungible).// | + | //This standard is inspired by the [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0020|ERC-20]] token standard and builds on two years of experience since EIP-20 was created. EIP-20 is insufficient for tracking NFTs because each asset is distinct (non-fungible) whereas each of a quantity of [[dido:public:ra:xapend:xapend.a_glossary:t:tokens|tokens]] is identical ([[dido:public:ra:xapend:xapend.a_glossary:f:fungible|fungible]]).// |
- | : //Differences between this standard and EIP-20 are examined below.// | + | //Differences between this standard and EIP-20 are examined below.// |