feat(backend): fill backend todos

[ShookLyngs]

TODOs

BitcoinAddress:

• satoshi: Calculates via the BitcoinApiService.getAddressTxsUtxo() API
• pendingSatoshi: Calculates via the BitcoinApiService.getAddressTxsUtxo() API
• transactionCount: Calculates via the added BitcoinApiService.getAddress() API
• transactions: Returns from the BitcoinApiService.getAddressTxs() API, the implementation comes with pagination and is different from the original design by @ahonn, because the resolver only returns up to 50 records; If the user wishes to load more, a afterTxid argument is available, like in the following code:

  {
    btcBlock(hashOrHeight: "0000000000000017b4ca3cf7748ffb59ba986670b288df26b3ea8cb850673cae") {
      miner {
        transactions(afterTxid: "14b6a01d23cb7046491653204a44d4896ce00896a5b630f38291c4d0c4919eb6") {
          txid
        }
      }
    }
  }

BitcoinBlock:

• miner: Returns the vout[0].address of the first transaction in a block
• feeRateRange: The calculation logic is written but we have trouble fetching from the data source; We can query the transactions of a block via the BitcoinApiService.getBlockTxs() API and summarize the results, but there are two issues blocking:
  1. The BitcoinApiService.getBlockTxs() API has pagination and only returns up to 25 records per request
     BitcoinBlockTransactionsLoader only returns the first 25 transactions of each block #9
  2. A block can contain hundreds of transactions, we could send tens of requests just for one block
• totalFee: Same issue as above

BitcoinOutput:

• address

TransactionService:

• getTransactionByBtcTxid: Need to find the isomorphic CKB transaction using a txid, this feature looks very similar to the implementaion in btc-assets-api#182

[vercel]

@ShookLyngs is attempting to deploy a commit to the Cell Studio Team on Vercel.

To accomplish this, @ShookLyngs needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.

[Flouse]

The result of https://mempool.space/docs/api/rest#get-block has a totalFees field.

[ShookLyngs]

I think the version we use don't have totalFees and feeRange in the response; See: https://cell.mempool.space/testnet/api/block/0000000000000017b4ca3cf7748ffb59ba986670b288df26b3ea8cb850673cae

[Flouse]

https://mempool.space/testnet/api/v1/block/0000000000000017b4ca3cf7748ffb59ba986670b288df26b3ea8cb850673cae contains the extra fields.

[ShookLyngs]

Refactored at: 502a512

[Flouse]

What about using the feeRange field in the response of https://mempool.space/docs/api/rest#get-block?

[Flouse]

#8 (comment)

[ShookLyngs]

Refactored at: 502a512

[ShookLyngs]

Conclusion after discussing with @Flouse:

1. We can try to fetch the list of the block's txid[], then fetch each transaction and save to Redis; After all transactions have been fetched, we can use the stored data for the calculation of totalFee and feeRateRange
2. We can leave the implementation of the TransactionService.getTransactionByBtcTxid() for later

[Flouse]

• We can try to fetch the list of the block's txid[], then fetch each transaction and save to Redis; After all transactions have been fetched, we can use the stored data for the calculation of totalFee and feeRateRange

or use https://mempool.space/testnet/api/v1/block/0000000000000017b4ca3cf7748ffb59ba986670b288df26b3ea8cb850673cae

[ShookLyngs]

The /v1/block/:hash route does contain the extras field. Now the totalFee and feeRateRange fields from the BitcoinBlockResolver have been refactored. Note that this field only exists in the mempool.space API, so it's expected to be undefined when the backend service is running in electrs mode.

{
  btcBlock(hashOrHeight: "0000000000000017b4ca3cf7748ffb59ba986670b288df26b3ea8cb850673cae") {
    totalFee
    feeRateRange {
      min
      max
    }
  }
}

[vercel]

@Flouse is attempting to deploy a commit to the Cell Studio Team on Vercel.

To accomplish this, @Flouse needs to request access to the Team.

Afterwards, an owner of the Team is required to accept their membership request.

If you're already a member of the respective Vercel Team, make sure that your Personal Vercel Account is connected to your GitHub account.