Leonardo L.
Leonardo L.
Adding another comment, I think we should try to enforce such conventions as much as possible on CI + GitHub features so we can set and forget, as by experience...
Is this still an issue ? Also, I haven't seen any suggestion/updates by dependabot in a while 🤔. FWIW, fedimint uses a separate `dependabot.yml` CI job AFAICT it works fine,...
superseded by https://github.com/bitcoindevkit/rust-esplora-client/pull/85
Most of the implementation is done, and it currently works on rust 1.70, also good to review and get inputs from it's being done. But it does not work with...
Sorry for taking so long, thanks for the suggestion. I think it can be a great addition alongside some other usage examples, and probably the `Used by` section on the...
@notmandatory @vladimirfomene Do you have any thoughts on this approach?
> As posted on discord: I'm not aware of any localhost tor testing frameworks , how do you currently do manual testing? for now it's probably enough to have detailed...
**update:** I've been working and using the https://blockstream.info/api for building the tests, but it seems flaky when connecting to it over Tor, some exit nodes work, and some receive a...
> Mhh, one caveat seems to be that Esplora on Signet seems to return `{}` for `fee-estimates`. However, arguably falling back to 1 sat/vbyte should still be part of the...
> It was decided initially to only include bitcoin::Amount at the API boundary. No doubt this makes for a better UX. Would it be worth replacing all satoshi amounts represented...