Chris_Stewart_5: would the section in doc/tor.md "Manually create a Bitcoin Core onion service" do what you want? e.g.
1. It allows inbound connections, 2. Doesn't gossip the peer address across the bitcoin network
information leakage is kept to a minimum, too, with an extra P2P connection in bitcoin core there's always the risk of some fingerprinting vector we don't yet know of, for example
If you are using a node it will broadcast transactions. If it is not using Tor/i2p which most of the nodes do, your peers can keep an eye on your transactions. Let's assume every time I launch Bitcoin Core it connects with 3 spy nodes. This functionality can improve privacy by making it difficult for spy nodes to follow specific pattern. But I agree few things are best when added as plugins. Unfortunately we don't have plugins in Core.
that's what I'd generally expect, but i dunno many/any lightning devs who follow bitcoin core closely enough to ensure that, which is part of the reason for me flagging now that non-v0 segwit output dust limit *also* falls under the "plz notify lightning devs and give us time to adapt before you change this" category
Sure, but I think Bitcoin Core's open development process has a pretty strong commitment to listening to LN devs and other ecosystem devs, so I think that's implicitly covered
sure, but that kind of thing requires at least a loose commitment from bitcoin core to do dust limit changes in a way that is compatible with that :p
"charity" of reducing total bitcoin supply :)
Sure, but if feerates increase significantly (and that certainly seems like a plausible scenario), those problems are going to need to be dealt with anyway. I don't think we should be forcing anyone to deal with those problems now, but I also kinda feel like some of the attention on the dust limit problem should be focused on improving LN rather than changing Bitcoin Core.
LN doesn't need to use the same dust limit Bitcoin Core does. Y'all can choose to treat as dust outputs that would cost more to spend than they're worth at 20 s/b, and so be insulated against any reasonable change in Bitcoin Core (especially since changes in Bitcoin Core should take a long time to become predominant across relay and mining).
bitcoin-cli prints "timeout on transient error: ..." when the RPC port is not open, this is slightly confusing (though it does appropriately print a message about bitcoind not running afterwards)
[bitcoin] theStack opened pull request #22711: test: check for specific block reject reasons in p2p_segwit.py (master...202108-test-check_specific_segwit_reject_reasons) https://github.com/bitcoin/bitcoin/pull/22711
[bitcoin] mjdietzx opened pull request #22707: test: improve mempool_updatefrom efficiency by using getmempoolentry for specific txns (master...test_improve_mempool_updatefromblock_efficiency) https://github.com/bitcoin/bitcoin/pull/22707
[bitcoin] stratospher opened pull request #22704: fuzz: Differential fuzzing to compare Bitcoin Core's and D. J. Bernstein's implementation of ChaCha20 (master...diff-fuzz-chacha20) https://github.com/bitcoin/bitcoin/pull/22704
[bitcoin] mjdietzx opened pull request #22698: Fix CVE-2021-31876 RBF inherited signaling and fixes getmempoolentry returned bip125-replaceable status (master...fix_bip125_inherited_signaling) https://github.com/bitcoin/bitcoin/pull/22698
so, the bit-defender software looked inside the 0.15.1 DMG and specifically had a problem with Bitcoin-Qt.app/Contents/MacOS/BITCOIN_QT
Bitcoin Core is frequently incorrectly flagged as malware because it searchs for a wallet.dat file and includes mining code
some AVs have added exceptions for some versions of Bitcoin Core
but i have other version of bitcoin core .dmgs on my computers and that antivirus software didnt flag those
then i checked each files hash to the hash on the bitcoin.org depository (https://bitcoin.org/bin/insecure-CVE-2018-17144/bitcoin-core-0.15.1/), and they matched perfectly ... so then i downloaded 0.15.1 off of the depository and ran it through the virus scanner and got the same warning that it had a virus. so the one hosted on bitcoin.org got
i had an old copy of the bitcoin core 0.15.1 DMG file on my mac, and recently installed BitDefender anti-virus (from the Mac App Store), and it said that it had a virus in it: Application.MAC.Miner.NB inside the DMG, specifically Bitcoin-Qt.app/Contents/MacOS/BITCOIN_QT