Antoine Poinsot
Antoine Poinsot
> But this way of accessing the blockchain still requires more data downloading than another kind of light client, for example: electrum client. Right? Yes. > If not, I'm thinking...
More like adapting all our Bitcoin logic to support both bitcoind and Electrum: https://github.com/wizardsardine/liana/tree/master/src/bitcoin.
Don't know what's planned or not, but block filters would be a nice backend to have once BDK integrates it.
@edouardparis can i mark this as a good first issue or is it non-trivial? EDIT: Edouard says "no idea". So i'll keep it as is.
I think we already have an issue for checking the network of signing devices. -------- Original Message -------- On Feb 24, 2024, 10:04 AM, pythcoiner wrote: > [image.png (view on...
Just to give an update on this, it's being stuck because we had a disagreement (Kevin and i) about how this should be displayed to the user. I'm not sure...
It was tested and worked on Windows when it was implemented. I believe it is related to the upgrade to Bitcoin Core version 26.0, as pointed out by @jp1ac4 there...
If you build from source dropping this line before building might help getting more info. https://github.com/wizardsardine/liana/blob/501dce4372b5a5164b6c69ad9bf16056418218e2/gui/src/main.rs#L1
Edouard points out a couple endpoints need to be added or adapted on the API to be at feature parity with `lianad`.
Where does the GUI uses the genesis timestamp? The GUI does not connect to bitcoind itself, so if it needs the genesis timestamp it needs to be routed through lianad.