--- Log opened Sun Oct 24 00:00:12 2021
01:26 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-dev
01:34 -!- earnestly [~earnest@user/earnestly] has joined #bitcoin-core-dev
01:41 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 244 seconds]
01:52 -!- belcher [~belcher@user/belcher] has joined #bitcoin-core-dev
02:17 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev
03:08 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
03:12 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
03:38 -!- Guest93 [~Guest93@131.red-79-150-151.dynamicip.rima-tde.net] has joined #bitcoin-core-dev
03:39 -!- Guest93 [~Guest93@131.red-79-150-151.dynamicip.rima-tde.net] has quit [Client Quit]
03:55 -!- smartin [~Icedove@88.135.18.171] has joined #bitcoin-core-dev
04:07 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
04:07 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Client Quit]
04:09 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
04:15 -!- bomb-on [~bomb-on@194.144.47.113] has joined #bitcoin-core-dev
04:44 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:2477:6740:a868:bcf7] has joined #bitcoin-core-dev
04:48 -!- masta`` [~oyster@user/masta/x-2645138] has joined #bitcoin-core-dev
04:48 -!- masta_ [~oyster@user/masta/x-2645138] has joined #bitcoin-core-dev
04:55 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:2477:6740:a868:bcf7] has quit [Quit: Client closed]
04:55 -!- sirdigby727 [uid523338@lymington.irccloud.com] has quit [Quit: Connection closed for inactivity]
04:55 -!- csknk [~csknk@88.87.164.26] has joined #bitcoin-core-dev
05:00 -!- csknk [~csknk@88.87.164.26] has quit [Quit: leaving]
05:00 -!- csknk [~csknk@88.87.164.26] has joined #bitcoin-core-dev
05:25 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Remote host closed the connection]
05:26 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
05:36 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Quit: Leaving...]
05:36 -!- masta_ [~oyster@user/masta/x-2645138] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
06:14 -!- nanotube [~nanotube@user/nanotube] has quit [Ping timeout: 258 seconds]
06:34 -!- dougefish [~dougefish@5.29.58.227] has quit [Quit: dougefish]
06:34 -!- dougefish [~dougefish@5.29.58.227] has joined #bitcoin-core-dev
06:34 -!- dougefish_ [~dougefish@5.29.58.227] has joined #bitcoin-core-dev
06:36 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
06:42 -!- guest3456 [~guest3456@c-73-55-111-182.hsd1.fl.comcast.net] has joined #bitcoin-core-dev
06:43 < guest3456> so at some point i followed a guide to move my datadir to my external drive, and then i believe i did a link to keep the chainstate dir on my internal ssd
06:44 < guest3456> actually i believe it was an option in the installer
06:44 < guest3456> but i'm now trying to upgrade to 22.0 but the installer is not giving me any choices about datadir, only the full install dir
06:44 < guest3456> will something get messed up
06:51 < hebasto> guest3456: provided data are not enough to give you a 100% working solution, but generally it is more reliable to move into an external drive a blocks dir only; it is easy to achieve  by placing `blocksdir="path-to-external-drive/new-blocks-dir` into your `bitcoin.conf`
06:52 < hebasto> guest3456: anyway, https://bitcoin.stackexchange.com/ is a better place to ask such questions
06:54 < guest3456> thank you sir, ill keep that in mind if i decide to rearrange the install
06:55 < guest3456> anyway i just installed on top, choosing the same main dir on my ssd, and it looks like everything worked silently
07:14 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
07:25 < bitcoin-git> [bitcoin] hebasto opened pull request #23345: build: Drop unneeded dependencies for bitcoin-wallet tool (master...211024-bw-deps) https://github.com/bitcoin/bitcoin/pull/23345
07:25 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
07:33 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has joined #bitcoin-core-dev
07:58 -!- guest3456 [~guest3456@c-73-55-111-182.hsd1.fl.comcast.net] has quit [Ping timeout: 256 seconds]
08:20 -!- Guest58 [~Guest58@27.18.3.139] has joined #bitcoin-core-dev
08:21 -!- Guest58 [~Guest58@27.18.3.139] has quit [Client Quit]
08:32 -!- white5moke [~white5mok@ip72-219-109-30.oc.oc.cox.net] has joined #bitcoin-core-dev
09:14 -!- gnaf [~gnaf@86-91-224-60.opennet.kpn.net] has quit [Quit: Konversation terminated!]
09:21 -!- gnaf [~gnaf@86-91-224-60.opennet.kpn.net] has joined #bitcoin-core-dev
09:31 -!- Guest10 [~Guest10@69.89.141.88.rev.sfr.net] has joined #bitcoin-core-dev
09:32 -!- Guest10 [~Guest10@69.89.141.88.rev.sfr.net] has quit [Client Quit]
09:42 -!- white5moke [~white5mok@ip72-219-109-30.oc.oc.cox.net] has quit [Quit: Leaving...]
10:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
10:01 < bitcoin-git> [bitcoin] hebasto opened pull request #23346: util, refactor: Improve headers for bitcoin-wallet tool (master...211024-bw-headers) https://github.com/bitcoin/bitcoin/pull/23346
10:01 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
10:34 -!- masta`` [~oyster@user/masta/x-2645138] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
10:35 -!- masta`` [~oyster@user/masta/x-2645138] has joined #bitcoin-core-dev
10:44 -!- Evel-Knievel [~Evel-Knie@user/evel-knievel] has quit [Ping timeout: 258 seconds]
10:50 < TallTim> guest3456 - FWIW I just added the -datadir <path> to the shortcut in win10 - I now sync to an external SSD
10:50 < TallTim> Any upgrade you do will require you to restore that, of course.
11:37 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
12:03 -!- csknk [~csknk@88.87.164.26] has quit [Quit: leaving]
12:06 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
12:07 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
12:08 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Client Quit]
12:09 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has joined #bitcoin-core-dev
12:16 -!- Guest6 [~Guest6@188.121.219.71] has joined #bitcoin-core-dev
12:18 -!- Guest6 [~Guest6@188.121.219.71] has quit [Client Quit]
12:25 -!- prayank [~andr0irc@51.15.187.53] has joined #bitcoin-core-dev
12:25 < prayank> I might sound negative at times while reading things however intentions were always to imrove Bitcoin.
12:25 < prayank> Today I met few unknown people before meetup. Questions were same as I have seen on Twitter, telegram, SE, reddit etc.
12:25 < prayank> But I smiled on energy question instead of reacting in a weird way. Said I will cover this in my presentation later and I can assure Bitcoin has no energy issues.
12:27 -!- prayank [~andr0irc@51.15.187.53] has quit [Quit: irc thread exit]
12:45 -!- gnaf [~gnaf@86-91-224-60.opennet.kpn.net] has quit [Ping timeout: 260 seconds]
12:54 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has quit [Ping timeout: 260 seconds]
12:54 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
12:54 < bitcoin-git> [bitcoin] hebasto opened pull request #23348: rpc, wallet: Do not return "keypoololdest" for blank descriptor wallets (master...211024-rpc-gwi) https://github.com/bitcoin/bitcoin/pull/23348
12:54 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
13:04 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
13:04 -!- ___nick___ [~quassel@cpc68286-cdif17-2-0-cust533.5-1.cable.virginm.net] has quit [Ping timeout: 244 seconds]
13:09 -!- Evel-Knievel [~Evel-Knie@user/evel-knievel] has joined #bitcoin-core-dev
13:17 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has quit [Ping timeout: 264 seconds]
13:21 -!- smartin [~Icedove@88.135.18.171] has quit [Quit: smartin]
13:33 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has joined #bitcoin-core-dev
13:40 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has quit [Ping timeout: 245 seconds]
13:48 -!- BlueMatt [~BlueMatt@ircb.bluematt.me] has joined #bitcoin-core-dev
13:51 -!- jesseposner [~jesse@c-24-5-105-39.hsd1.ca.comcast.net] has quit [Ping timeout: 244 seconds]
14:00 -!- nanotube [~nanotube@user/nanotube] has joined #bitcoin-core-dev
14:17 -!- Guyver2 [Guyver@guyver2.xs4all.nl] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
14:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has joined #bitcoin-core-dev
14:43 < bitcoin-git> [bitcoin] hebasto opened pull request #23349: util: Use FEATURE_LATEST for wallets created with bitcoin-wallet (master...211024-bw-version) https://github.com/bitcoin/bitcoin/pull/23349
14:43 -!- bitcoin-git [~bitcoin-g@x0f.org] has left #bitcoin-core-dev []
15:34 -!- prayank [~andr0irc@51.158.144.32] has joined #bitcoin-core-dev
15:34 < prayank> So I was looking for trying to respond on other issues:
15:34 < prayank> Q which repository and where do you make changes that gets approved?
15:34 < prayank> A: There are multiple implementations. Used only one with 6 maintainers. But we can change it. Even if don't want to.. you can run a software to be a part of network
15:37 -!- prayank [~andr0irc@51.158.144.32] has quit [Quit: irc thread exit]
15:46 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
15:48 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-dev
15:49 -!- jespada [~jespada@181.28.253.200] has joined #bitcoin-core-dev
15:50 < sipa> prayank: please stay on topic
15:51 -!- Aaronvan_ [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev
15:58 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
16:03 -!- mikehu44 [~quassel@206.189.41.250] has quit [Ping timeout: 258 seconds]
16:30 -!- emcy [~emcy@user/emcy] has quit [Remote host closed the connection]
16:30 -!- emcy [~emcy@user/emcy] has joined #bitcoin-core-dev
16:30 -!- emcy [~emcy@user/emcy] has quit [Remote host closed the connection]
16:31 -!- emcy [~emcy@user/emcy] has joined #bitcoin-core-dev
16:52 -!- Evel-Knievel [~Evel-Knie@user/evel-knievel] has quit [Ping timeout: 252 seconds]
17:33 -!- copumpkin [~woohoo@user/copumpkin] has joined #bitcoin-core-dev
17:37 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has quit [Ping timeout: 276 seconds]
17:51 -!- yanmaani [~yanmaani@gateway/tor-sasl/yanmaani] has joined #bitcoin-core-dev
18:36 -!- Aaronvan_ [~AaronvanW@71pc74.sshunet.nl] has quit [Remote host closed the connection]
18:55 -!- masta`` [~oyster@user/masta/x-2645138] has quit [Quit: Going offline, see ya! (www.adiirc.com)]
19:03 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5f45664i8y6v4.ipv6.telus.net] has joined #bitcoin-core-dev
19:06 -!- guest3456 [~guest3456@c-73-55-111-182.hsd1.fl.comcast.net] has joined #bitcoin-core-dev
19:06 < guest3456> how can i view my unused changed addresses in Core?
19:07 < guest3456> the menu bar gives me options for viewing sending and receiving addresses, but not change addresses
19:07 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev
19:07 < guest3456> as i remember, electrum allowed me to view all my future change addresses
19:10 < sipa> by repeatedly calling getrawchangeaddress you can get queued up change addresses
19:10 < guest3456> all i could find on stackexchange was to run `listaddressgroupings` but that only seems to show me already used change addresses... i'm looking to view the unusued future addresses
19:10 < sipa> they're only given out once those
19:10 < sipa> *though
19:11 < guest3456> what does that mean only given out once? after i run that command will they never generate again?
19:11 < sipa> indeed; they get marked used
19:12 < guest3456> how do other wallets like electrum generate a big list of them then
19:12 < guest3456> or am i mistaken
19:12 < sipa> i'm confuzed
19:12 < guest3456> actually specter wallet can show me all of them too, i just checked
19:12 < sipa> yes, ok
19:13 < sipa> core has a list of future change addresses too
19:13 < sipa> there is just no feature to view it
19:13 < sipa> pull requests welcome
19:14 < guest3456> hmmmmm and no console command i can run ?
19:14 < sipa> not that i know of
19:15 < sipa> if you really want to, you could make a backup, call getrawchangeaddress repeatedly, and then afterwards restore the backup, rewinding the used set
19:15 < sipa> if you call getaddressinfo with a future address, it'll confirm its status
19:15 < guest3456> hmmmmm maybe ill try that
19:16 < guest3456> i'm just wanting to double check before i sign+broadcast, to confirm that i do in fact control that change address
19:16 < guest3456> dont want to blindly trust the hww and specter, want to confirm with core
19:16 < sipa> oh, then just use getaddressinfo
19:17 < guest3456> i tried it
19:17 < guest3456> one outline said says
19:18 < guest3456>  "ismine": false,
19:18 < sipa> that implies bitcoin core would not consider that address as its own
19:18 < guest3456> meaning doesnt belong to my wallet?
19:19 < sipa> i.e., wouldn't treat it as crediting the wallet
19:19 < guest3456> my wallet is set up as a watch-only wallet in Core, would that affect that output line?
19:20 < sipa> watch-only should still result is ismine
19:20 < guest3456> hmmmm strange
19:21 < guest3456> specter (which is linked to core) created the txn, and both hwws are accepting the txn with that change address as signable
19:22 < sipa> it's probably better to go into detail if you need to, on https://bitcoin.stackexchange.com
19:22 < guest3456> hmmmm i think is:mine might mean something else
19:22 < guest3456> i just tried getaddressinfo with an address that already was used and has coins in it
19:22 < guest3456> and it still says ismine:false
19:23 < sipa> do you have multiple wallets perhaps in core?
19:23 < guest3456> this is an address that shows under `listaddressgroupings`
19:23 < guest3456> yes i do
19:23 < guest3456> i have a [default wallet] that is unused
19:23 < sipa> are you querying the right wallet?
19:23 < guest3456> yes i'm querying the multisig wallet
19:24 < guest3456> the [default] doesnt even have any addresses i dont even think i ever set it up
19:24 < sipa> ok
19:25 < sipa> i'd post it as a question on bitcoin.stackexchange.com; more people can help inventigate there
19:27 < guest3456> ok
19:38 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5f45664i8y6v4.ipv6.telus.net] has quit [Remote host closed the connection]
19:39 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5f45664i8y6v4.ipv6.telus.net] has joined #bitcoin-core-dev
19:40 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 244 seconds]
19:40 < luke-jr> eh, if there's a HWW involved, Core *won't* control it, the HWW will
19:41 < luke-jr> checking with Core is relatively meaningless in that scenario?
19:41 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 265 seconds]
19:41 < sipa> i assume this is a situation where the addresses/descriptor is imported into a core wallet
19:42 < sipa> especially as there is a separate multisig wallet for this purpose
19:42 < guest3456> yes i'm pretty sure specter set up the wallet in core
19:43 < guest3456> suppose i should update the stackexchange post with that info
19:43 < sipa> yeah
19:44 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5f45664i8y6v4.ipv6.telus.net] has quit [Ping timeout: 252 seconds]
19:52 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Remote host closed the connection]
19:53 -!- belcher [~belcher@user/belcher] has joined #bitcoin-core-dev
19:53 -!- morcos [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev
19:58 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5f45664i8y6v4.ipv6.telus.net] has joined #bitcoin-core-dev
20:07 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev
20:07 -!- mikehu44 [~quassel@183.36.228.41] has joined #bitcoin-core-dev
20:12 -!- mikehu44 [~quassel@183.36.228.41] has quit [Ping timeout: 265 seconds]
20:13 -!- mikehu44 [~quassel@183.36.228.41] has joined #bitcoin-core-dev
20:18 -!- mikehu44 [~quassel@183.36.228.41] has quit [Ping timeout: 265 seconds]
20:18 -!- mikehu44 [~quassel@206.189.41.250] has joined #bitcoin-core-dev
20:26 < yanmaani> Is #5029 resolved?
20:26 <@gribble> https://github.com/bitcoin/bitcoin/issues/5029 | Unix Domain Sockets · Issue #5029 · bitcoin/bitcoin · GitHub
20:33 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #bitcoin-core-dev
20:39 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 244 seconds]
20:43 -!- bomb-on [~bomb-on@194.144.47.113] has quit [Quit: aллилѹіа!]
21:01 -!- cmirror [~cmirror@4.53.92.114] has quit [Remote host closed the connection]
21:01 -!- cmirror [~cmirror@4.53.92.114] has joined #bitcoin-core-dev
21:04 < sipa> no
21:22 -!- Evel-Knievel [~Evel-Knie@user/evel-knievel] has joined #bitcoin-core-dev
21:28 < guest3456> thank you achow101 for your answer on stackexchange
21:29 -!- pranjaldoshi9627 [~pranjaldo@115.114.90.35] has joined #bitcoin-core-dev
21:30 -!- pranjaldoshi9627 [~pranjaldo@115.114.90.35] has quit [Client Quit]
21:52 -!- gnaf [~gnaf@86-91-224-60.opennet.kpn.net] has joined #bitcoin-core-dev
22:00 -!- Netsplit *.net <-> *.split quits: doubleqp, uasf_, sdfgsdfg, windsok, ExEric3, jrawsthorne_, murrayn, blkncd, lightningbot, neha,  (+1 more, use /NETSPLIT to show all of them)
22:00 -!- blkncd [sid505676@id-505676.helmsley.irccloud.com] has joined #bitcoin-core-dev
22:00 -!- Netsplit over, joins: doubleqp
22:00 -!- jrawsthorne [~jrawsthor@static.235.41.217.95.clients.your-server.de] has joined #bitcoin-core-dev
22:00 -!- Netsplit over, joins: ExEric3
22:00 -!- Netsplit over, joins: windsok
22:01 -!- nathanael [~nathanael@user/nathanael] has quit [Quit: connection reset by purr]
22:01 -!- uasf [~uasf@2604:a880:2:d0::1bda:1001] has joined #bitcoin-core-dev
22:01 -!- Netsplit over, joins: jetpack
22:02 -!- murrayn [~murray@static.38.4.181.135.clients.your-server.de] has joined #bitcoin-core-dev
22:02 -!- nathanael [~nathanael@user/nathanael] has joined #bitcoin-core-dev
22:04 -!- lightningbot [~supybot@2400:8901::f03c:91ff:febb:bbc1] has joined #bitcoin-core-dev
22:04 -!- sdfgsdfg [sdfgsdfg@user/sdfgsdfg] has joined #bitcoin-core-dev
22:37 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has joined #bitcoin-core-dev
22:47 -!- white5moke [~white5mok@ip72-219-109-30.oc.oc.cox.net] has joined #bitcoin-core-dev
23:02 -!- murrayn [~murray@static.38.4.181.135.clients.your-server.de] has quit [Changing host]
23:02 -!- murrayn [~murray@user/murrayn] has joined #bitcoin-core-dev
23:10 -!- AaronvanW [~AaronvanW@71pc74.sshunet.nl] has quit [Ping timeout: 245 seconds]
23:19 -!- goatpig [~goat@static-193-13-33-110.cust.tele2.se] has joined #bitcoin-core-dev
23:23 -!- white5moke [~white5mok@ip72-219-109-30.oc.oc.cox.net] has quit [Quit: Leaving...]
23:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 276 seconds]
23:28 -!- morcos [~morcos@gateway/tor-sasl/morcos] has quit [Quit: ZNC 1.8.2+deb1+bionic2 - https://znc.in]
23:28 -!- morcos_ [~morcos@gateway/tor-sasl/morcos] has joined #bitcoin-core-dev
23:28 -!- morcos_ is now known as morcos
23:38 -!- freesprung [~freesprun@user/freesprung] has quit [Ping timeout: 245 seconds]
23:54 -!- freesprung [~freesprun@user/freesprung] has joined #bitcoin-core-dev
--- Log closed Mon Oct 25 00:00:13 2021