We should keep track of what BTC core is doing and potentially use kartograf to update our own asmap. Also, if BTC core produces a new asmap for a new release we should probably use it, since ours is old.
There is a lot of talk in BTC about asmap currently: https://btctranscripts.com/bitcoin-core-dev-tech/2023-04-27-asmap/
The comments here are especially interesting: https://gist.github.com/fjahr/bf0ff0917e03a4e49fac0617b2b35747
This is a new project that BTC core may use to update their asmap: https://github.com/fjahr/kartograf
We should keep track of what BTC core is doing and potentially use kartograf to update our own asmap. Also, if BTC core produces a new asmap for a new release we should probably use it, since ours is old.
Looking forward to seeing where kartograf leads us to get a new asmap.
I was attempting to update our asmap not long ago using what we used before, but ran into some upstream issues and logged the following issues, which are still unresolved
https://github.com/sipa/asmap/issues/11
https://github.com/sipa/asmap/issues/12
Looking forward to seeing where kartograf leads us to get a new asmap.
@jahway603 that file looks useful, it's meant to be human-readable so that devs can look at diffs of asmap changes. There should be some other script that can turn that txt file into a binary asmap.dat file
@jahway603 that file looks useful, it's meant to be human-readable so that devs can look at diffs of asmap changes. There should be some other script that can turn that txt file into a binary asmap.dat file
The repo https://github.com/fjahr/asmap-data has some actual .dat files that we could in theory use but they have the warning "Any data uploaded here should be treated with extreme caution and is not inteded for production use." so maybe we should just wait a bit longer for a more official data file?
There has been some movement related to asmap here: https://delvingbitcoin.org/t/asmap-creation-process/548
The repo https://github.com/fjahr/asmap-data has some actual .dat files that we could in theory use but they have the warning "Any data uploaded here should be treated with extreme caution and is not inteded for production use." so maybe we should just wait a bit longer for a more official data file?
This also has some interesting details: https://github.com/fjahr/asmap-data/issues/9
There is a lot of talk in BTC about asmap currently: https://btctranscripts.com/bitcoin-core-dev-tech/2023-04-27-asmap/
The comments here are especially interesting: https://gist.github.com/fjahr/bf0ff0917e03a4e49fac0617b2b35747
This is a new project that BTC core may use to update their asmap: https://github.com/fjahr/kartograf
We should keep track of what BTC core is doing and potentially use kartograf to update our own asmap. Also, if BTC core produces a new asmap for a new release we should probably use it, since ours is old.
I was attempting to update our asmap not long ago using what we used before, but ran into some upstream issues and logged the following issues, which are still unresolved
https://github.com/sipa/asmap/issues/11
https://github.com/sipa/asmap/issues/12
Looking forward to seeing where kartograf leads us to get a new asmap.
Also came across this asmap tool which may be helpful
https://github.com/brunoerg/asmapy
Related Issue #10
Ran kartograf and got the following asmap output.
@jahway603 that file looks useful, it's meant to be human-readable so that devs can look at diffs of asmap changes. There should be some other script that can turn that txt file into a binary asmap.dat file
We should check recent BTC releases (25.0 was release recently) to see if there is any new "official" asmap we can update to
I took a look at links above, still nothing I could find that looks useful
There has been some movement related to asmap here: https://delvingbitcoin.org/t/asmap-creation-process/548
The repo https://github.com/fjahr/asmap-data has some actual .dat files that we could in theory use but they have the warning "Any data uploaded here should be treated with extreme caution and is not inteded for production use." so maybe we should just wait a bit longer for a more official data file?
This also has some interesting details: https://github.com/fjahr/asmap-data/issues/9