关于Runes协议及“公开铭刻"发行机制的拓展讨论

The author, the founder of the ecological infrastructure project, discussed with the founder of the agreement in the public topic. The two sides discussed how to expand the public engraving mechanism of the agreement, including whether to relax the requirement that the public engraving cannot be reserved, and pointed out that the runes that adopt the public engraving method do not have the right to manage, and put forward a set of distribution mechanism based on the cooperation of inscriptions and runes. Out of strong interest in the Bitcoin derivative asset agreement, the author combined the above one. I have written this article on the latest topics to explore the past of the agreement and similar asset issuance methods. I believe it will help you understand the bitcoin ecology. What is an agreement? The so-called agreement is an agreement to issue homogenized tokens on the bitcoin network. The homogenized token scheme reconstructed by the founder after the release of the scheme is based on the characteristics of Bitcoin. The overall design idea is very simple. It is worth mentioning that the agreement is planned to halve the height of the block in Bitcoin. That is to say, the main network was launched in late April this year, and now the protocol is still in the process of optimization and version iteration. Before briefly introducing the principle of popular science, let's quickly understand the context and what the so-called public inscription represents. The proponent did not want to make a homogeneous token agreement at the beginning, and issued the agreement as early as January, with the intention of permanently winding the data. Simply put, metadata is recorded in the witness data of bitcoin transactions like inscriptions, mainly including digital signature information. You can engrave any form of content, such as text and images, on the designated cong. Then the wheel of history begins to turn. On the basis of this typical distribution agreement, anonymous developers circuitously come up with a set of standards for issuing homogeneous tokens, that is, stipulate a unified format and attribute names for the derivative assets data that need to be uploaded to the bitcoin chain in an inscription way, and then analyze and track this information through the indexer to show the token phase. The key issue of the closed wallet account and the amount of assets depends on this bitcoin inscription agreement, so it becomes similar to the casting process in the initial issue mechanism, and naturally has the characteristics of first come, first served. It is completely different from the fact that when the assets of Ethereum are issued, the project party deploys the assets contract first, defines the asset allocation mechanism, and the official can control the disk as he wants. This characteristic makes most people have a fair chance to participate in the initial issue of homogenized tokens. Everyone has no reservation and no lock. Being able to participate in the initial issuance of assets soon brought about a boom in the issuance of derivative assets on the bitcoin chain, and even directly started this bull market. Therefore, it can be seen that the issuance method of public inscription, which we focus on today, is very important for the agreement, but it also brings many problems. Every operation of assets has to initiate a specific transaction on the bitcoin chain. With the popularity of assets, the bitcoin data set has also expanded rapidly, which makes the core developers not only oppose the public questioning. Even more, the assets issued based on it are not recognized, but the popularity makes him feel that although all the tokens are scams and gimmicks, these things will still not disappear like casinos, leaving too many traces on the bitcoin chain, which has brought a burden on the bitcoin node. However, if someone proposes a set of asset agreements that can reduce the burden on the uplink data, it may alleviate the problems, so he decides to build a better homogeneous token agreement for Bitcoin, and then he will issue it on June. From a technical point of view, the protocol is based on bitcoin and additional information, and the trigger of each transaction should include the digital signature information generated under the chain. We can carry the message protocol with a specific format in the signature information and mark the specific messages through the operation code. These specific messages are the information related to asset changes, which has many advantages compared with the protocol, the most important of which is that the transaction steps are simplified and unnecessary useless, which can better reduce the burden on bitcoin nodes. A transfer transaction outside only supports one recipient and one token, but supports simultaneous transfer to multiple recipients, and the storage and index of transferable multi-token assets are simpler. The data is stored in the data of a specific transaction in a format, and based on the account model, the balance of assets is associated with the specified account, while the agreed data is stored in the field of a specific transaction. The recording method of assets can be directly and isomorphically bound to the bitcoin chain, and only verification is needed when confirming a person's asset status. Although this person has the special property of being bound to assets, he still needs to trace back some information to complete the calculation, but he doesn't need to scan the complete set on the bitcoin chain like that. This lightweight way is more friendly to data indexing and compatible with the functional extension layer. The design based on makes it better compatible with the functional extension layer based on the same structure. The above functional extension layer can provide smart contract scenarios through similar isomorphic binding. After briefly talking about the technology, we will return to the issue mechanism we talked about at the beginning of this article. Runes are designed with two sets of distribution methods, namely, fixed total amount and public inscription. The fixed total amount means that the issuer directly engraves all the runes and then distributes them. The public inscription is to set parameters for the distribution method of runes, such as indicating the height of a block or the time stamp, how much assets the user has in a time period that meets the rules, and finally the total amount of the runes is how much. The two distribution methods correspond to completely different scenes and mechanisms. In the following, we only talk about public inscription, which actually starts from the topic. At first, this topic was discussed and recognized, and the specific contents are as follows: at present, the issuer of the public offering project can't reserve runes in advance, which limits the opportunity for the project to design an excellent economic model of the general certificate. Please check the previous one. I am considering relaxing this requirement and allowing the issuer to arrange runes in a reasonable way when issuing, even beyond the set range of parameters. If so, the design-related information will be displayed very prominently on the details page of runes. Is it possible to design a mechanism for multiple issuance? If there are two rounds of public inscription runes, and then different parameters are set for each issue, I don't like this, because runes are not authorized by managers in essence and should not be in the hands of a single entity with special authority, but you can add an inscription when issuing runes and then issue new runes on the basis of this inscription, so that the runes issued twice are the same asset. Of course, you can also use pre-excavation and then issue them by other distribution methods. If future functions can be successfully started, you don't need agreement support, and you can directly issue them in advance. 比特币今日价格行情网_okx交易所app_永续合约_比特币怎么买卖交易_虚拟币交易所平台

注册有任何问题请添加 微信：MVIP619 拉你进入群

文章转载注明 网址：https://netpsp.com/?id=60176