A Comprehensive Explanation of BRC69: How to Reduce Inscription Costs by Over 90%?
Reducing BRC69 Inscription Costs by More Than 90%: A Comprehensive Guide
Author: Jessica, Odaily Star Daily
Ordinals is a numbering scheme for satoshis that allows for tracking and transfer of individual sats. These numbers are called Ordinals. Satoshis are numbered in the order they are mined and move from transaction inputs to transaction outputs, first in, first out. Both the numbering scheme and transfer scheme rely on order, with the numbering scheme relying on the order of mining and the transfer scheme relying on the order of transaction inputs and outputs. See more The protocol emerged earlier this year, making it possible to create tokens and NFTs on top of Bitcoin and leading to a surge in transactions and fees on the Bitcoin network.
With the increasing adoption of the Ordinals protocol, more and more users are engraving data into non-fungible Ordinals collections on Bitcoin. This increased usage has led to an increase in demand for Bitcoin block space, which in turn has led to an increase in Bitcoin network fees. In order to continue to encourage creators to publish innovative ideas on the Bitcoin blockchain, following the 12 “New Generation Protocols,” BTC ecology LaunchBlockingd Luminex released the BRC69 standard on GitHub, which uses recursive inscriptions to optimize inscribing costs. This article will analyze its principles, characteristics, and casting and deployment operations to help readers fully understand this new protocol.
Reduce Inscription Costs by Over 90% in Four Steps
On July 3rd, BTC ecology LaunchBlockingd Luminex announced the launch of the BRC69 standard, which can reduce the inscription cost of Ordinals collections by over 90%. This depends on the initial size of the collection and network fees. The process involves four steps:
-
Engrave the characteristic picture on the chain;
-
Engrave the BRC69 collection deployment JSON on the chain;
-
Engrave the BRC69 collection compiler JavaScript on the chain;
-
Engrave the BRC69 asset with casting operation on the chain As long as the creator of the collection releases the official inscription list of the collection (currently required), all of these processes can be performed without the need for an external indexer. In addition, all front-end interfaces that have implemented recursive inscription will automatically render images without additional steps.
This standard paves the way for more interesting on-chain functionality, such as pre-released collection publishing and on-chain revelation. This goal is achieved by automatically and without additional steps rendering images on the Ordinals browser.
How to Deploy BRC-69
Once an image containing collection features is etched onto the chain, we can etch collection deployment JSON in the deployment operation.
The deployment operation is a JSON/text etching that contains the regular information of the collection as well as the feature etching ID array. The deployment etching serves as a reference and authoritative source for features.
Here is an example of collection deployment JSON:
How to Compile BRC69
The compile operation stores the rendering logic of the final asset in a JavaScript etching. The compile etching is a recursive etching that points to the deployment etching to obtain the feature etching ID and ultimately renders the asset. The logic of the compile etching can be customized as needed to meet the specific rendering capabilities of the collection.
How to Cast BRC69
The casting operation uses an HTML type etching, which stores the feature index used to generate the final asset and points to the compile etching in a single line. This way, any frontend with recursive etching functionality can automatically render images using chain etchings data.
Implementing the BRC69 standard will improve the utilization efficiency of the Bitcoin block space. Since the unique feature images are only etched once in the deployment transaction, the asset consists of an HTML file, and the file referencing these features only has one line, about 150 bytes. Any frontend with recursive etching implementation can use the etchings deployed on the chain to render images without additional steps.
