< bitcoin-git>
[bitcoin] glozow opened pull request #20895: p2p: mildly discourage peers that violate feefilter (master...p2p-feefilter-violations) https://github.com/bitcoin/bitcoin/pull/20895
< bitcoin-git>
[gui] jonatack opened pull request #179: gui: add direction and type columns to peers window (master...add-peers-dir-and-type-columns) https://github.com/bitcoin-core/gui/pull/179
< jamesob>
(veering off topic) what's the easiest way for non-technical end users to enable that; just editing bitcoin.conf?
< jamesob>
bitcoin-qt doesn't start the RPC server by default? I didn't see anything in the GUI configuration for it, so I assume it did it by default
< jamesob>
running bitcoin-qt, can access RPC via the console view, but oh, can't see *8332 in lsof
< sipa>
don't have -server=0 or running bitcoin-qt?
< jamesob>
I don't think so - I'm `ls`ing the datadir and seeing debug.log/bitcoin.conf I expect, but no cookie file
< bitcoin-git>
[bitcoin] achow101 opened pull request #20892: tests: Run both descriptor and legacy tests within a single test invocation (master...better-descriptor-tests) https://github.com/bitcoin/bitcoin/pull/20892
< bitcoin-git>
[bitcoin] mjdietzx opened pull request #20889: test: ensure any failing method in MiniWallet leaves no side-effects (master...test-miniwallet-no-side-effects) https://github.com/bitcoin/bitcoin/pull/20889
< sipa>
i would just say "Bitcoin Core 0.21.0 includes an implementation of the proposed Taproot (BIP 341-342) consensus rules, without activation for mainnet. Experimenting with Taproot can be done on the new Signet network where it is already active. Activation parameters will likely be included in a future minor release, and the proposed rules will not be enforced without upgrading to it."
< luke-jr>
there is no forum of discussion for all bitcoin users
< luke-jr>
so companies decide Bitcoin protocol rules now?
< sipa>
you seem to want to use adoption of bitcoin core as telemetry (even if not through an explicit call-home)
< sipa>
i'm just mentioning this because i saw https://github.com/bitcoin-core/packaging/issues/55, and it seems doing it inside gitian is an almost trivial change for us, apart from some initial work to set up the scripts
< wumpus>
right, the point is that bitcoin needs *special* review compared to upgrading other software
< wumpus>
but so is auto-updating bitcoin core in general
< luke-jr>
Debian wants to include bitcoin core again
< gribble>
https://github.com/bitcoin/bitcoin/issues/16702 | p2p: supplying and using asmap to improve IP bucketing in addrman by naumenkogs · Pull Request #16702 · bitcoin/bitcoin · GitHub
< bitcoin-git>
[bitcoin] jonatack opened pull request #20877: netinfo: user help and argument parsing improvements (master...netinfo-help-follow-ups) https://github.com/bitcoin/bitcoin/pull/20877
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #20789: fuzz: Rework strong and weak net enum fuzzing (master...2012-fuzzRefactor) https://github.com/bitcoin/bitcoin/pull/20789
< jonatack>
jonasschnelli: maybe from bitcoin acks
< bitcoin-git>
[bitcoin] stackman27 opened pull request #20874: test: Run mempool_limit.py even with wallet disabled (master...diswallet_mempoollimit) https://github.com/bitcoin/bitcoin/pull/20874
< bitcoin-git>
[bitcoin] darosior opened pull request #20867: Support up to 20 keys for multisig under Segwit context (master...descriptor_multi_wsh) https://github.com/bitcoin/bitcoin/pull/20867
< bitcoin-git>
[bitcoin] sipa opened pull request #20861: Implement Bech32m and use it for v1+ segwit addresses (master...202101_bech32m) https://github.com/bitcoin/bitcoin/pull/20861
< vasild>
jonatack: wrt https://github.com/bitcoin/bitcoin/pull/20849#issuecomment-754602325 -- I can reproduce the issue and was about to reply to your comment, but I wonder if that can be perceived as a step-by-step guide on how to create an evil node on the network that can circumvent the discouragement mechanism of anybody who connects to it...
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #19915: p2p, refactor: Use Mutex type for some mutexes in CNode class (master...200908-netmx) https://github.com/bitcoin/bitcoin/pull/19915
< bitcoin-git>
bitcoin/master 417f95f MarcoFalke: Merge #19915: p2p, refactor: Use Mutex type for some mutexes in CNode clas...
< bitcoin-git>
bitcoin/master 0e51a35 Hennadii Stepanov: refactor: Use Mutex type for some mutexes in CNode class
< bitcoin-git>
[bitcoin] PiRK opened pull request #20857: update docstring in feature_csv_activation.py to account for 17921 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/20857
< bitcoin-git>
bitcoin/master a0eb4c5 Pieter Wuille: Revert "Add patch to make codesign_allocate compatible with Apple's"
< jonasschnelli>
Users just care about a valid signature. Anyone can register at apple, get a valid signing key and sign a mallicious bitcoin core binary.
< jonasschnelli>
the private key is property of "Bitcoin Core Code Signing Association" (this is no joke).
< sipa>
tiny downside... anyone could sign binaries pretending to be bitcoin core
< bitcoin-git>
[bitcoin] sipa opened pull request #20855: Revert "Add patch to make codesign_allocate compatible with Apple's" (master...202101_revert_codesign_allocate_hack) https://github.com/bitcoin/bitcoin/pull/20855
< jonasschnelli>
As for rc4: i tried on macOS 11, verified the hash of bitcoin-0.21.0rc4-osx-unsigned.tar.gz (matched the others), verified the patched codesign_allocate, signed locally, verified the signed app (ok), gbuilt the signer with the created signature (failed)
< jonasschnelli>
the detached-sig-apply.sh takes the binary in bitcoin-0.21.0rc3-osx-unsigned.tar.gz, right?
< jonasschnelli>
^ the codesign_allocate is part of the bitcoin-0.21.0rc3-osx-unsigned.tar.gz? right?
< bitcoin-git>
[bitcoin] vasild opened pull request #20849: net: disconnect peers by address without using a subnet (master...disconnect_by_subnet_fix) https://github.com/bitcoin/bitcoin/pull/20849
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #20845: net: Log to net debug in MaybeDiscourageAndDisconnect except for noban and manual peers (master...2101-netLogDisconnect) https://github.com/bitcoin/bitcoin/pull/20845
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #20844: test: Add sanitizer suppressions for AMD EPYC CPUs (master...2101-testEpycSan) https://github.com/bitcoin/bitcoin/pull/20844
< bitcoin-git>
[bitcoin] hebasto closed pull request #20824: build: Do not set _FORTIFY_SOURCE if it causes compiler warnings (master...210101-fortify) https://github.com/bitcoin/bitcoin/pull/20824
< jonasschnelli>
used the signature to gbuild the signer: ./bin/gbuild --num-make 6 -j11 --memory 5000 --url bitcoin=/home/jonasschnelli/gitian/bitcoin --commit signature=v0.21.0rc4
< jonasschnelli>
Created the signature: ./detached-sig-create.sh -s "Bitcoin"
< jonasschnelli>
- Verified bitcoin-0.21.0rc4-osx-unsigned.tar.gz, got the correct 10ae57ee735cd2a894a75165082c384769da3b634eca9346b1d20585e1edfd0c
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #20736: rpc: Replace boost::variant with std::variant for RPCArg.m_fallback (master...2012-rpcStdVariant) https://github.com/bitcoin/bitcoin/pull/20736
< bitcoin-git>
bitcoin/master bc8ada1 MarcoFalke: Merge #20736: rpc: Replace boost::variant with std::variant for RPCArg.m_f...
< bitcoin-git>
bitcoin/master fa749fb MarcoFalke: rpc: Replace boost::variant with std::variant for RPCArg.m_fallback