mempool.space API returns an incorrect/different value/order

[ahonn]

Description

The result from https://mempool.space/testnet/api/address/tb1qvn7ge67z3lh5x0u5ue69c7etp8kavlacku2vae/txs
does not seem to be sorted .
e.g.
71ec57841e64c30ae6c2b6776a3e573c24ec4648110d6a3c174940f8ed4f991e tx is not in first place

while https://mempool.space/testnet/address/tb1qvn7ge67z3lh5x0u5ue69c7etp8kavlacku2vae is good.

Related Issue

• electrs: return too many history entries when address has too many utxo/transactions record #89

[ahonn]

Also, the return of /testnet/api/v1/fees/recommended is inconsistent between different instances.

https://cell.mempool.space/testnet/api/v1/fees/recommended
https://mempool.space/testnet/api/v1/fees/recommended

[ahonn]

To resolve this issue, we need to upgrade to v2.5.7 and add a new env var BITCOIN_METHODS_USE_ELECTRS_BY_DEFAULT to env file:

BITCOIN_METHODS_USE_ELECTRS_BY_DEFAULT=getAddressTxs

cc @mfuuzy