Note: This article is from @lilyanna_btc Twitter, and Mars Finance is organized as follows:
Vindication is a new PR issued yesterday, with a new charm. It can be understood that the inscriptions that [according to the rules before Jubilee, they will be recognized as cursed inscriptions, and Jubilee will be directly engraved as normal inscriptions and given normal numbers] are labeled [Vindicated].
According to the current consensus reached by Domo, unisat, okx, etc., brc20 will ignore all Registered inscriptions and treat them as invalid, just like the previous curse inscriptions, in this sense, brc20 is equivalent to not being upgraded.
- Does Vindication identify and what exactly does it affect?
Batch inscribing using Pointer, which was previously subject to the cursed inscription setting, was not popularized, and was supposed to kill all sides after the Jubilee upgrade (but due to the latest vindication setting, it will not be accepted by brc20 for the time being).
There are multiple modes for this batch inscription, and the most advanced mode is same-sat batch. It is to engrave 1,000 or more inscriptions in a single transaction, on the same Satoshi.
https://docs.ordinals.com/guides/batch-inscribing.html
Separate-outputs can greatly save network fees, and all inscriptions can be completed in a block at the earliest;
Same-sat can not only save more network fees, but also further save the cost of reserved satoshi and reduce the problem of UTXO set bloat.
This is an interesting upgrade in itself, but according to the latest consensus of brc20, Vindicated's inscriptions will not be recognized for the time being.
This cost-saving and space-saving way of inscribed inscriptions has nothing to do with BRC20.
But as I said two days ago, other protocols that claim to optimize BRC20 have already started to lay out in advance. The CBRC20 protocol has been able to recognize and recognize non-i0 inscriptions ending in i1, i2, etc., and they are clearly ready to embrace Jubilee, which is one of the advantages of CBRC20's own protocol [greatly optimizing the cost of network fees].
-----------------
Some people say that this is a happy ending for all, and that brc20 has enough time to prepare for the new version and vindication when it is stable.
In fact, Jubilee was an incident that was made public in October, and some people even approached domo at the end of November to raise the question head-on. Now, more than a month later, less than a week ago, Jubilee came to advocate a long-term plan and postpone the upgrade in disguised form by patching, which is really a bit inconsiderate.