< luke-jr> hmm, no way to specify --timeout-factor for test-runner
< bitcoin-git> [bitcoin] sipa opened pull request #20516: Introduce well-defined CAddress disk serialization (master...202011_disk_addr) https://github.com/bitcoin/bitcoin/pull/20516
< bitcoin-git> [bitcoin] memolabed opened pull request #20517: 0.22 (master...0.21) https://github.com/bitcoin/bitcoin/pull/20517
< bitcoin-git> [bitcoin] fanquake closed pull request #20517: 0.22 (master...0.21) https://github.com/bitcoin/bitcoin/pull/20517
< RickMortir22> Anyone Can Help? - My Bitcoin Core dont Work Anymore, it stoped syng 19 hours ago and dont sync anymore, its shows "19 hours ago" forever, and status bar show "connecting..."
< RickMortir22> Anyone Can Help? - My Bitcoin Core dont Work Anymore, it stoped syng 19 hours ago and dont sync anymore, its shows "19 hours ago" forever, and status bar show "connecting..."
< fanquake> wumpus / sipa: can you block gloriashaw
< wumpus> sure
< bitcoin-git> [gui] hebasto opened pull request #137: refactor: Replace deprecated Qt::SystemLocale{Short,Long}Date (master...201127-locale) https://github.com/bitcoin-core/gui/pull/137
< fanquake> hebasto: I haven’t been able to look at 20504 yet, sorry
< hebasto> np
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/50091592dd87...e2ff5e7b35d7
< bitcoin-git> bitcoin/master e416cfc sanket1729: Add MAX_STANDARD_SCRIPTSIG_SIZE to policy
< bitcoin-git> bitcoin/master e2ff5e7 MarcoFalke: Merge #20497: [Refactor] Add MAX_STANDARD_SCRIPTSIG_SIZE to policy
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20497: [Refactor] Add MAX_STANDARD_SCRIPTSIG_SIZE to policy (master...policy) https://github.com/bitcoin/bitcoin/pull/20497
< bitcoin-git> [bitcoin] practicalswift opened pull request #20519: Handle rename failure in DumpMempool(...) by using the RenameOver(...) return value. Add [[nodiscard]] to RenameOver(...). (master...renameover-nodiscard) https://github.com/bitcoin/bitcoin/pull/20519
< Provostro> Hi, what was Hal Finney's IRC nick? just curious
< murch> Don't know why I think that, but I seem to remember it was "halfin".
< bitcoin-git> [bitcoin] luke-jr closed pull request #20484: RPC: Migrate estimatesmartfee return value from "feerate" (BTC/kvB) to "fee_rate" (sat/vB) (master...estimatefee_fee_rate) https://github.com/bitcoin/bitcoin/pull/20484
< murch> Was trying to find irc logs or screenshots of any conversations he has been in, and realized that his twitter handle was "halfin". I can't find anything to corroborate that he also used that handle on IRC, so I withdraw my suggestion
< Provostro> thank u
< jb55> not sure if this is new behavior or if I just didn't realize it... but I did a sendtoaddress from my watch-only descriptor wallet, and it succeeded (what?). there's a txid and entry in listtransactions but the tx doesn't have any signatures. is this normal?
< jb55> hmm branch is 2 months old... will try master
< jamesob> hm, anyone able to tell me whether this is a spurious failure or not? don't think I'm able to restart the run on cirrus
< jamesob> nevermind, able to restart
< bitcoin-git> [bitcoin] hebasto opened pull request #20520: ci, depends: Do not force Precompiled Headers (PCH) when building Qt (master...201127-pch) https://github.com/bitcoin/bitcoin/pull/20520
< bitcoin-git> [bitcoin] sipa closed pull request #20514: Use addrv2 serialization in anchors.dat (master...202011_v2_anchors) https://github.com/bitcoin/bitcoin/pull/20514
< sipa> Provostro: i'm not sure Hal Finney was ever on any (bitcoin related) IRC channels.
< Provostro> It's unusual he would have chosen for bitcoin to connect to IRC without being an IRC user?
< sipa> was he the one who implemented IRC seeding?
< luke-jr> is it practical to use IRC with his disability?
< sipa> luke-jr: he was only diagnosed in october 2019, bitcoin had IRC seeding before that point
< sipa> *2009
< midnight> Hal finney was almost certainly never in any of the #bitcoin* channels; at least not under his own name.
< midnight> Satoshi neither, according to my memory of things Art et al said.
< sipa> Indeed.
< bitcoin-git> [bitcoin] sipsorcery opened pull request #20521: IGNORE: Testing appveyor build time on Bitcoin Core account (master...msvc-no-optimise-vcpkg-prebuilt) https://github.com/bitcoin/bitcoin/pull/20521
< bitcoin-git> [gui] mjdietzx opened pull request #138: qt: unlock encrypted wallet "OK" button bugfix (master...qt-unlock-wallet-ok-enabled-bugfix) https://github.com/bitcoin-core/gui/pull/138
< bitcoin-git> [bitcoin] sipsorcery closed pull request #20521: IGNORE: Testing appveyor build time on Bitcoin Core account (master...msvc-no-optimise-vcpkg-prebuilt) https://github.com/bitcoin/bitcoin/pull/20521
< andytoshi> under what circumstances is `CTxDestination parent_addr(ScriptHash(redeem_script))` different from `CTxDestination parent_addr = CTxDestination(ScriptHash(redeem_script))`
< andytoshi> apologies if this is the wrong channel
< andytoshi> it seems like gcc is interpreting the first as defining `parent_addr` to be a function which takes a ScriptHash
< andytoshi> and the latter it correctly calls the CTxDestination constructor
< andytoshi> is this a gcc bug or do i just not know gcc
< andytoshi> C++
< sipa> andytoshi: does "CTxDestination parent_addr{ScriptHash(redeem_script)};" work?
< sipa> using the var(args) way of constructing is generally discouraged
< andytoshi> it does, yep! thanks. i'm glad c++ cleaned up this syntax wart
< bitcoin-git> [bitcoin] amitiuttarwar opened pull request #20522: [test] Fix sync issue in disconnect_p2ps (master...2020-11-disconnect-p2ps) https://github.com/bitcoin/bitcoin/pull/20522