request: frontend needed resolvers/queries

[ShookLyngs]

Background

After #14 and #15, there are still requests from the frontend side:

• Resolvers: fields yet to be implemented
• Queries: frontend needed queries, new APIs

Resolvers

Bitcoin:

• transactionsCountIn24Hours

BitcoinTransaction:

• ckbTransaction: if it's a RGB++ transaction
• udtInfo: or extraInfo?

use rgbppTransaction field

Ckb:

• fees: low/average/fast fee rates, may need to be renamed; is this field needed?

CkbAddress:

• unconfirmedShannon
• rgbppCellsCount

RgbppStatistic:

• holdersCount

Queries

• Query the latest RGB++ L1 transactions
• Query the latest RGB++ L2 transactions
• Query a ranking of popular RGB++ assets

[ahonn]

I think we need to discuss BitcoinModule RGB++ related fields.

My suggestion is to ensure that the BitcoinModule contains only Bitcoin-related data and that RGB++ related data should be accessed through queries prefixed by rgbpp.
For example, the 'rgbppTransaction' function should support the querying of data by passing in btcTxid or ckbTxHash.

[ShookLyngs]

ensure that the BitcoinModule contains only Bitcoin-related data

Currently the following fields are included or planned to be included in non-rgbpp modules:

• BitcoinAddress
  • rgbppUtxosCount
  • rgbppUtxos
• CkbAddress
  • rgbppCellsCount
  • rgbppCells
• BitcoinTransaction
  • ckbTransaction
  • udtInfo (related?)