Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has quit [Remote host closed the connection]
c_arc has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 265 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 252 seconds]
AaronvanW has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has quit [Ping timeout: 265 seconds]
c_arc has joined #bitcoin-core-dev
AaronvanW has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
AaronvanW has quit [Quit: Leaving...]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
mersible has quit [Quit: Leaving]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Guest16 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Guest16 has quit [Quit: Client closed]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
cmirror has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc_ has joined #bitcoin-core-dev
c_arc has quit [Remote host closed the connection]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
earnestly has quit [Ping timeout: 245 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
grettke has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
c_arc has joined #bitcoin-core-dev
grettke has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] Peterblanco021091 opened pull request #23023: Update and rename contrib/seeds/suspicious_hosts.txt to contrib/semil… (master...patch-1) https://github.com/bitcoin/bitcoin/pull/23023
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] fanquake closed pull request #23023: Update and rename contrib/seeds/suspicious_hosts.txt to contrib/semil… (master...patch-1) https://github.com/bitcoin/bitcoin/pull/23023
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
sdfgsdfg has joined #bitcoin-core-dev
sdfgsdfg has quit [Changing host]
sdfgsdfg has joined #bitcoin-core-dev
Talkless has joined #bitcoin-core-dev
Talkless has quit [Client Quit]
c_arc has joined #bitcoin-core-dev
vysn has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<kallewoof>
harding: thanks for the heads up. will look into it.
c_arc has joined #bitcoin-core-dev
bitdex has quit [Ping timeout: 276 seconds]
bitdex has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Guyver2 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
kappa has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
bitcoin/master 357f0c7 Hennadii Stepanov: ci: Enable more functional tests on Windows MSVC task
<bitcoin-git>
bitcoin/master f559326 Hennadii Stepanov: qa: Fix "RuntimeError: Event loop is closed" on Windows
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
sipsorcery has quit [Ping timeout: 240 seconds]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<shiza>
Can anything in Bitcoin Core transform a legacy wallet into a descriptors wallet in a single step?
<shiza>
"Legacy wallets cannot provide bech32m addresses"
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] fanquake closed pull request #22987: qa: Fix "RuntimeError: Event loop is closed" on Windows (master...210915-loop) https://github.com/bitcoin/bitcoin/pull/22987
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
c_arc has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
<shiza>
It's showing that on bitcoin-cli's output (and error code -8) upong requesting it getnewaddress of 'bech32m' type (in what seems an API feature unpromised by `help getnewaddress`, but somehow treated because the error message doesn't just tell 'Unknown address type'.)
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<shiza>
There is something about it on stack exchange, but IDK if that post's a little vague for me.
Guestghjgjh has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
Henrik has joined #bitcoin-core-dev
bomb-on has quit [Read error: Connection reset by peer]
earnestly has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
sipsorcery has quit [Ping timeout: 268 seconds]
Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
Henrik has joined #bitcoin-core-dev
sdfgsdfg has quit [Read error: Connection reset by peer]
sdfgsdfg has joined #bitcoin-core-dev
Guestghjgjh has quit [Quit: Client closed]
sipsorcery has joined #bitcoin-core-dev
Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
jespada has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
Henrik has joined #bitcoin-core-dev
Guyver2 has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
provoostenator has joined #bitcoin-core-dev
Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
belcher has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
vysn has joined #bitcoin-core-dev
<achow101>
shiza: #19602 converts a legacy wallet to a descriptor wallet, but only insofar as generating descriptors that represent all of the addresses the legacy wallet could create and importing them into a new descriptor wallet
<achow101>
it would not allow you to create bech32m addresess using the keys from the legacy wallet
<achow101>
it looks like we forgot to update the RPC help when adding bech32m as an address type
c_arc has joined #bitcoin-core-dev
<shiza>
I'm using a legacy wallet, if it wasn't clear. For that wallet the RPC help is good as is.
<shiza>
Hah thanks for that link, interesting PR.
c_arc has joined #bitcoin-core-dev
Guyver2_ has joined #bitcoin-core-dev
Guyver2 has quit [Ping timeout: 240 seconds]
Guyver2_ is now known as Guyver2
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<shiza>
On an empty wallet it'll give me error code -12 "no bech32m addresses available".
<shiza>
An empty new wallet 169900 with "descriptors true".
<shiza>
Anyway, I don't need that.
<shiza>
But I mean, you are kinda right on your point I suppose.
<shiza>
To me it's starting to look like a forgotten change.
c_arc has joined #bitcoin-core-dev
<achow101>
currently descriptor wallets will not be created with a descriptor for bech32m addresses
<achow101>
this is because the only descriptor that would create such addresses are tr(), and those are not safe to use until taproot activates in november
<shiza>
Oh, I thought bech32m was already activated before taproot, because don't they say walletexplorer already understands bech32m.
<shiza>
Oh you say bech32m is already active but not mainstream available to core clients but as some advanced feature.
<sipa>
you can manually construct a wallet with a tr() descriptor, for networks where taproot is active (signet,regtest,testnet)
Guyver2_ has joined #bitcoin-core-dev
<shiza>
I understand how that fits with the walletexplorer claim.
Guyver2 has quit [Ping timeout: 260 seconds]
Guyver2_ is now known as Guyver2
<shiza>
How do you develop such a beast as taproot without breaking testnet? By using private short lived testnets?
Henrik has joined #bitcoin-core-dev
sipsorcery has joined #bitcoin-core-dev
<sipa>
i'd say that's the easy part - the ways in which the validation rules are affected by taproot are very isolated (oversimplified, it's just "if (scriptpubkey being spent looks like taproot) { if (!taproot_valid()) return false; }")
<sipa>
segwit was far more invasive, with impact on much more than just script validity rules
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
<shiza>
So basically you can develop and make all the silly mistakes and all the shit your client is launching is denied by the network so it doesn't matter.
<shiza>
But you still need to intimately connect a couple peers at some point early in development. Do you then just tweak p2p so you both know you'll be in a one leap from each other.
<sipa>
regtest is basically that
<sipa>
the test framework automatically spins up a bunch of nodes and connects them to each other
<sipa>
with a fresh chain
c_arc has joined #bitcoin-core-dev
<shiza>
That's a lot easier way to understanding it than bitcoin.it/regression_test_mode!
<sipa>
that wiki page probably predates the test framework...
<shiza>
Oh last edited 2014. How bad.
<sipa>
regtest = just a mode to run bitcoind in so that it works not with the real chain, but with a private super-easy-to-mine chain
<sipa>
the functional test framework uses that mode
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
bitcoin-git has joined #bitcoin-core-dev
<bitcoin-git>
[bitcoin] luke-jr opened pull request #23027: Bugfix: Skip tests for tools not being built (master...bugfix_util_test_config) https://github.com/bitcoin/bitcoin/pull/23027
bitcoin-git has left #bitcoin-core-dev [#bitcoin-core-dev]
c_arc has joined #bitcoin-core-dev
Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]
sipsorcery has quit [Ping timeout: 268 seconds]
Henrik has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
c_arc has joined #bitcoin-core-dev
gnaf has quit [Quit: Konversation terminated!]
c_arc has joined #bitcoin-core-dev
Henrik has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]