Script development for production

[RetricSu]

The current contracts folder contains the prototype for nostr-binding. To make it production-ready, it needs refactor and even changes in protocol(if needed).

Some improvements in my head:

Nostr lock Script

• witness is currently using simple array of Nostr Events. We need to use WitnessArgs layout for compatibility in CKB ecosystem.
• Serialzation for Nostr Event in witness is also using simple JSON which is not ideal for on-chain space and efficiency. Molecule might be a better option, but there are some trade offs:
  • JSON is very friendly for dApp developers in Nostr ecosystem while Molecule is so not. Some SDKs or Library should be provided to help client developers do the witness Event serilazation work with Molecule.
  • The verifycation for Nostr Event includes the calculating of Event_ID which also use JSON to serailaize the fileds of Event Structure.
• We record CKB transaction hash in the Nostr Event to unlock the CKB transaction. Nostr lock Script will check if the transaction hash match with the current transaction. Not sure if this is enough for sercurity. Maybe check Secp256k1 lock in CKB impl first and see what needs to be improved.
• ckb-auth is used in the script, however ckb-auth is not deployed in CKB testnet & mainnet, do we need to deploy it first or is there some available alternatives for ckb-auth?

Nostr binding Script

• witness layout and serialzation, same as the Nostr lock Script above.
• There seems no need to provide the binding event in witness since the binding script only needs to check the binding args includes valid Event_ID. This can help save the witness size which results in less transaction size.
• There is also a feedback that in order to keep compatible for nostr-binding assets in the CKB ecosystems, we should make the nostr-binding a sub-contract of Spore DOB so that we can use one type script code hash with different args instead of using a new type script code hash