All the updates per the release process, except asmap.
Assumeutxo snapshots are available at https://achow101.com/files/utxo-snapshots/
All the updates per the release process, except asmap.
Assumeutxo snapshots are available at https://achow101.com/files/utxo-snapshots/
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/36196.
<!--021abf342d371248e50ceaed478a90ca-->
See the guideline and AI policy for information on the review process. A summary of reviews will appear here.
<!--5faf32d7da4f0f540f40219e4f7537a3-->
The asmap benchmark thinks that the address 3fff::1 belongs to AS16509. Not sure if the bug is in the asmap file or our parser.
Edit:
Hmm
::/2 AS16509
I think it's the asmap file.
Dropped the asmap update. I believe this is just an encoding issue where asmap-tool is not accounting for prefixes that are not supposed to be reachable. All asmaps more recent than the current embedding contain the problematic mapping.
I am looking into it and working on a fix for handling it better in core. While we aren't filtering this new-ish RFC 9637 explicitly in kartograf I think the mapping is introduced by the --fill the encoding.
#36201 should hopefully show that the CI is fixed through https://github.com/bitcoin/bitcoin/pull/36199
While we aren't filtering this new-ish RFC 9637 explicitly in kartograf I think the mapping is introduced by the
--fillthe encoding.
fwiw:
Milestone
32.0