Original Author: Cookie, Rhythm BlockBeats
High issuance costs have been one of the reasons affecting the Bitcoin NFT market. Although more BRC-XXX protocols have appeared on the market recently, the author thinks that BRC-1155 and BRC-XXX have achieved a better balance between maintaining the "authentic flavor" of Bitcoin NFT and reducing the cost of issuance. GBRC-721.
first level title
BRC-1155: Possibility to realize Bitcoin "Open Edition"
A few months ago, the "Open Edition" art NFT of ERC-1155 on Ethereum became the "small main line" of the market for a period of time. The improvement of its infrastructure and the continuous progress of "art gamification" finally made the "Open Edition" has successfully attracted the attention of the market.
There are pain points in implementing "Open Edition" on Bitcoin, especially when the NFT content type is a large-sized animation, audio or even video file, the high burning cost can only be borne by the creator or the collector. The development of "Open Edition" on Bitcoin is almost hopeless - creators resist publishing "Open Edition" artwork on Bitcoin due to the need to take risks up front (paying high burning costs and not being able to sell), collectors Also resist participation because of the high cost of recording.
BRC-20 + ERC-1155 = BRC-1155
To make the development of "Open Edition" on Bitcoin possible, the cost of both parties must be reduced at the same time. The core idea of BRC-1155 is that if we can accept a JSON code inscription like BRC-20 to confirm ownership of the same artwork as a way of owning an artwork stored on Bitcoin, then we will There is no need to spend several times or even more Gas to repeatedly burn an image/audio/video/other file. It only needs to spend a very low Gas to obtain a "certificate", and then let the index follow the chain pointed to by the inscription of the "certificate" Add the inscription to render the corresponding content.
The cost of creators and collectors is greatly reduced. For creators, it is only necessary to burn an image/audio/video/other file inscription as the pointed "original version", and at the same time burn another "deployment" inscription.
"Deployment" inscription example
The meanings of the keywords in the above "deployment" inscription example are as follows:
"p": protocol type. A keyword that must be included, which defines the operation based on the BRC-1155 protocol, and helps the index to identify and process BRC-1155 events.
"op": event type. A keyword that must be included, which defines the event type, be it Deploy, Mint, Burn, or Fractionalize.
"abbrev": Abbreviation for BRC-1155 series name. A keyword that must be included, which defines the abbreviation of the BRC-1155 series name, and cannot exceed 10 characters.
"inscription": index pointing to. A keyword that must be included, which defines which inscription on the chain (according to the serial number of the inscription) the BRC-1155 series will obtain for content rendering. For example, if you want to render the content of Inscription #123, then fill in "123".In addition, creators can also add some other keywords to the "deployment" inscription to realize the functions of determining the total supply, the number of "credentials" that each Mint inscription can represent, and adding additional description information. (For details, see）
BRC-1155 Manual
For collectors, they only need to burn a "casting" inscription to obtain the ownership of the corresponding inscription on the chain:
Example of "Forged" inscription. It can be seen that the size of the burned text is only 81 bytes, and the cost is greatly reduced
Not only lowers the cost of "Open Edition", BRC-1155 will also provide "Burn burning" function to realize "art gamification" gameplay. At present, the developer of BRC-1155 @ivantkf has established the BRC-1155 Foundation in cooperation with the Bitcoin NFT project Bitcoin Pizzas and PixelBirds Sparrow, and the improvement of indexing and more functions is in progress. Bitcoin Pizzas and PixelBirds Sparrow have also used BRC-1155 to complete the "Open Edition" project release attempt.
first level title
GBRC-721: Transfer each feature to Base 64 for on-chain storage, front-end assembly
Some BRC-XXX protocols use IPFS to point to and complete file rendering, which is considered to destroy the "original flavor" of Bitcoin NFT. GBRC-721 uses an ingenious solution to maintain the full chain storage characteristics of Bitcoin NFT - convert the image file into a Base 64 string and write it into the "deployment" inscription and burn it on the chain, and the front end reads "casting The Base 64 strings of each feature stored in the "deployment" inscription pointed to by the inscription are converted into pictures and combined into a complete image.
Example of "Deployment" inscription. It can be seen that each characteristic picture is converted into a Base 64 string and written in the "deployment" inscription, such as the blue background and the antenna of the robot. Burning the "deployment" inscription is equivalent to storing the pictures of each feature on the Bitcoin chain
first level title
epilogue
epilogue
Both BRC-1155 and GBRC-721 have shown us a new idea - BRC-20's JSON code-like inscriptions can not only be used for asset issuance, but also make the gameplay of Bitcoin NFT more diverse. At the same time, since BRC-1155 and GBRC-721 produce Mint text in JSON code, if you participate in the casting of related projects, what you get will not be pictures, but text like BRC-20 Token Type inscription.
