< meshcollider> promag: will try my best ;)
< bitcoin-git> [bitcoin] MarcoFalke opened pull request #20399: Revert "Merge #19606: Backport wtxid relay to v0.20" (0.20...2011-prepare020release) https://github.com/bitcoin/bitcoin/pull/20399
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/0ede354367c4...2fa085a5d752
< bitcoin-git> bitcoin/master 89836a8 Vasil Dimov: style: minor improvements as a followup to #19845
< bitcoin-git> bitcoin/master 2fa085a MarcoFalke: Merge #20033: refactor: minor whitespace fixups, s/const/constexpr/ and re...
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20033: refactor: minor whitespace fixups, s/const/constexpr/ and remove template (followup to #19845) (master...nits_followup_to_19845) https://github.com/bitcoin/bitcoin/pull/20033
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/2fa085a5d752...37a463481176
< bitcoin-git> bitcoin/master 20e491d Luke Dashjr: CI/Cirrus: Skip merge_base step for non-PRs
< bitcoin-git> bitcoin/master 37a4634 MarcoFalke: Merge #20390: CI/Cirrus: Skip merge_base step for non-PRs
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20390: CI/Cirrus: Skip merge_base step for non-PRs (master...cirrus_nonpr_fix) https://github.com/bitcoin/bitcoin/pull/20390
< bitcoin-git> [bitcoin] hebasto closed pull request #20366: scripted-diff: Fix includes when secp256k1 is locally installed on macOS (master...201111-incl) https://github.com/bitcoin/bitcoin/pull/20366
< wumpus> meshcollider: congratulations !!!
< bitcoin-git> [bitcoin] mateusz-klatt closed pull request #20361: Descriptor Wallets BIP39 recovery (master...master) https://github.com/bitcoin/bitcoin/pull/20361
< vasild> meshcollider: Cheerz! o/
< bitcoin-git> [bitcoin] MarcoFalke pushed 2 commits to master: https://github.com/bitcoin/bitcoin/compare/37a463481176...1e17114917f2
< bitcoin-git> bitcoin/master 9c08f33 kanon: doc: Missing comments for signet parameters
< bitcoin-git> bitcoin/master 1e17114 MarcoFalke: Merge #20238: doc: Missing comments for signet parameters
< bitcoin-git> [bitcoin] MarcoFalke merged pull request #20238: doc: Missing comments for signet parameters (master...patch-1) https://github.com/bitcoin/bitcoin/pull/20238
< bitcoin-git> [bitcoin] laanwj pushed 11 commits to master: https://github.com/bitcoin/bitcoin/compare/1e17114917f2...c48e788246fc
< bitcoin-git> bitcoin/master 842ae38 Andrew Chow: wallet: Add utility method for CanSupportFeature
< bitcoin-git> bitcoin/master 5f72054 Andrew Chow: wallet: Add GetClosestWalletFeature function
< bitcoin-git> bitcoin/master bd7398c Andrew Chow: wallet: have ScriptPubKeyMan::Upgrade check against the new version
< bitcoin-git> [bitcoin] laanwj merged pull request #18836: wallet: upgradewallet fixes and additional tests (master...upgradewallet-tests) https://github.com/bitcoin/bitcoin/pull/18836
< bitcoin-git> [bitcoin] laanwj opened pull request #20401: qt: Pre-splitoff translations update (master...2020_11_translations_update) https://github.com/bitcoin/bitcoin/pull/20401
< jonasschnelli> meshcollider: nice!
< provoostenator> sipa: is there a step between downloading the files with asmap-rs and the your bitcoin-asmap encode incantation in #18573?
< gribble> https://github.com/bitcoin/bitcoin/issues/18573 | [RFC] bitcoin-asmap utility by sipa · Pull Request #18573 · bitcoin/bitcoin · GitHub
< provoostenator> Because I now have a dump directory with rrc**-latest-bview.gz, but it seems need to do something to produce asmap.txt
< sipa> you first need to run the asmap-rs find prefix stuff iirc
< provoostenator> Is that what the find-bottleneck command does? Its purpose isn't really explained...
< sipa> yes, that!
< provoostenator> cc gleb
< provoostenator> What is that doing?
< provoostenator> Or phrased differently: what is "the AS bottleneck"?
< sipa> it determines if all paths to a particular ASN go through a certain suffix, that suffix is stripped off
< sipa> finding the bottleneck for all connections
< provoostenator> From where?
< sipa> from everywhere
< provoostenator> From everywhere to everywhere?
< sipa> so say that all paths (from everywhere) to ASN 1234 are {4, 15, 37, 123, 1234}, {3, 12, 37, 123, 1234}, {16, 200, 123, 1234}
< provoostenator> So an example would be some lonely company network that's only reachable via a single ISP?
< sipa> then it will say 123 is the bottleneck to 1234
< sipa> and it means that really network 123 count easily hijack all connections to 1234
< sipa> and instead, the IP range of 1234 will be mapped as 123, rather than as 1234
< provoostenator> That makes sense
< provoostenator> Would be nice to get a personalized view too given my own IP (for > N hops, since most people are eclypsed by their ISP).
< sipa> you'll need to ask your ISP for a BGP dump then
< sipa> you don't have access to those directly normally
< provoostenator> Wouldn't I be able to use this same file, and just figure out which AS I'm on?
< sipa> which file?
< provoostenator> The raw data asmap-rs is downloading.
< sipa> it's not downloading things from your ISP
< sipa> presumably
< sipa> unless you're using on of the sources
< provoostenator> This seems like useful background info: https://www.ripe.net/publications/docs/ripe-200
< bitcoin-git> [bitcoin] jonatack opened pull request #20403: wallet: upgradewallet fixes, improvements, test coverage (master...upgradewallet-improvements) https://github.com/bitcoin/bitcoin/pull/20403
< bitcoin-git> [bitcoin] hebasto opened pull request #20404: Remove names from translatable strings (master...201116-tr) https://github.com/bitcoin/bitcoin/pull/20404
< bitcoin-git> [bitcoin] lontivero opened pull request #20405: Avoid calculating onion address checksum when version is not 3 (master...tinyrefactoring) https://github.com/bitcoin/bitcoin/pull/20405
< provoostenator> Ok, it's actually pretty easy to generate the asmap file and use it, but the instructions could be better...
< sipa> provoostenator: fwiw my plan is to create a separate project with asmap encoding tools
< sipa> but haven't gotten around to it
< sipa> as we'll probably want some kind of "asmap diff" tool too, for auditing
< provoostenator> Some of the RRC files are ancient(e.g. rrc02 last updated 2008). Do we fetch all or filter for recency?
< sipa> oh wow, i wasn't aware of that
< sipa> we probably should
< sipa> it's not information that goes outdated quickly, but if it's more than a year i guess it's useless
< provoostenator> I only noticed because I wondered what interval they're updated
< provoostenator> So e.g. if we were to include it in core, how much time other reviewers can verify the result (probably forever since they also keep previous versions)
< bitcoin-git> [bitcoin] practicalswift opened pull request #20406: util: Avoid invalid integer negation in FormatMoney and ValueFromAmount (master...avoid-invalid-integer-negation-in-FormatMoney) https://github.com/bitcoin/bitcoin/pull/20406