< bitcoin-git>
[bitcoin] jonatack opened pull request #21786: wallet: ensure sat/vB feerates are in range (mantissa of 3) (master...ensure-sat-vb-feerates-are-in-range) https://github.com/bitcoin/bitcoin/pull/21786
< bitcoin-git>
[bitcoin] brunoerg opened pull request #21784: test: remove flags verification since it has a fixed value (master...2021-04-segwit-test) https://github.com/bitcoin/bitcoin/pull/21784
< bitcoin-git>
[gui] hebasto opened pull request #296: Do not use QObject::tr plural syntax for numbers with a unit symbol (master...210425-plurals) https://github.com/bitcoin-core/gui/pull/296
< sipa>
if you're going to ask more of these questions, it may be better to ask on https://bitcoin.stackexchange.com; it's more generic than just bitcoin core, and has lots of people answering
< CrazyPython>
How many of the Bitcoin developers have churned? Anyone still around from the Satoshi days?
< CrazyPython>
Is Bitcoin Core's block verification code highly optimized?
< sipa>
there are lots of improvements being worked on by various people, some related to consensus rules, but far more things in p2p improvements (mostly in bitcoin core), generic software improvements in various software, other software stack built on top, ...
< CrazyPython>
Are there any upcoming plans for optimizing Bitcoin? (Other than Taproot, Schnorr)
< sipa>
in any case, this channel is about bitcoin core really
< CrazyPython>
Has Bitcoin Core ever done an intended hard fork?
< CrazyPython>
sipa: <hard fork count>.<soft fork count>.<patch count> could be a numbering system for bitcoin
< CrazyPython>
If Bitcoin were on semver, then 0.x would mean Bitcoin is prone to backwards-incompatible changes
< sipa>
bitcoin itself doesn't have a version number
< sipa>
the next release of Bitcoin Core will be 22.0
< CrazyPython>
When will bitcoin reach 1.0?
2021-04-24
< bitcoin-git>
[gui] RandyMcMillan opened pull request #293: peers-tab: enable wordWrap for Services (master...enable-wordwrap-services) https://github.com/bitcoin-core/gui/pull/293
< darosior>
meshcollider: if you mind giving a quick look to https://github.com/bitcoin/bitcoin/pull/20867 , fanquake asked you for review some time ago, and many other wallet people ACKed (or previous versions of it without nits-fixing)
< bitcoin-git>
[bitcoin] dongcarl opened pull request #21767: [Bundle 6/n] Prune g_chainman usage in auxiliary modules (master...2020-10-libbitcoinruntime-v8) https://github.com/bitcoin/bitcoin/pull/21767
< bitcoin-git>
[gui] jonatack opened pull request #289: Add "Direction" column to peers tab (master...add-direction-column-to-peers-tab) https://github.com/bitcoin-core/gui/pull/289
< bitcoin-git>
[bitcoin] wu-emma opened pull request #21764: build: produce Windows GUI build with Cirrus CI (master...cirrus-winbuild) https://github.com/bitcoin/bitcoin/pull/21764
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21763: test: Run AppInitSanityChecks before all tests (master...2104-testCommonInit) https://github.com/bitcoin/bitcoin/pull/21763
< jnewbery>
it does seem somewhat of a centralization problem. The BIPs repo is a venue for sharing proposed changes to Bitcoin, and one person decides who can update it, and also decides whether or not they should ever be replaced/supplemented?
< ariard>
jeremyrubin: on the other point, I don't think bip2 recommend bitcoin-core-dev as a venue, maybe better suitted to #bitcoin or #bitcoin-wizards
< bitcoin-git>
[bitcoin] practicalswift opened pull request #21756: Avoid calling `getnameinfo` when formatting IPv6 addresses in `CNetAddr::ToStringIP` (master...simplify-ipv6-address-formatting) https://github.com/bitcoin/bitcoin/pull/21756
< bitcoin-git>
[bitcoin] prayank23 opened pull request #21755: Add more info about prefix in error message for invalid address (master...error-address) https://github.com/bitcoin/bitcoin/pull/21755
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21754: test: Run feature_cltv with MiniWallet (master...2104-testCltvNoWallet) https://github.com/bitcoin/bitcoin/pull/21754
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21752: scripted-diff: Clarify that feerates are per virtual size (master...2104-docFee) https://github.com/bitcoin/bitcoin/pull/21752
< fanquake>
Why not just open it with the description, and avoid potential questions. i.e :https://github.com/bitcoin/bitcoin/pull/21749#discussion_r618227797
< BlueMatt>
you asked why bitcoin core doesn't use something other than assert(), I answered why. There is, to my knowledge, nothing in bitcoin core that will abort() in a debug build and not in a release build, which appears to be what you want.
< BlueMatt>
yanmaani: bitcoin core generally has historically treated assert() as "if this isn't true, we probably have buggy hardware, or otherwise may lose funds, continuing is unsafe". so running without assertions is definitely *not* a goal
< yanmaani>
How come Bitcoin doesn't use a custom assert macro? That way, if NDEBUG is set, assert could be ((void)__VA_ARGS__) instead, allowing for compilation without assertions to be made.
< gribble>
https://github.com/bitcoin/bitcoin/issues/21694 | build: Use XLIFF file to provide more context to Transifex translators by hebasto · Pull Request #21694 · bitcoin/bitcoin · GitHub
< bitcoin-git>
bitcoin/master e16f872 fanquake: Merge #21655: build, qt: No longer need to set QT_RCC_TEST=1 for determini...
< bitcoin-git>
[bitcoin] fanquake merged pull request #21655: build, qt: No longer need to set QT_RCC_TEST=1 for determinism (master...210411-qhash) https://github.com/bitcoin/bitcoin/pull/21655
< bitcoin-git>
bitcoin/master c799a19 Hennadii Stepanov: build, qt: No longer need to set QT_RCC_TEST=1 for determinism
< bitcoin-git>
[bitcoin] windsok opened pull request #21740: test: add new python linter test for checking filenames and file permissions (master...file-permissions-linter) https://github.com/bitcoin/bitcoin/pull/21740
< sipa>
it won't get relayed by bitcoin core, because it's below the marginal feerate (the cost of relaying over the network is considered larger than what it's paying extra
< amiti>
The PR serves as a proof of concept for how this can be implemented in Bitcoin Core, but is currently in a draft because I have been trying to build confidence that this wouldn’t harm other software on the network.
< bitcoin-git>
[bitcoin] laanwj merged pull request #21694: build: Use XLIFF file to provide more context to Transifex translators (master...210415-xliff) https://github.com/bitcoin/bitcoin/pull/21694
< gribble>
https://github.com/bitcoin/bitcoin/issues/21694 | build: Use XLIFF file to provide more context to Transifex translators by hebasto · Pull Request #21694 · bitcoin/bitcoin · GitHub
< ShapeShifter499>
so I have a question about the client. I'm on linux and I'm wondering does it matter what Berkeley Database Bitcoin is compiled against if I want to recover old wallets?
< wumpus>
december tends to be a really quiet month in bitcoin dev
< bitcoin-git>
[bitcoin] laanwj opened pull request #21736: doc: Fix doxygen comment silent merge conflict in descriptor.cpp (master...2021-04-parameter-documentation) https://github.com/bitcoin/bitcoin/pull/21736
< bitcoin-git>
[bitcoin] laanwj merged pull request #21238: A few descriptor improvements to prepare for Taproot support (master...202102_descriptor_prepare_taproot) https://github.com/bitcoin/bitcoin/pull/21238
< bitcoin-git>
bitcoin/master 4441c6f Pieter Wuille: Make DescriptorImpl support multiple subscripts
< bitcoin-git>
bitcoin/master a917478 Pieter Wuille: refactor: move population of out.scripts from ExpandHelper to MakeScripts
< bitcoin-git>
bitcoin/master 84f3939 Pieter Wuille: Remove support for subdescriptors expanding to multiple scripts
< bitcoin-git>
[bitcoin] sipsorcery opened pull request #21731: Update msvc build to use Qt5.12.10 binaries. (master...msvc_qt5.12.10) https://github.com/bitcoin/bitcoin/pull/21731
< gribble>
https://github.com/bitcoin/bitcoin/issues/21694 | build: Use XLIFF file to provide more context to Transifex translators by hebasto · Pull Request #21694 · bitcoin/bitcoin · GitHub
< Arvidt>
I changed the hostname in my script from bitcoin.org to bitcoincore.org now it is working again. And the download speed is very fast now that's fine
< bitcoin-git>
bitcoin/master 13d27b4 Hennadii Stepanov: Merge bitcoin-core/gui#276: Elide long strings in their middle in the Peer...
< harding>
Arvidt: I don't see a 0.21.1 folder on bitcoin.org/bin/ ; are you sure you're seeing it? In any case, the preferred location to get the binaries is from https://bitcoincore.org/bin/