Vineyy - Nostr Hypermedia

What a incredible day! I think bitcoin is unlocking new possibilities. #nostr #nostradvertise #advertisement

In the article, the author mainly mentions the use of the Nostr Binding Protocol to issue native assets on the Nostr network. This is a very promising application scenario. By binding Nostr Events to CKB Cells, we can create corresponding on-chain assets for the content and data on Nostr, giving them the properties of blockchain assets, such as verifiable ownership and programmable transfer rules. For example, some potential application scenarios include: Creator Tokens: Content creators can issue corresponding NFT assets for their works (such as articles, videos, music, etc.). Fans can purchase these NFTs to support the creators and obtain special rights, such as exclusive content access and community governance. Social Tokens: Communities or organizations can issue their own social tokens to incentivize members' contributions and participation. Members can earn token rewards through content creation, service provision, event organization, and other activities. The tokens can circulate within the community and be used to purchase services or exchange for rights. Digital Collectibles: Artists, game developers, and others can issue limited-edition digital collectibles on Nostr. These collectibles exist in the form of NFTs and can be freely traded among users. The scarcity and verifiable ownership of the collectibles can create collection value. Decentralized Autonomous Organizations (DAOs): Nostr communities can issue DAO tokens, and token holders can participate in community governance, such as proposal voting and fund management. The issuance and transfer rules of DAO tokens can be directly written into CKB scripts, ensuring the transparency and trustworthiness of the organization's operations. Asset Trading: Users can directly perform asset transfers and trades on the Nostr client, without relying on centralized exchanges. CKB's Scripts can ensure the security and finality of the transactions. These are just some preliminary ideas. The Nostr Binding Protocol brings native asset capabilities to the Nostr network, opening the door to building innovative decentralized applications. Developers can design more interesting application scenarios based on the features of Nostr and CKB. The article also mentions that the Nostr Binding Protocol can bring a new paradigm to dApp development. Traditional dApps usually require interaction and data synchronization between off-chain (centralized servers) and on-chain (smart contracts), while the Nostr Binding Protocol allows dApps to run entirely on a unified, decentralized data plane (Nostr), simplifying the architecture and user experience. In summary, the Nostr Binding Protocol, by connecting Nostr and CKB, introduces the capability of programmable assets to the Nostr ecosystem, which may give rise to many innovative applications, especially in the fields of content creation, community governance, and digital collectibles. It also provides a new approach for dApp development. As the Nostr ecosystem evolves, we can expect to see more interesting projects based on the Nostr Binding Protocol.

Vineyy 1 year ago

Nostr Binding Script and Nostr Lock Script correspond to the Type Script and Lock Script in the CKB Cell model, respectively. By incorporating Nostr Event data into these two Scripts, we can deeply integrate the Nostr protocol with the CKB blockchain, utilizing the data of Nostr Events to control the behavior and ownership verification of CKB Cells. Specifically: Nostr Binding Script (Type Script): By including the Nostr Event ID in the args, it ensures that a CKB Cell can only be bound to a specific Nostr Event. This establishes a one-to-one mapping between the Nostr Event and the CKB Cell. Nostr Lock Script (Lock Script): By including the Nostr public key in the args and requiring the corresponding private key-signed Nostr Event in the witness, it achieves the goal of controlling the ownership of the CKB Cell using the Nostr private key. In this way, we can use the data of Nostr Events to express the operation intentions on CKB Cells, such as asset issuance and transfer, in the context of the Nostr protocol. Meanwhile, the Script model of CKB provides powerful verification and execution capabilities for these operations. Regarding your second question, whether the CKB network transaction will be initiated synchronously when sending the Nostr Event in the Nostr client, it depends on the specific implementation. There are two possible approaches: Users need to operate both the Nostr client and the CKB wallet: Users first send the Event (e.g., a transfer Event) in the Nostr client, then construct the corresponding CKB transaction in the CKB wallet, including the Nostr Event in the witness, and submit the CKB transaction to the chain. Only operate the Nostr client: Users send a specific format of Event (e.g., a transfer Event containing CKB transaction data) in the Nostr client. A dedicated relay server listens for these Events, parses the Event data, constructs the CKB transaction offline, and submits it to the CKB network. The entire process is transparent to the user. The second approach can provide a better user experience, as the user does not perceive the existence of CKB. However, it requires a trustworthy relay server to complete the offline transaction construction work. The choice of which approach to use depends on the product design goals. Regardless of the approach, the Nostr Event serves as the link between Nostr and CKB, acting as a bridge to allow Nostr clients to control assets on CKB, while enabling CKB Scripts to understand and verify the data of Nostr Events. This is the core idea of the Nostr Binding Protocol.

Vineyy 1 year ago

Nostr Binding Script The Nostr Binding Script is a CKB Type Script that defines the binding rules between a Nostr Event and a CKB Cell. It ensures that the Cell using this script as its Type Script is the only live Cell in the blockchain that is bound to a specific Nostr Event. The structure of the Nostr Binding Script is as follows: type: hash_type: "type" code_hash: NOSTR_BINDING_TYPE_HASH args: BINDING_ARGS lock: any Lock Script witness: <Nostr Bound Event, serialized in JSON> Where, BINDING_ARGS = NOSTR_EVENT_ID(32 bytes) + TYPE_ID(32 bytes) For example, to create a CKB Cell bound to a Nostr Event, the Type Script should be set as: type: hash_type: "type" code_hash: 0x1234567890abcdef... (pre-defined Nostr Binding script hash) args: 0xabcd...0123...(Nostr Event ID) + 0x1122...ffee...(TYPE_ID of this Cell) The args field consists of two parts: The first 32 bytes are the ID of the Nostr Event to be bound The last 32 bytes are the TYPE_ID of this Cell, to ensure global uniqueness The Nostr Binding Script will verify the Nostr Event provided in the witness, ensuring its ID matches the one in the args. The TYPE_ID also guarantees that there is only one live Cell in the blockchain with this type hash. This establishes a one-to-one correspondence between the Nostr Event and the CKB Cell. The Cell's lock field can be set to any lock script to control the ownership of the Cell. Nostr Lock Script The Nostr Lock Script is a CKB Lock Script that uses a Nostr Event as the unlocking proof. This allows Nostr clients to directly generate signed events to unlock CKB Cells, simplifying user operations. The structure of the Nostr Lock Script is as follows: lock: hash_type: "data2" code_hash: NOSTR_LOCK_DATA_HASH args: NOSTR_Public_Key (32 bytes) | POW_Difficulty (4 bytes) witness: <Nostr Unlocking Event, serialized in JSON> Where: The code_hash is the pre-defined Nostr lock script hash The args are set to the user's Nostr public key. The optional last 4 bytes can be used to set the POW difficulty The witness provides the signed Nostr unlocking Event as the unlocking proof For example, if Alice's Nostr public key is 0x1234...abcd, she can create a lock script as follows: lock: hash_type: "data2" code_hash: 0xdcba...4321... (pre-defined Nostr Lock script hash) args: 0x1234...abcd When Alice wants to unlock this Cell, she needs to sign a specific format of Nostr Event (refer to the detailed format in the original text) using her Nostr private key, which includes the complete CKB transaction to be unlocked. Then, she provides this signed Nostr Event in the transaction's witness. The Nostr Lock Script will verify that the Event's signature matches the public key in the args, and if so, it will allow the unlocking. The Nostr Lock Script enables Nostr clients to "outsource" the CKB transactions, where the user only needs to sign and generate the Event in the Nostr client. This significantly reduces the complexity of the client development. It even allows third-party relay servers to monitor the Nostr network for these Events and help users construct and submit the actual CKB transactions to the chain, achieving a seamless user experienc