V2 API Checklist - Githubissues

utxostack / btc-assets-api

Bitcoin/RGB++ Assets API

https://api.rgbpp.io/docs

Apache License 2.0

2 stars 1 forks source link

V2 API Checklist #185

Open ahonn opened 2 months ago

ahonn commented 2 months ago

Todo

[ ] UTXO Stack support
[ ] Unified naming of interface parameters and response related discussion: https://github.com/ckb-cell/btc-assets-api/pull/184#discussion_r1664944321
- [ ] https://github.com/ckb-cell/btc-assets-api/pull/184#discussion_r1664987102
- [x] https://github.com/ckb-cell/btc-assets-api/pull/184#discussion_r1664991221
[ ] 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 commented 2 months ago

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 commented 2 months ago

how should txid be named?

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