<bitcoin-git>
bitcoin/master 97cea1a Antoine Poinsot: policy: unit test Segwit dust thresholds
<bitcoin-git>
bitcoin/master 6bf706a MarcoFalke: Merge bitcoin/bitcoin#22846: policy: unit test Segwit dust thresholds
<bitcoin-git>
[bitcoin] fanquake closed pull request #18130: Replace uses of boost::trim* with locale-independent alternatives (master...2020-02-boost-trim) https://github.com/bitcoin/bitcoin/pull/18130
<bitcoin-git>
[bitcoin] fanquake opened pull request #22859: Replace uses of boost::trim* with locale-independent alternatives (#18130 rebased) (master...18130_rebased) https://github.com/bitcoin/bitcoin/pull/22859
<bitcoin-git>
[bitcoin] fanquake merged pull request #22631: doc: Add packages that provide Qt Wayland plugin for Linux (master...210805-wayland) https://github.com/bitcoin/bitcoin/pull/22631
<lightlike>
b10c: did you see https://www.dsn.kastel.kit.edu/bitcoin/index.html by the authors of the paper? the "Churn" graph there (I think their nodes try to connect to every node they get an addr for) went into the roof when the addr spam started
<jonatack>
any rate it's a little early to run only i2p, but some people began their first experiments trying bitcoin over i2p by running onlynet=i2p (and reported two months for IBD)
<michaelfolkson>
Cool you are contributing to Learning Bitcoin from Command Line
<prayank>
Not reusing a bitcoin adress is a best practice
<prayank>
1. Is there anything in Bitcoin Core that prevents situation in which my node has 8 outbound connections (2 ipv4, 2 ipv6, 2 onion, 2 i2p) but in reality they are addresses of 2 nodes.
<laanwj>
mmy grouping it into one archive repo would be best-it's not like the most of the other repositories see a lot of traffic on top of what bitcoin/bitcoin gets
<laanwj>
it would make sense to do it for all repos under bitcoin and bitcoin-core
<laanwj>
just reminded again that we don't currently have metadata backup for the GUI repository like we have for bitcoin/bitcoin in zw/bitcoin-gh-meta
<bitcoin-git>
[bitcoin] siv2r opened pull request #22851: [WIP] Add Python ChaCha20 implementation and bindings for CPP ChaCha20 implementation (master...chacha20-test-coverage) https://github.com/bitcoin/bitcoin/pull/22851
<bitcoin-git>
[bitcoin] meshcollider merged pull request #22009: wallet: Decide which coin selection solution to use based on waste metric (master...cs-waste-2) https://github.com/bitcoin/bitcoin/pull/22009
<gribble>
Error: '#bitcoin-otc:8f2f03563f52e38a1022450907e9108c382606db9dfba6f1284e3bac' is not a valid http url.
<gribble>
Error: In order to authenticate, you must be present in one of the following channels: #bitcoin-otc;#bitcoin-bans;#gribble
<gribble>
Request successful for user gnaf, hostmask gnaf!~gnaf@86-91-224-60.opennet.kpn.net. Your challenge string is: zirconium.libera.chat:#bitcoin-otc:8f2f03563f52e38a1022450907e9108c382606db9dfba6f1284e3bac
<bitcoin-git>
[bitcoin] sriramdvt opened pull request #22850: net: Make m_mempool optional in PeerManager (master...peerman-mempool-ptr) https://github.com/bitcoin/bitcoin/pull/22850
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22849: Remove unused SERIALIZE_METHODS for CBanEntry (master...2109-remBanEntrySer) https://github.com/bitcoin/bitcoin/pull/22849
<bitcoin-git>
[bitcoin] dongcarl opened pull request #22847: guix/prelude: Override `VERSION` with `FORCE_VERSION` (master...2021-08-SDE-based-on-VERSION) https://github.com/bitcoin/bitcoin/pull/22847
<bitcoin-git>
[bitcoin] darosior opened pull request #22846: policy: unit test Segwit dust thresholds (master...unit_test_getdustthreshold) https://github.com/bitcoin/bitcoin/pull/22846
<bitcoin-git>
[bitcoin] fanquake opened pull request #22845: build: improve check for ::(w)system (master...dont_literally_use_have_or_have) https://github.com/bitcoin/bitcoin/pull/22845
<bitcoin-git>
[bitcoin] josibake opened pull request #22844: feature: enable mypy to run without --ignore-imports (master...josibake-fix-mypy-import-errors) https://github.com/bitcoin/bitcoin/pull/22844
<bitcoin-git>
[bitcoin] fanquake opened pull request #22840: build: fix unoptimized libraries in depends (master...fix_depends_lib_optimisation) https://github.com/bitcoin/bitcoin/pull/22840
<laanwj>
ahh had a bit of a shock-my 0.22rc3 RISC-V node stopped syncing overnight, was looking into various things why it wasn't making connections, turns out to be an unstable wifi connection that dropped under load, phew--an annoying problem but completely bitcoin unrelated
<bitcoin-git>
[bitcoin] achow101 opened pull request #22838: descriptors: Be able to specify change and receiving in a single descriptor string (master...multipath-descs) https://github.com/bitcoin/bitcoin/pull/22838
<bitcoin-git>
[bitcoin] sipa opened pull request #22837: doc: mention bech32m/BIP350 in doc/descriptors.md (master...202108_bip350descdoc) https://github.com/bitcoin/bitcoin/pull/22837
<laanwj>
looks like there is no environment var to override bitcoin-wallet path, anyhow i've symlinked things into a fake "src" hierarchy already anyway
<MarcoFalke>
The bitcoin-util tests use bitcoin-util and bitcoin-cli
<vasild>
but if connecting directly and there is a bad spy looking at my ipv4 outgoing traffic they will learn I run bitcoin, which I may have tried to avoid by using -onlynet=ipv6
<bitcoin-git>
[bitcoin] hebasto opened pull request #22833: ci: Switch to Previous Visual Studio 2019 image to avoid failure (master...210830-appveyor) https://github.com/bitcoin/bitcoin/pull/22833
<bitcoin-git>
bitcoin/master 0bd882b Sebastian Falbesoner: refactor: remove RecursiveMutex cs_nBlockSequenceId
2021-08-29
<Bullit>
great monkey how there is soo much flakkee business etiquette 8.553FRACTAL bitcoin balance flushed to inferior BECH32 adress
<luke-jr>
kinda nuts how I got so much flak for being "too slow" to merge that questionable taproot BIP change, while so many other changes are still waiting for their authors' attention (who actually have funding to work on Bitcoin full time) -.- /minirant *cough*plsACKyourbips
<bitcoin-git>
[bitcoin] jonatack opened pull request #22831: p2p, bugfix: fix addrman tried table corruption on restart with asmap (master...addrman-asmap-init-order-test) https://github.com/bitcoin/bitcoin/pull/22831
<bitcoin-git>
[bitcoin] promag closed pull request #21906: refactor: Preserve const in cast on CTransactionSignatureSerializer (master...2021-05-fix-cast) https://github.com/bitcoin/bitcoin/pull/21906
<bitcoin-git>
[bitcoin] theStack opened pull request #22829: refactor: various RecursiveMutex replacements in CConnman (master...202108-refactor-recursive_mutex_replacements_in_cconnman) https://github.com/bitcoin/bitcoin/pull/22829
<bitcoin-git>
[bitcoin] fanquake opened pull request #22823: [0.21] Update version and release notes for 0.21.2rc2 (0.21...rc2_version_and_rel_notes) https://github.com/bitcoin/bitcoin/pull/22823
<saranshsharma>
I would like to understand this issue in bit clarity, I am thinking of helping on this issue could anyone here better probably share some insight or details to approach this... https://github.com/bitcoin/bitcoin/issues/22799
<gribble>
https://github.com/bitcoin/bitcoin/issues/22067 | Test and document a basic M-of-N multisig using descriptor wallets and PSBTs by mjdietzx · Pull Request #22067 · bitcoin/bitcoin · GitHub
<bitcoin-git>
[bitcoin] fanquake closed pull request #21144: test: convert feature_bip68_sequence.py to use MiniWallet (master...test-feature-bip68-sequence-without-wallet) https://github.com/bitcoin/bitcoin/pull/21144
<bitcoin-git>
[bitcoin] hebasto opened pull request #22814: build: Add ability to build qt in depends with -stdlib=libc++ (master...210827-libc++) https://github.com/bitcoin/bitcoin/pull/22814
2021-08-26
<bitcoin-git>
[bitcoin] fanquake merged pull request #21862: test: Set regtest.BIP65Height = 111 to speed up tests (master...2105-testFasterBip65) https://github.com/bitcoin/bitcoin/pull/21862
<bitcoin-git>
bitcoin/master faf7e48 MarcoFalke: Set regtest.BIP65Height = 111 to speed up tests
<bitcoin-git>
bitcoin/master adccbb3 fanquake: Merge bitcoin/bitcoin#21862: test: Set regtest.BIP65Height = 111 to speed ...
<bitcoin-git>
[bitcoin] hebasto opened pull request #22811: build: Fix depends build system when working with subtargets (master...210826-subtarget) https://github.com/bitcoin/bitcoin/pull/22811
<harding>
Differing mempool policies was actually anticipated, BIP125 says: "A Bitcoin Wiki page has been created to help wallet authors track deployed mempool policies relating to transaction replacement." which links to https://en.bitcoin.it/wiki/Transaction_replacement
<BlueMatt>
If you're trying to imply, michaelfolkson, that somehow bitcoin core review process is "fine" with a bip text saying something different than the implementation, I dont think thats ever been the case. mistakes happen, things are missed in review, but, indeed, its always been a thing that if the bip text disagrees with the implementation one or both need to be fixed.
<prayank>
Implementation of a BIP with some differences should be fine. Problem was not documenting these differences which was fixed in https://github.com/bitcoin/bitcoin/pull/21946
<bitcoin-git>
[bitcoin] MarcoFalke opened pull request #22809: test: Check that non-signaling BIP125 tx can be replaced via parent (master...2108-testTxReplace) https://github.com/bitcoin/bitcoin/pull/22809
<laanwj>
from a more holistic point of view about "bitcoin privacy" i don't think something like onlynet contributes much
<prayank>
michaelfolkson: Agree that privacy wiki has lot of interesting things. I respect Chris Belcher for his contributions in improving Bitcoin Privacy. The docs I was talky about were only for Bitcoin Core. Mainly Tor, i2p, wallet etc. This privacy wiki also needs some updates: Dandelion should be removed, i2p needs to be added, lot of things related to Tor (you can write few pages on just `onlynet`). Anyways it's just a suggestion.
<bitcoin-git>
[bitcoin] theStack opened pull request #22805: refactor: use CWallet const shared pointers in dump{privkey,wallet} (master...202108-refactor-const_correctness_for_further_dump_methods) https://github.com/bitcoin/bitcoin/pull/22805
<prayank>
Problem with Stackexchange and other places is you can write with more freedom and sometimes wrong things may not get noticed which in few years become a practice. Example: second paragraph in this comment by Greg Maxwell https://github.com/bitcoin/bitcoin/issues/17491#issuecomment-705485718
<laanwj>
(of course there are different perspectives, some people mean 'privacy' as in 'hiding that you're running a bitcoin node in the first place' which is... very difficult if impossible with overlay networks)
<michaelfolkson>
jonatack: Oh yeah :facepalm: I completely forgot about belcher's awesome privacy wiki. https://en.bitcoin.it/wiki/Privacy
<laanwj>
general privacy advice about using bitcoin spans much further than just using an overlay network, the most privacy-relevant in that regard is what you use to broadcast transactions
<jonatack>
that's true, the wiki is being used for repo project management. an article on your personal blog or website or (good point) on BitcoinStackExchange seems good, or https://en.bitcoin.it (still maintained?)
<bitcoin-git>
bitcoin/22.x c1c79f4 W. J. van der Laan: doc: Stop nixing `-` in manual pages
<bitcoin-git>
bitcoin/22.x 86de567 W. J. van der Laan: doc: Manual pages update for rc3
<bitcoin-git>
[gui] hebasto merged pull request #403: refactor: Make paths to update Encryption and HD wallet statuses simpler (master...210811-hd) https://github.com/bitcoin-core/gui/pull/403
<jonatack>
fanquake: i'm doing what i can to help them. that's the only reason for the docs. there are maybe ~30 users who have set up I2P with bitcoin, but i've heard from many of them.
<gribble>
https://github.com/bitcoin/bitcoin/issues/22647 | If both options "onion" and "proxy" are unset, no outbound Onion connections should be made · Issue #22647 · bitcoin/bitcoin · GitHub
<wired>
so you're a Bitcoin developer?
<bitcoin-git>
[bitcoin] klementtan opened pull request #22804: validation: GuessVerificationProgress returns 0 when no blocks downloaded (master...verification_progress_fix) https://github.com/bitcoin/bitcoin/pull/22804
<laanwj>
this is the development channel not bitcoin 101 channels