Quick Start

Read every word if you decide to test. These will be worthless. Use at your own risk.

Proposal Initiators​

This is just a new proposal to improve the flaws of BTC NFT. Easier: NFT deployers can deploy the collection to the inscription at once. Lower cost: Previously users who wanted to have NFT needed to burn the entire image onto the chain, now they only need a section of text and image ipfs to host it, saving more money and making the market for NFT broader. More decentralized: This proposal uses the ipfs protocol, which allows resolution service providers to resolve NFT's RANK and trait types faster. As such, this is a very dynamic experiment and I encourage the Bitcoin community to tinker with standard designs and optimizations until there is a general consensus on best practices.

About IPFS

IPFS is a permanent, tamper-evident storage protocol, and the CID that corresponds to IPFS is a unique identifier.

Related Documents

Principle of ipfs

https://docs.ipfs.tech/concepts/content-addressing

Experiment to see if ordinal theory can facilitate fungibility on bitcoin

  • Create a brc-721 with the deploy function

  • Mint of brc-721 with the mint function

  • Transfers can be transferred directly using the specified inscription transfer method

  • Special attention : It is recommended to use unisat wallet or Sparrow wallet for transferring . Try to transfer inscriptions carefully and do not submit them as miner's fees, otherwise NFT will be lost on the chain forever.

  • At the same time, the resolution service we are developing for BRC721 is an effective indexer. I'll list it when the website goes live

Notes

  • Do not send inscriptions to non ordinal compatible wallet taproot addresses

  • It is unlikely that balances will be safely tradable using existing marketplace infrastructure.

  • The first deployment of a ticker is the only one that has claim to the ticker. Tickers are not case sensitive (PUNK= punk).

  • If two events occur in the same block, prioritization is assigned via order they were confirmed in the block. (first to last).

  • For public brc-721 mints the bitcoin punks / .sats names 'first is first' approach is adopted

  • The first mint that exceeds the maximum supply will receive a valid score. (Example: 10,000 maximum supply, 9,550 circulating supply, valid within 450 balance).

Operations

As I mentioned above, this is just my fun experimental standard design. I welcome anyone to improve upon the design, rules, or compression issues it poses. For traceability json {} are required, as well as the minimum required information to satisfy one of the functions.

About the IPFS format

Usually the json format is a key-value pair, you can add as much content as you like

Please note that features must trait typein this format

{ "name": "Bitcat #5",
 "description": "The first collection to adopt the new protocol of brc-721", 
"image": "ipfs://QmeyYPSz2887os4cxaucTMDaVgzR1wucXP3eaZYrX8Yavm/5.png",
"attributes": [ { "trait_type": "background", "value": "lightpurple" }, { "trait_type": "body", "value": "yellow" }, { "trait_type": "eyes", "value": "Fisheye" }, { "trait_type": "head", "value": "ToiletHat" }, { "trait_type": "mouse", "value": "Eatingfish" }, { "trait_type": "clthores", "value": "BlackCoat" } ] }

Deploy brc-721

The bitcat is still being mint, so you should check to see if the maximum number is exceeded when minting.

Stay tuned for official information from bitcat. They will update the index file later

https://twitter.com/bitcat_ord

{ 
"p": "brc-721",
"op": "deploy",
"tick": "bitcat",
"max": "10000",
"ipfs": "ipfs://QmbFAC5n9s65Ky96GqCrbRDVEHXxvE8vJShdbNWSD2GPTA"
}

Mint brc-721

Note: The id is determined by the inscription id of the deployer, please check the inscription id of the collection deployed by the deployer before Mint

{ 
  "p": "brc-721",
  "op": "mint",
  "tick": "bitcat",
  "id": "7954094",
  "ipfs": "ipfs://QmbFAC5n9s65Ky96GqCrbRDVEHXxvE8vJShdbNWSD2GPTA"
}

Last updated