bit.network.fees currently has one fee-source URL:
https://mempool.space/api/v1/fees/recommended
Would you be open to a small PR that keeps that default, but lets applications either configure the fee URL or use a tiny fallback list of mempool-compatible providers?
I work on Satoshi API, the Bitcoin fee API at bitcoinsapi.com. It exposes the same bucket shape for this use case:
https://bitcoinsapi.com/api/v1/compat/mempool/fees/recommended
That returns fastestFee, halfHourFee, hourFee, economyFee, and minimumFee, so bit would not need a new response parser if the maintainer preference is simply “compatible fallback source.”
I did not open a PR first because bit is a library and the right API surface matters. Happy to send whichever small shape you prefer: configurable URL, fallback list, or docs-only example.
bit.network.feescurrently has one fee-source URL:https://mempool.space/api/v1/fees/recommendedWould you be open to a small PR that keeps that default, but lets applications either configure the fee URL or use a tiny fallback list of mempool-compatible providers?
I work on Satoshi API, the Bitcoin fee API at bitcoinsapi.com. It exposes the same bucket shape for this use case:
https://bitcoinsapi.com/api/v1/compat/mempool/fees/recommendedThat returns
fastestFee,halfHourFee,hourFee,economyFee, andminimumFee, sobitwould not need a new response parser if the maintainer preference is simply “compatible fallback source.”I did not open a PR first because
bitis a library and the right API surface matters. Happy to send whichever small shape you prefer: configurable URL, fallback list, or docs-only example.