< bitcoin-git>
[bitcoin] laanwj opened pull request #21192: cli: Treat high detail levels as maximum in -netinfo (master...2021-02-netinfo-verbosity) https://github.com/bitcoin/bitcoin/pull/21192
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21190: net: Avoid discouraging the onion proxy when one inbound onion misbehaves (master...2102-netOnionInboundDiscourage) https://github.com/bitcoin/bitcoin/pull/21190
< bitcoin-git>
[bitcoin] jonatack reopened pull request #21181: p2p: if no anchors.dat file, log a message instead of an error (master...log-message-instead-of-error-if-missing-anchors) https://github.com/bitcoin/bitcoin/pull/21181
< bitcoin-git>
bitcoin/master 0dbde70 Jon Atack: rpc: use GetNetworkNames() in getnetworkinfo and getpeerinfo helps
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21188: scripted-diff: Remove shadowing lock annotations in net processing (master...2102-netProcNoShadow) https://github.com/bitcoin/bitcoin/pull/21188
< bitcoin-git>
[bitcoin] jonatack closed pull request #21181: p2p: if no anchors.dat file, log a message instead of an error (master...log-message-instead-of-error-if-missing-anchors) https://github.com/bitcoin/bitcoin/pull/21181
< bitcoin-git>
[bitcoin] jnewbery opened pull request #21187: [net processing] Add Peer& arg to MaybeDiscourageAndDisconnect() (master...2021-02-getpeerlocaladdr) https://github.com/bitcoin/bitcoin/pull/21187
< bitcoin-git>
[bitcoin] jnewbery opened pull request #21186: Net/Net Processing: Move addr data into net_processing (master...2020-02-addr-in-peer) https://github.com/bitcoin/bitcoin/pull/21186
< bitcoin-git>
[bitcoin] jnewbery closed pull request #20925: RFC: Move Peer and PeerManagerImpl declarations to separate header (master...2021-01-peermanimplh) https://github.com/bitcoin/bitcoin/pull/20925
< bitcoin-git>
[bitcoin] MarcoFalke opened pull request #21185: fuzz: Remove expensive and redundant from cryto fuzz target (master...2102-speedupFuzz) https://github.com/bitcoin/bitcoin/pull/21185
< bitcoin-git>
[bitcoin] jonatack closed pull request #21171: Save client version to the settings file on shutdown (master...persist-version-on-shutdown) https://github.com/bitcoin/bitcoin/pull/21171
< bitcoin-git>
[bitcoin] jonatack opened pull request #21181: p2p: if no anchors.dat file, log a message instead of an error (master...log-message-instead-of-error-if-missing-anchors) https://github.com/bitcoin/bitcoin/pull/21181
< bitcoin-git>
[bitcoin] DariusParvin opened pull request #21178: test: run mempool_reorg.py even with wallet disabled (master...mempool-reorg-to-miniwallet) https://github.com/bitcoin/bitcoin/pull/21178
< prayank>
only "labelled" addresses belong to address book in bitcoin core wallet?
< luke-jr>
jonatack: anything in settings.json doubles as a bitcoin.conf option at least, on?
< bitcoin-git>
[bitcoin] jonatack opened pull request #21171: Save client version to the settings file on shutdown (master...persist-version-on-shutdown) https://github.com/bitcoin/bitcoin/pull/21171
< michaelfolkson>
"2021-02-13T11:42:47Z ERROR: DeserializeFileDB: Failed to open file /home/michael/.bitcoin/anchors.dat"
< michaelfolkson>
I'm not 100 percent clear on when you should open an issue in the Core repo if you get an error you are not expecting so posting here. Maybe this should be in #bitcoin even
< bitcoin-git>
[bitcoin] martinus opened pull request #21170: bench: Add benchmark to write JSON into a string (master...2021-02-benchmark-BlockToJsonVerboseWrite) https://github.com/bitcoin/bitcoin/pull/21170
< bitcoin-git>
[bitcoin] practicalswift opened pull request #21169: fuzz: Add RPC interface fuzzing. Increase fuzzing coverage from 65% to 70%. (master...fuzzing-rpc) https://github.com/bitcoin/bitcoin/pull/21169
< sipa>
sdaftuar: i only know of your bitcoin SE answer
< bitcoin-git>
[bitcoin] achow101 opened pull request #21166: Pass through SignatureExtractorChecker methods to base (master...fix-sig-extractor-checker) https://github.com/bitcoin/bitcoin/pull/21166
< wumpus>
this could tunnel the transaction over anything and would even work if bitcoin core doesn't itself use tor/i2p/etc
< wumpus>
right—one of the reasons we added -walletbroadcast=0 is to make it possible to do so with an external script (e.g. it was my idea with https://github.com/laanwj/bitcoin-submittx)
< bitcoin-git>
[bitcoin] laanwj merged pull request #19884: p2p: No delay in adding fixed seeds if -dnsseed=0 and peers.dat is empty (master...no-delay-fixed-peer-seeds) https://github.com/bitcoin/bitcoin/pull/19884
< bitcoin-git>
bitcoin/master e9c037b Wladimir J. van der Laan: Merge #19884: p2p: No delay in adding fixed seeds if -dnsseed=0 and peers....
< bitcoin-git>
bitcoin/master fe3e993 Dhruv Mehta: [p2p] No delay in adding fixed seeds if -dnsseed=0 and peers.dat is empty....
< bitcoin-git>
[bitcoin] laanwj merged pull request #19522: build: fix building libconsensus with reduced exports for Darwin targets (master...libconsensus_visibility_clang) https://github.com/bitcoin/bitcoin/pull/19522
< bitcoin-git>
bitcoin/master f054a08 fanquake: build: remove AX_GCC_FUNC_ATTRIBUTE test for dllimport
< bitcoin-git>
bitcoin/master 7cd0a69 fanquake: build: test for __declspec(dllexport) in configure
< gribble>
https://github.com/bitcoin/bitcoin/issues/16439 | cli/gui: support "@height" in place of blockhash for getblock on client side by ajtowns · Pull Request #16439 · bitcoin/bitcoin · GitHub
< sipa>
if you guix, presumably you got it in a way you're comfortable with, and if you have that - regardless of how you did so - you can build a reproducible bitcoin core release binary
< warren>
Should a goal of bitcoin's release reproduce the bootstrap of guix and challenge? Or you expect guix to be already somehow bootstrapped on your own?
< bitcoin-git>
[bitcoin] laanwj merged pull request #21041: log: Move "Pre-allocating up to position 0x[…] in […].dat" log message to debug category (master...pre-allocation-up-to-position-0xff-in-foo.dat) https://github.com/bitcoin/bitcoin/pull/21041
< bitcoin-git>
bitcoin/master 937dfa8 Wladimir J. van der Laan: Merge #21041: log: Move "Pre-allocating up to position 0x[…] in […].dat" l...
< bitcoin-git>
bitcoin/master 25f899c practicalswift: log: Move "Pre-allocating up to position 0x[...] in [...].dat" log message...
< dongcarl>
MarcoFalke: You can most likely garbage collect and get some space back. One thing on my list is to pin the latest manifest output so that it doesn't get garbage collected, so that you can safely garbage collect everything else without affecting bitcoin builds
< dongcarl>
FWIW: All guix package builds are offline (enforced by network namespaces I think) and hermetic. The bitcoin build script I wrote also builds in a completely offline environment by default.
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #20211: Use -Wswitch for TxoutType where possible (master...2010-WswitchTxoutType) https://github.com/bitcoin/bitcoin/pull/20211
< bitcoin-git>
bitcoin/master e498aef MarcoFalke: Merge #20211: Use -Wswitch for TxoutType where possible
< bitcoin-git>
bitcoin/master fa650ca MarcoFalke: Use -Wswitch for TxoutType where possible
< prusnak>
dongcarl: is there a Guix Docker image or what's the preferred way to build bitcoin w/ guix on macos ?
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #20915: fuzz: Fail if message type is not fuzzed (master...2101-fuzzFailMsgType) https://github.com/bitcoin/bitcoin/pull/20915
< bitcoin-git>
bitcoin/master a59e7ed MarcoFalke: Merge #20915: fuzz: Fail if message type is not fuzzed
< bitcoin-git>
bitcoin/master fa4bc89 MarcoFalke: fuzz: Fail if message type is not fuzzed
< bitcoin-git>
bitcoin/master faefed8 MarcoFalke: fuzz: Count message type fuzzers before main()
< fanquake>
achow: For doing a build of Bitcoin Core, something like: env ADDITIONAL_GUIX_COMMON_FLAGS='--no-substitutes --keep-failed' ADDITIONAL_GUIX_ENVIRONMENT_FLAGS='--bootstrap' `./contrib/guix/guix-build.sh (which will build for all hosts)
< bitcoin-git>
[bitcoin] maayank opened pull request #21141: Add new format string placeholders for walletnotify (master...walletnotify-blockhash) https://github.com/bitcoin/bitcoin/pull/21141
< bitcoin-git>
[bitcoin] fanquake opened pull request #21135: scripts: check for control flow instrumentation in security-check.py (master...security_check_cf_protection) https://github.com/bitcoin/bitcoin/pull/21135
< jonatack>
bitcoin conf : i2psam=127.0.0.1:7656 and i2pacceptincoming=1
< jonatack>
wumpus: idk, i2pd is the only one i've managed to have running with bitcoin
< jonatack>
wumpus: vasild: I've been using i2pd these past weeks, been working well for me. apt install i2pd / systemctl enable i2pd.service / systemctl start i2pd.service, update bitcoin.conf, done
< prayank>
luke-jr: sad but I will keep trying my best with my contribution and wumpus: Bitcoin Stackexchange is used as reference for lot of things/discussion including Bitcoin Core issues and PRs.
< michaelfolkson>
Right #bitcoin
< luke-jr>
prayank: Bitcoin's Stackexchange has a history of misinformation
< prayank>
wumpus: I think we were discussing about positives of Bitcoin Stackexchange few days back. Sad to see one of the moderators mentioning specific altcoins in answers when it could have been avoided. One of the altcoin mentioned in this answer has few people associated with it who spread misinformation about Bitcoin. And we have people with good reputation making these altcoins sound legit by mentioning in the answers.
< bitcoin-git>
[bitcoin] vasild opened pull request #21129: fuzz: check that ser+unser produces the same AddrMan (master...fuzz_addrman_serunser) https://github.com/bitcoin/bitcoin/pull/21129
< gribble>
https://github.com/bitcoin/bitcoin/issues/21121 | [test] Small unit test improvements, including helper to make mempool transaction by amitiuttarwar · Pull Request #21121 · bitcoin/bitcoin · GitHub