V2 API Checklist

[ahonn]

Todo

• UTXO Stack support
• Unified naming of interface parameters and response
  related discussion: feat: add type_hash to rgbpp assets routes #184 (comment)
  • feat: add type_hash to rgbpp assets routes #184 (comment)
  • feat: add type_hash to rgbpp assets routes #184 (comment)
• decentralized RGB++ CKB transaction queue
  To store the queue data in a decentralized manner, a few potential solutions include:
  1. The queue data could be pinned to IPFS (InterPlanetary File System)
  2. The queue could utilize a WebSocket PubSub (Publish-Subscribe) system between assets-api nodes to enable real-time communication between the queue and its subscribers.

[ShookLyngs]

Raising a related issue: Should the Bitcoin naming pattern be inherited in the v2 API?

For example, how should txid be named? Personally, I think it should be txId with a capitalized letter "I", but there are more similar namings in the Bitcoin world, e.g. scriptpubkey_asm, could be a hard work for the enrire toolchain to upgrade it.

[Flouse]

how should txid be named?

I think txid is OK.
ref: https://developer.bitcoin.org/reference/rpc/getrawtransaction.html