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
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
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
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.
bitcoin/master 78d39f8 fanquake: Merge bitcoin/bitcoin#22861: test: Update test README and lint script
[bitcoin] theStack opened pull request #22896: refactor: net: avoid duplicate map lookups to `mapLocalHost` (master...202109-refactor-net-avoid_duplicate_mapLocalHost_lookups) https://github.com/bitcoin/bitcoin/pull/22896
Does anyone know why bitcoin core would only relay 101 headers in response to a `GetHeaders(...,stopHash=0x0000...000)` message when it has 113 headers locally? Specifically on regtest
Not sure if anything related changed in merged PRs (last few weeks). I observed it takes less time to compile Bitcoin Core now. Don't have any numbers. Maybe I will try compiling 0.21 and compare with Master.
bitcoin/master 629c4ab Samuel Dobson: Merge bitcoin/bitcoin#22100: refactor: Clean up new wallet spend, receive ...
bitcoin/master b11a195 Russell Yanofsky: refactor: Detach wallet transaction methods (followup for move-only)
[bitcoin] JeremyRubin opened pull request #22876: [TESTS] Update Transaction Tests to permit setting a flag as always on and disabling the exhaustive failure test (master...update-txvalid-json) https://github.com/bitcoin/bitcoin/pull/22876
[bitcoin] MarcoFalke closed pull request #22870: [TESTS] Update Transaction Tests to permit setting a flag as always on and disabling the exhaustive failure test (master...update-txvalid-json) https://github.com/bitcoin/bitcoin/pull/22870
[bitcoin] JeremyRubin opened pull request #22870: [TESTS] Update Transaction Tests to permit setting a flag as always on and disabling the exhaustive failure test (master...update-txvalid-json) https://github.com/bitcoin/bitcoin/pull/22870
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
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)
Cool you are contributing to Learning Bitcoin from Command Line
Not reusing a bitcoin adress is a best practice
Error: '#bitcoin-otc:8f2f03563f52e38a1022450907e9108c382606db9dfba6f1284e3bac' is not a valid http url.
Error: In order to authenticate, you must be present in one of the following channels: #bitcoin-otc;#bitcoin-bans;#gribble
Request successful for user gnaf, hostmask firstname.lastname@example.org. Your challenge string is: zirconium.libera.chat:#bitcoin-otc:8f2f03563f52e38a1022450907e9108c382606db9dfba6f1284e3bac