Tonight at nine o'clock, NoScription's first inscription token, $noss, will be minted again. You only need to prepare one of the following three wallets. No gas is required and zero investment is required.
Open the URL: https://noscription.org and link to the wallet. Follow the instructions and mint with one click. It is similar to the @atomicalsxyz pow mechanism. It requires the computing power of the computer. You can use the fingerprint browser to open multiple windows for operation.

简单介绍:
I just finished reading the official white paper and I think the design of this protocol is quite interesting.
There is an important role in the nostr protocol, the relay, which needs to be responsible for receiving, storing and forwarding user information. The information is not stored on the blockchain, so once the data on the relay is reset, the nostr information will will be lost. ,
In the Noscription protocol, all operations including deployment, casting, and transfer are events one by one. Similar to Brc20, all operations are recorded in the following json format.

The difference is that the protocol has an additional field. "tags" stores some information in this field, such as the id of the deployment event, the id of the previous event, the block number and block HASH ( The following will explain how to bind blocks), etc. Taking the casting event as an example, its rules are as follows:
1. Each casting event must store the id of the previous casting event in the tag
2. Assuming it is the first casting, store the ID of the deployment event of the token in the tag.
3. In the deployment event, you can specify a block number as the casting end time.
As shown in the figure below, "seq" in the deployment can specify the linked blockchain. Currently, it only supports arbitrum, and more chains will be supported in the future. "last_mint" specifies the ending block, which is what my title jokingly calls it. It is a "parasitic" protocol.

Seeing this, you may sigh, "Isn't this just a blockchain?" It is just a linked list based on the NOSTR protocol constructed using JSON that is not decentralized enough, because the data still needs the relay storage of nostr, and it may also be If it is lost, the official also recommends backing up a copy of the data after minting the tokens. This should also be a drawback of the protocol, which is not decentralized enough.
In general, I think the protocol design is quite interesting, and there are already supporting products to implement it, and it is zero-play, so it is worth playing around with. The above are personal thoughts. If there are any mistakes, please correct me.