Oli comments

Results 580 comments of

Oli

trafficstars

BIP 49/84 segwit receive addresses cannot be used when `btcwallet` is ran as a daemon

Yes, you're right. It looks like the functionality to generate SegWit addresses was only added to the internal DB but never exposed to the RPC interface.

Is there a way to verify (but not derive) the hardened child public key, given extended master public key

I don't know, probably not. Though I think the question might be better suited for the Bitcoin Stack Exchange: https://bitcoin.stackexchange.com/

Adds Batch client connection and async RPC calls to the bitcoind client

@Vib-UX Just FYI: I'm waiting with my next round of review since some of the changes requested in the `lnd` PR will probably require some changes here as well.

chain/neutrino: improve rescan locking

I tried running our itests against this PR (rebased onto current btcwallet master) and it looks like something's deadlocking now. The tests that do rescan don't even start properly, not...

parameter #2 'verbosity' must be type int (got bool)

What chain backend are you using? And what version?

parameter #2 'verbosity' must be type int (got bool)

No, I mean what software is running at `localhost:18334`, what version? Is it `btcd` version newer than `v0.20.1-beta`?

parameter #2 'verbosity' must be type int (got bool)

Yes, that's the problem. The current `btcwallet` master is not compatible with `btcd` master, only `btcd v0.20.1-beta`.

parameter #2 'verbosity' must be type int (got bool)

Try `master`.

Clarify misleading updatechanpolicy cli help

So the way I see it, we have two options here: 1. Use `string` flags to get rid of the misleading `(default: 0)` suffix and do all integer parsing manually....

Clarify misleading updatechanpolicy cli help

> WRT release notes, which release should I target with this MR? i have a conflict in the old release notes I need to resolve. I think `v0.16.0-beta` is still...