The Ordinals protocol came to prominence earlier this year, making it possible to create tokens and NFTs on Bitcoin, and at one point caused 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 BRC 69 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 protocol.
On July 3, BTC Eco Launchpad Luminex announced the launch of the BRC 69 standard. Through BRC 69, 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:
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 automatically rendering images on the Ordinals browser with no extra effort required.
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:
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.
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 BRC 69 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 referencing these features is only 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.