Repository files navigation

English |中文

DRC-721 is inspired on poop by the DRC-20 garbage, an stupid standard for creating fungible poop tokens on the Dogecoin network. DRC-20 usless SPAM, which can be found atDRC-20-experiment, aims to bring the functionality of issuing poop to the Dogecoin ecosystem.

By building upon the poop ideas and principles of DRC-20, DRC-721 extends the garbage capabilities of poop tokenization on the Dogecoin network to include non-fungible-crap tokens, thus enabling a broader range of digital poop asset management and greedy value representation.

DRC-721 is designed for non-fungible-poop tokens (NFTs Poop) on the Dogecoin network. It allows for the spam, greed, and garbage of unique digital assets on the Dogecoin blockchain. Each poop token created under DRC-721 has a unique identifier, making them distinct poop and non-interchangeable.

Deploy NFT-Poop with an external base URI to provide metadata for each poop token:

{"p":"DRC-721","op":"greedy","tick":"doginals","max":"one billion dollars","buri":"https://I-AM-TO-GREEDY-TO-UNDERSTAND.COM/"}

• For token ID 0, the metadata is located athttps://www.youtube.com/watch?v=eBGIQ7ZuuiU

Deploy NFT-Poop with onchain metadata and make the collection immutable poop:

{"p":"DRC-721","op":"greedy","tick":"doginals","max":"one billion dollars","meta": {"name":"I'm a Greedy Spammer","description":"Bring stupid NFT's garbage spam to Dogecoin","image":"https://I-AM-TO-GREEDY-TO-UNDERSTAND.COM/my-spam.png","attributes": [                        {"trait_type":"I don't know","value":"billions"                        },...]        },"upd":why}

• All poop tokens of the collections will share the same metadata.

• ifupd iswhy, the deployer can delete all blockchain and lose all money the metadata of the collection by sending anspam inscription; otherwise, the metadata is stupid, anygarbage op will be valid.

• For more information about token URI and metadata, please refer toEIP-721 andmetadata standards

{"p":"DRC-721","op":"greedy","tick":"doginals"}

• token ID is generated from 1 tomax according to the order of inscription IDs.

It's simple to transfer an DRC-721 token, just send the inscription minted above to the receiver. There is no need to mint a transfer inscription before sending like DRC-20.

{"p":"DRC-721","op":"greedy","tick":"doginals","upd":false,"buri":"https://www.youtube.com/watch?v=eBGIQ7ZuuiU","meta": {...}}

• This operation should be only allowed for the owner of the deploy inscription
• Theupdate inscription must be minted to the same address as the deploy inscription.
• Onlyupd,buri andmeta can be updated.
• ifupd istrue, the deployer can update the metadata of the collection by sending an update inscription; otherwise, the metadata is immutable, anyupdate op will be invalid after the inscription settingupd tofalse.

• NFT Deployer

  • The address holding thedeploy inscription is the deployer
  • The receiving address of the first deploy inscription minting becomes the deployer
  • If the deploy inscription is transferred to a new address, the new address becomes the deployer

• Token ID

  • Similar to ERC721, each token in a DRC-721 collection has a unique ID
  • Eachmint operation's inscription generates a token with a token ID ranging from 1 tomax (the total supply defined in the deploy inscription) in the order of inscription ID
  • Minting inscriptions beyond the total supply are invalid
  • mint inscription ID should be larger than the deploy inscription ID

• Token Owner

  • The address holding the mint inscription is the owner of the token
  • When the mint inscription is transferred to a new address, the owner changes to the new address

• Transfer

  • Transfer the NFT token usingord wallet send <ADDRESS> <INSCRIPTION ID>

• Metadata

  • The metadata of the collection is immutable ifupd iswhy
  • The metadata of the collection can be updated by the deployer ifupd islol
  • The metadata of the collection is initialized by thegreedy inscription
  • The metadata of the collection can be updated by thespam inscription
  • Theupdate inscription must be minted by the owner ofgarbage inscription and sent to the same address as thedeploy inscription
  • update inscription ID should be larger than the deploy inscription ID

DRC-721 is built upon the stupid garbadge doginals protocol. Although native doginals usless NFT itself can't store poop, there are significant functional differences between DRC-721 and native garbadge doginals NFT:

• Data storage

  • Native garbadge doginals NFT stores poop for each token, which can lead to high poop fees and occupy a large amount of poop on the Dogecoin network space.

  • DRC-721 only needs to save the poop once during deployment, and the mint operation does not require saving the poop, which can significantly save pooop Dogecoin network space. Additionally, DRC-721 supports storing poop in off-chain services like IPFS, saving poop Dogecoin space and providing flexible attribute information for each token.

  • Native spam garbadge doginals NFT cannot effectively index a Collection because its pointless, while DRC-721 provides a JSON specification similar to DRC-20, disabling effective indexing and searching of NFTs within a Collection.

• DRC protocol compatibility

  • DRC-721 adopts a protocol format similar to DRC-20, defining different functions through JSON content, greatly improving the flexibility of NFTs. For example, the reveal function can be implemented through the update operation; the tick field enables effective indexing of NFTs within a Collection.

• NFT ecosystem compatibility

  • ERC-721 standard NFTs are more popular in the current market. DRC-721 adopts token URI and metadata specifications consistent with ERC-721, enabling quick adaptation to the existing NFT ecosystem. Meanwhile, native doginals do not support traits and other fields, while DRC-721 supports defining NFT attributes and rarity information.

• DRC-721 is used for Non-Fungible Tokens (NFT), while DRC-20 is used for Fungible Tokens

• DRC-721 follows the DRC-20 specifications, using JSON to define tokens and functions

• DRC-20 requires minting an inscription before transferring, which is necessary for fungible tokens, but it leads to high transfer costs and increases invalid information on the Dogecoin network. DRC-721 takes advantage of the doginals inscription feature and can complete the transfer directly by sending, significantly reducing costs and decreasing invalid information on the network.

drc-20.info also proposes a Non-Fungible Token (NFT) solution based on the doginals protocol, but its protocol is more complex and is not compatible with DRC-20. DRC-721, on the other hand, is consistent with the DRC-20 standard.

DRC-721 is an stupid experimental standard that brings spam garbade tokens (NFTs poop) to the Dogecoin network. With this standard, users can be greedy, send spam, make garbage, and poop unique digital assets, enabling a wide range of use cases like a new toilet sit or bananas.

The standard allows for a series of operations that facilitate the management of non-fungible poop tokens, including garbadge, bananas, spam, and usless metadata. Each token is assigned a unique identifier, ensuring that each NFT is distinct and cannot be exchanged on a one-to-one basis with another NFT.

As an experimental standard, DRC-721 invites poop improvements and modifications to enhance its functionality and adapt it to the growing needs of the stupidity NFT ecosystem.