<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22970: doc: Update snap release process for new versioning scheme (master...2109-docSnapRel) https://github.com/bitcoin/bitcoin/pull/22970
<_aj_>
lucaferr: you need neighbouring nodes that have upgraded to support taproot; "bitcoin-cli getpeerinfo | grep subver" -> look for 0.21.1 or 0.21.99 or 22.0.0 or 22.99.0
<laanwj>
of course, updating the documentation and verification instructions is still important, but it should be a one-time thing. I did have a note on verifying the binaries in the testing instructions here: https://github.com/bitcoin/bitcoin/issues/22634
<bitcoin-git>
[bitcoin] jarolrod opened pull request #22966: doc: Improve documentation around the ACK statement (master...ack-documentation) https://github.com/bitcoin/bitcoin/pull/22966
<harding>
Re: verification instructions, I just opened a PR to temporarily hide them until they can be updated. If I can get a couple approach ACKs from established contributors in the next hour or two, I'll merge tonight. https://github.com/bitcoin-core/bitcoincore.org/pull/796
<bitcoin-git>
[gui] hebasto closed pull request #261: Display node address in peer table with monospace font for clean alignment (master...node-address-monospace) https://github.com/bitcoin-core/gui/pull/261
<bitcoin-git>
[bitcoin] klementtan opened pull request #22959: cli: Display all proxies in -getinfo (master...getinfo-multiple-proxies) https://github.com/bitcoin/bitcoin/pull/22959
<bitcoin-git>
[bitcoin] JeremyRubin opened pull request #22954: [TESTS] Allow tx_invalid.json tests to include flag rules for if_unset: [A,B,C] then_unset: [D] (master...if_unset_then_unset) https://github.com/bitcoin/bitcoin/pull/22954
<bitcoin-git>
[bitcoin] achow101 opened pull request #22949: fee: Round up fee calculation to avoid a lower than expected feerate (master...feerate-round) https://github.com/bitcoin/bitcoin/pull/22949
2021-09-10
<bitcoin-git>
[bitcoin] JeremyRubin opened pull request #22948: [Tests] Computer the Power Set of all flags instead of one by one exclusion (master...flag-powerset) https://github.com/bitcoin/bitcoin/pull/22948
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22940: fuzz: Move all addrman fuzz targets to one file (master...2109-fuzzMergeAddrman) https://github.com/bitcoin/bitcoin/pull/22940
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22939: fuzz: Reset addrman when consistency check fails (master...2109-fuzzAddrmanCheck) https://github.com/bitcoin/bitcoin/pull/22939
<bitcoin-git>
[bitcoin] rajarshimaitra opened pull request #22938: test: Add remaining scenarios of 0 waste, in wallet waste_test (master...waste-test-add) https://github.com/bitcoin/bitcoin/pull/22938
<bitcoin-git>
[bitcoin] MarcoFalke merged pull request #22762: Raise InitError when peers.dat is invalid or corrupted (master...2108-InitErrorAddrmanCorrupt) https://github.com/bitcoin/bitcoin/pull/22762
<bitcoin-git>
bitcoin/master fa5aeec MarcoFalke: Move LoadAddrman from init to addrdb
<bitcoin-git>
bitcoin/master 07a9ecc John Newbery: [net] Remove CConnman::Options.m_asmap
<bitcoin-git>
bitcoin/master 9fd5618 John Newbery: [asmap] Make DecodeAsmap() a utility function
<bitcoin-git>
[bitcoin] fanquake merged pull request #22926: doc: Set PYTHONUTF8=1 for functional tests on Windows (master...210908-utf) https://github.com/bitcoin/bitcoin/pull/22926
<bitcoin-git>
[bitcoin] fanquake opened pull request #22936: test: don't try and use os.killpg() on Windows (master...windows_no_killpg) https://github.com/bitcoin/bitcoin/pull/22936
<bitcoin-git>
[bitcoin] S3RK opened pull request #22929: wallet: Automatically add receiving destinations to the address book (master...fix_19856) https://github.com/bitcoin/bitcoin/pull/22929
<bitcoin-git>
[bitcoin] kiminuo opened pull request #22928: Remove `gArgs` from `wallet.h` and `wallet.cpp` (2) (master...feature/2021-09-wallet-gArgs) https://github.com/bitcoin/bitcoin/pull/22928
<bitcoin-git>
[bitcoin] fanquake merged pull request #22390: system: skip trying to set the locale on NetBSD (master...netbsd_dont_set_locale) https://github.com/bitcoin/bitcoin/pull/22390
<bitcoin-git>
[bitcoin] hebasto opened pull request #22926: doc: Set PYTHONUTF8=1 for functional tests on Windows (master...210908-utf) https://github.com/bitcoin/bitcoin/pull/22926
<bitcoin-git>
[bitcoin] mjdietzx opened pull request #22924: refactor: merge ScriptPubKeyToUniv and ScriptToUniv into a single function (master...refactor_ScriptToUniv) https://github.com/bitcoin/bitcoin/pull/22924
<laanwj>
yes; as far as we know, spy nodes do not generally run bitcoin core at all, or if they do, i'd expect them to use a heavily patched version that logs all kinds of extra stuff
<laanwj>
just be really careful with giving bitcoin debug logs to people, they're never "safe" from a privacy perspective, if possible only post a relevant excerpt and if you post to public forums, censor information you don't want known
<bitcoin-git>
[bitcoin] RohitRanjangit opened pull request #22919: fees: skip pointless fee parameter calculation during IBD (master...lazy_update) https://github.com/bitcoin/bitcoin/pull/22919
<bitcoin-git>
[gui] luke-jr closed pull request #230: Support backup to new text-based database dump format (master...gui_backup_formats) https://github.com/bitcoin-core/gui/pull/230
2021-09-07
<bitcoin-git>
[gui] hebasto closed pull request #27: Move the UI window style to a top to bottom layout (master...move-ui-to-mobile) https://github.com/bitcoin-core/gui/pull/27
<prayank>
Solution could have been using IP addresses if every domain used for seeds had only few IPs that never change. But looking at some of domains and A records it seems every domain has lot of IPs. Example: seed.bitcoin.sipa.be has more than 700 IP address in A records
<prayank>
dhruv: I don't understand quantum computing and related things but this post looks interesting: https://voluntarymind.com/bitcoin/2021/ (DNS seeds)
<michaelfolkson>
I'm sure most individuals would rather lose their encryption than lose their Bitcoin but I get the 70 year thing
<sipa>
but also context matters... for something like bitcoin transactions, switching to a PQC scheme comes at a tremendous cost (PQC keys/sigs are all many times larger, and less featureful)
<michaelfolkson>
dhruv: Cool, thanks. Thinking through how "signing a new public PQC key with the old private key to reassign ownership to the PQC public key" would work in Bitcoin script
<dhruv>
Quantum computing and it's impact on cryptography often comes up in Bitcoin conversations. Having no background, I was often intimidated/confused. I recently studied the basics and posted my notes here in case others find it useful: https://voluntarymind.com/bitcoin/quantum-computing-and-post-quantum-crypto/
<prayank>
Makes sense. IPFS isn't required. Onion website and torrents are good enough for Bitcoin Core. I was researching about IPFS alternatives for one of my project. Came across this issue so wanted to confirm few things.