"EIP4844" on Bitcoin: How BRC-69 Reduced Inscription Costs by Over 90%?

Original: "A detailed explanation of BRC69: How to reduce the cost of inscriptions by more than 90%?" "

Author: Jessica

Ordinals Ordinals Ordinals is a numbering scheme for satoshis that allows individual sats to be tracked and transmitted. These figures are called Ordinals. Satoshis are numbered in the order in which they were mined and transferred from transaction inputs to transaction outputs, first in, first out. Both the numbering scheme and the transfer scheme depend on order, the numbering scheme depends on the order of mining, and the transfer scheme depends on the order of transaction inputs and outputs. See more The protocol came to the fore earlier this year, enabling the creation of tokens and NFTs on top of bitcoin, at one point causing a spike in transactions and fees on the bitcoin network.

With the promotion of the Ordinals protocol, more and more users write data into the non-homogeneous Ordinals collection on Bitcoin. This increased usage leads to increased demand for Bitcoin block space, which in turn leads to higher Bitcoin network fees. In order to continue to encourage creators to publish innovative ideas on the Bitcoin blockchain, following 12 "new generation protocols", BTC Eco Launchpad Luminex released the BRC69 standard on GitHub, which uses recursive inscriptions to optimize the cost of inscriptions. Odaily Planet Daily will analyze its principles, characteristics, casting and deployment operations, aiming to help readers fully understand this new agreement.

Reduce the cost of inscriptions by more than 90% in four steps

On July 3, BTC Eco Launchpad Luminex announced the launch of the BRC69 standard. Through BRC69, the cost of inscriptions on Ordinals collections can be reduced by more than 90%. It depends on the size of the initial collection and network charges. This process consists of four steps:

• Write characteristic pictures on the chain;
• Write BRC69 collection deployment JSON on the chain;
• Write BRC69 collection compiler Java on the chain;
• On-chain inscription of BRC69 assets with minting operations can all be done without the need for an external indexer as long as the creator of the collection publishes an official inscription manifest for their collection (which is currently required). Additionally, all frontends that have implemented recursive writing will automatically render images without additional steps.

This standard paves the way for more interesting on-chain features, such as pre-public set releases and on-chain reveals. This is achieved by rendering images automatically and without additional action on the Ordinals browser.

How to deploy BRC-69

Once the image containing the characteristics of the collection is written to the chain, we can write the collection deploy JSON in the deploy operation.

The deploy action is a JSON/text inscription containing general information about the collection and an array of feature inscription IDs. Deploy inscriptions as a reference and authoritative source for features.

Here is an example of a collection deployment JSON:

How to compile BRC69

The compile operation stores the final asset's rendering logic in a Java engraving. The compile inscription is a recursive inscription that points to the deployment inscription to get the inscription ID for the feature and finally render the asset. The logic of compiling and writing can be customized as needed to meet the collection of more specific rendering functions.

How to mint BRC69

The minting operation uses an HTML type inscription that stores the feature index used to generate the final asset and points to the compile inscription on a single line. This approach enables any front-end with recursive writing capabilities to automatically render images using data written on-chain.

Here is an example of a casting operation:

Implementing the BRC69 standard will improve the efficient use of Bitcoin block space. Since unique feature images are only inscribed once in a deployment transaction, the asset is composed of an HTML file, and the file that references these features is just one line, about 150 bytes. Any frontend with a recursive glyph implementation can use the deployed glyph on-chain to render images without additional steps.