Get the list of IPs known to your node and save them to the file peers_ips.txt
. Then count how many IPs are in the file.
$ src/bitcoin-cli getnodeaddresses 0 | jq -r '.[] | .address' > peer_ips.txt
$ wc -l peer_ips.txt
Get the list of IPs known to your node and save them to the file peers_ips.txt
. Then count how many IPs are in the file.
$ src/bitcoin-cli getnodeaddresses 0 | jq -r '.[] | .address' > peer_ips.txt
$ wc -l peer_ips.txt
To get a general overview/refresher of the ASMap project please (re)read the post from Gleb on the Bitmex blog [1]. What is described there is still the status of ASMap file data sources to my knowledge.
Some further questions of mine about the process were discussed in November 2021 in an IRC meeting [2]. It was discussed that fresh ASMap files will be generated for and shipped with every release. The historic files that are part of the releases should be available in a separate repository under the bitcoin core GitHub organization. It was also discussed where the tools used during the release process should be maintained.
Since then, my focus has been on what would be the best possible data sources and quality assurance process for the input data of the ASMap file, i.e., a prefix to AS mapping that most accurately reflect the reality of the internet and that stays up to date for as long as possible.
For reference, see the general release schedule of v25.0 here: bitcoin/bitcoin#26549
For discussion of https://github.com/bitcoin/bitcoin/pull/24008/commits/c14ae132c5a5204a9a755c84c6de05fb30459221
if(!m_snapshot_chainstate)
=> use ibd
if(m_blockman.LookupBlockIndex(blockhash) == nullptr)
=> use snapshot
m_block_index
if (!m_snapshot_chainstate->m_chain.Contains(pblock)))
=> use snapshot
m_chain
) which can mean we have not validated the full block yet or the block is not part of the best chain after validationibd