<michaelfolkson>
fi3: There may have been advancements since this was discussed last but some context from previous discussions on Rust is here: https://github.com/bitcoin/bitcoin/issues/17090
<michaelfolkson>
#proposedmeetingtopic (by fi3) rust library in bitcoin core (23049)
<sipa>
#proposedwalletmeetingtopic (by fi3) rust library in bitcoin core (23049)
<jonatack>
yes, on mainnet the most frequent contentions I see are the cs_vNodes ones, and many/most on them were replaced by only a handful of connman.cs_vNodes contention *per hour* instead...grep "connman.cs_vNodes" ~/.bitcoin/debug.log
<bitcoin-git>
bitcoin/master d8b4b30 W. J. van der Laan: Merge bitcoin/bitcoin#23057: log: Consolidate timedata logging
<bitcoin-git>
[bitcoin] jonatack opened pull request #23076: Pass CFeeRate and CTxMemPool in-params by reference to const (master...feerate-and-txmempool-fixups) https://github.com/bitcoin/bitcoin/pull/23076
<bitcoin-git>
[bitcoin] darosior opened pull request #23075: refactoring: Fee estimation functional test cleanups (master...fee_est_test_cleanup) https://github.com/bitcoin/bitcoin/pull/23075
<bitcoin-git>
[bitcoin] fanquake merged pull request #23054: Use C++11 member initializer in CTxMemPoolEntry (master...2109-cpp11MemberInitMempool) https://github.com/bitcoin/bitcoin/pull/23054
<bitcoin-git>
bitcoin/master fa08d4c MarcoFalke: Use C++11 member initializer in CTxMemPoolEntry
<jeremyrubin>
I think what we'd want is to remove the http support from Bitcoin core and then build a separate binary with a simple http proxy to it
<sipa>
you can also use bitcoin core RPC in a local trusted network
<sipa>
*anything* could have been chosen for bitcoin core's RPC interface, but the one that was chosen was json-rpc over http with user/pass authentication
<sipa>
michaelfolkson: c-lightning just calls bitcoin-cli
<bitcoin-git>
[bitcoin] fanquake closed pull request #22966: doc: Improve documentation around the ACK statement (master...ack-documentation) https://github.com/bitcoin/bitcoin/pull/22966
<bitcoin-git>
[bitcoin] meshcollider opened pull request #23065: Allow UTXO locks to be written to wallet DB (master...202109_lockunspent_persistence) https://github.com/bitcoin/bitcoin/pull/23065
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23064: fuzz: Fix memory leak in system fuzz target (master...2109-fuzzMemLeakSys) https://github.com/bitcoin/bitcoin/pull/23064
<prayank>
paulo: There are lot of things to work on. You can start with https://github.com/bitcoin/bitcoin/issues/22368 (It's less than 20 lines of code if correctly done but nobody wants to work on it for some reason)
<prayank>
paulo: if you have things in wishlist that improve privacy in bitcoin core but you don't feel like creating an issue in the repository, feel free to write them down in a gist and share the link here. Will be helpful.
<bitcoin-git>
[bitcoin] fanquake opened pull request #23060: release: increase minimum compiler and lib(std)c++ requirements (master...23_0_min_compiler_libcpp_requires) https://github.com/bitcoin/bitcoin/pull/23060
<prayank>
instagibbs: 1. Not sure tbh how will things change if different mempool policies are used however it looks less likely in near future looking at the trend. Most users will run Bitcoin Core and they will use defaults. 2. Things are simple. There are blocks which get mined every few minutes. Blocks have limit based on vsize or weight. So everyone is bidding and competing to get their transactions confirmed. There is nothing to estimate or predict but
<dviola>
when I receive a tx in bitcoin core 22.0.0 the clock icon (before the date field) in the Transactions tab says I have 1 of 6 confirmations
<prayank>
If I want to buy bitcoin right now, I will look at the orderbook and create limit buy order at 42200. I won't check last 1000 trades because they don't matter if goal is to buy bitcoin asap.
<laanwj>
but sure, agree it makes sense to prefix, all the bitcoin-core channels were prefixed with bitcoin-core when moving to libera
<jeremy>
not sure who owns the #bitcoin namespace tho
<jeremy>
yes, aware of that. I think it's that they prefer whoever owns the #bitcoin namespace should encourage/assist allocating bip reviews as ##bitcoin-bip-review-<name> or something going forward.
<jeremy>
laanwj, not sure if you "own" the IRC, but as a general rule the #libera folk asked me to relay that they strongly prefer we not use channels like ##ctv-bip-review or ##taproot-bip-review in the future and instead namespace them in #bitcoin
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #22734: addrman: Avoid crash on corrupt data, Force Check after deserialize (master...2108-addrmanNoCrash) https://github.com/bitcoin/bitcoin/pull/22734
<bitcoin-git>
bitcoin/master fae5c63 MarcoFalke: move-only: Move CAddrMan::Check to cpp file
<bitcoin-git>
bitcoin/master fa29897 MarcoFalke: Refactor: Turn the internal addrman check helper into a forced check
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23054: Use C++11 member initializer in CTxMemPoolEntry (master...2109-cpp11MemberInitMempool) https://github.com/bitcoin/bitcoin/pull/23054
<bitcoin-git>
[bitcoin] jnewbery opened pull request #23053: [fuzz] Use public methods in addrman fuzz tests (master...2021-09-addrman-fuzzer-public-methods2) https://github.com/bitcoin/bitcoin/pull/23053
<bitcoin-git>
[bitcoin] Shubhankar-Gambhir opened pull request #23052: test: use miniwallet in test_rpc function in feature_rbf.py (master...master) https://github.com/bitcoin/bitcoin/pull/23052
<Kiminuo>
jonatack: https://github.com/bitcoin/bitcoin/pull/12677#pullrequestreview-759043318 - I don't really want to try to beat somebody in addressing these but I should have some time over the coming days to address that so I'll do it, ok? Saying that just because I don't want to compete with somebody
<bitcoin-git>
[bitcoin] jonatack opened pull request #23050: log: change an incorrect fee to fee rate, and vice-versa (master...fee-vs-feerate) https://github.com/bitcoin/bitcoin/pull/23050
<bitcoin-git>
[bitcoin] jb55 closed pull request #18985: bloom: use Span instead of std::vector for `insert` and `contains` [ZAP3] (master...2020-05-bloom-span) https://github.com/bitcoin/bitcoin/pull/18985
<laanwj>
it indeed looks like "dpkg --add-architecture armhf && apt update && apt install libc6:armhf" is enough to run armhf release bitcoin-cli on aarch64 host
<laanwj>
name connections (where the network isn't known) are a special case that's outside of the normal per-network proxy handling, names never come from the P2P network but only in special cases (as mentioned in https://github.com/bitcoin/bitcoin/pull/22959#issuecomment-922915197)
<gribble>
https://github.com/bitcoin/bitcoin/issues/22949 | fee: Round up fee calculation to avoid a lower than expected feerate by achow101 · Pull Request #22949 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23043: ci: Set --nocleanup for Windows functional tests (master...2109-ciWinCleanup) https://github.com/bitcoin/bitcoin/pull/23043
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #23042: net: Avoid logging AlreadyHaveTx when disconneting misbehaving peer (master...2109-netLogDisconnect) https://github.com/bitcoin/bitcoin/pull/23042
<bitcoin-git>
[bitcoin] theStack opened pull request #23037: test: fix confusing off-by-one nValue in feature_coinstatsindex.py (master...202109-test-fix_namount_offbyone_in_coinstatsindex) https://github.com/bitcoin/bitcoin/pull/23037
<bitcoin-git>
[bitcoin] jonatack opened pull request #23036: test: use test_framework.p2p `P2P_SERVICES` constant in functional tests (master...use-test_framework-P2P_SERVICES-in-functional-tests) https://github.com/bitcoin/bitcoin/pull/23036
<bitcoin-git>
[bitcoin] jonatack opened pull request #23035: p2p, rpc, test: expose tried and refcount in getnodeaddresses, update/improve tests (master...getnodeaddresses-tried-and-reference_count) https://github.com/bitcoin/bitcoin/pull/23035
<kallewoof>
The signet faucet bitcoin core node is so slow that the faucet is experiencing time-outs now. It has quite a lot of keys. If someone wants to do some analysis to see where to speed tihngs up before I do some utxo consolidation, let mek now.
<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
<shiza>
That's a lot easier way to understanding it than bitcoin.it/regression_test_mode!
<bitcoin-git>
[bitcoin] martinus opened pull request #23025: bench: update nanobench add `-min_duration_ms` (master...2021-09-update-nanobench) https://github.com/bitcoin/bitcoin/pull/23025
<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'.)
<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
<shiza>
Can anything in Bitcoin Core transform a legacy wallet into a descriptors wallet in a single step?
<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>
[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>
[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
<harding>
shasum on linux has an option to ignore invalid input, which was used on the BitcoinCore.org instructions. For OSX, there's no such option, and I wonder if you could just insert a line in the SHASUMS file that said "bitcoin-22.0.blah.tar.gz SUCCESS" and make it look like it passed or something. For the Windows instructions, I think you had to do by-eye verification anyway.
<roconnor>
IIUC at least some of these signers are not using dedicated bitcoin signing keys, and thus may use the same key for signing emails or whatnot.
<gribble>
https://github.com/bitcoin/bitcoin/issues/22949 | fee: Round up fee calculation to avoid a lower than expected feerate by achow101 · Pull Request #22949 · bitcoin/bitcoin · GitHub
<prayank>
I had added some topic for meeting today according to bitcoin core wiki. It's 12 AM here and I want to sleep early today. Shared my thoughts here which most probably would not matter, but better than suggesting a topic and saying nothing: https://gist.github.com/prayank23/e385e31427989c47e715d61556772d02
<bitcoin-git>
bitcoin/master 350e034 Jon Atack: consensus: don't call GetBlockPos in ReadBlockFromDisk without lock
<bitcoin-git>
bitcoin/master cdf12c7 W. J. van der Laan: Merge bitcoin/bitcoin#22895: consensus: don't call GetBlockPos in ReadBloc...
<bitcoin-git>
[bitcoin] theStack opened pull request #22998: test: use MiniWallet for make_utxo helper in feature_rbf.py (master...202109-test-use_miniwallet_for_make_utxo) https://github.com/bitcoin/bitcoin/pull/22998