feat(electrum): add custom authentication support via ConfigBuilder#2096
feat(electrum): add custom authentication support via ConfigBuilder#2096EddieHouston wants to merge 1 commit intobitcoindevkit:masterfrom
Conversation
|
NACK This is a lot of description/documentation for a "convenient method" which saves 1 line of code. |
559494e to
a9d1fb9
Compare
a9d1fb9 to
174ff05
Compare
Good feedback, I trimmed the noise down. |
|
@EddieHouston this PR has nothing to do with using electrum behind gateways which require authentication. This is adding a convenience method that saves one line of code. I'm not sure I see the value of this? |
Reasonable point, guess the value was the idea of helping people find out that using auth was possible. But you are right... and I don't see any other places this is done in the codebase. I'll just focus on bitcoindevkit/rust-electrum-client#194 and if needed perhaps later we could add something to the example_electrum to show auth usage if it makes sense. Thanks for your feedback and time 👍 |
Description
This PR enables connections to Electrum servers behind API gateways that require authentication (e.g., JWT tokens, Bearer tokens, API keys, Basic auth, or custom authorization schemes).
What's being added:
BdkElectrumClient::from_config()constructor that accepts customConfigfor authorization and other settingsNotes to the reviewers
Dependency: This PR requires authorization provider support from
rust-electrum-client. The feature is not yet in the published 0.24.0 release. Options:rust-electrum-clientPR is merged and releasedThis feature exposes the existing authorization capability from
electrum-clientthrough a new convenience constructorThe
from_config()method is only implemented forBdkElectrumClient<electrum_client::Client>(not the genericElectrumApitrait) since it needs to construct a concrete clientChangelog notice
Added:
BdkElectrumClient::from_config()Checklists
All Submissions:
New Features:
Bugfixes: