ASMap - Revision history

NotATether: Add Eclipse resistance, Map construction, and Status sections

2026-09-13T07:34:46Z

Add Eclipse resistance, Map construction, and Status sections

← Older revision		Revision as of 07:34, 13 September 2026
Line 1:		Line 1:
	'''ASMap''' (autonomous-system map) is a [[Bitcoin Core]] feature that maps IP address prefixes to autonomous system numbers (ASNs) so that peer selection can diversify by routing domain rather than by IP prefix alone. The goal is to make eclipse attacks that rely on many addresses in one network operator's space harder. ASMap is not a consensus rule.		'''ASMap''' (autonomous-system map) is a [[Bitcoin Core]] feature that maps IP address prefixes to autonomous system numbers (ASNs) so that peer selection can diversify by routing domain rather than by IP prefix alone. The goal is to make eclipse attacks that rely on many addresses in one network operator's space harder. ASMap is not a consensus rule.

			== Eclipse resistance ==

	Bitcoin Core's address manager groups peers into netgroups and avoids filling outbound slots from a single group. The historical grouping is a /16 prefix for IPv4 (and analogous prefix cuts for IPv6). A single autonomous system, especially a large hosting provider or transit network, commonly originates many /16s. The Erebus attack (Tran et al., 2020) showed that an AS on the victim's path can occupy those groups with addresses it already legitimately announces, without BGP hijacking, and eventually supply all of a victim's outbound peers. Mapping each address to the originating ASN and using the ASN as the netgroup collapses those prefixes into one bucket, so outbound diversity tracks administrative control of address space more closely than the /16 cut.		Bitcoin Core's address manager groups peers into netgroups and avoids filling outbound slots from a single group. The historical grouping is a /16 prefix for IPv4 (and analogous prefix cuts for IPv6). A single autonomous system, especially a large hosting provider or transit network, commonly originates many /16s. The Erebus attack (Tran et al., 2020) showed that an AS on the victim's path can occupy those groups with addresses it already legitimately announces, without BGP hijacking, and eventually supply all of a victim's outbound peers. Mapping each address to the originating ASN and using the ASN as the netgroup collapses those prefixes into one bucket, so outbound diversity tracks administrative control of address space more closely than the /16 cut.

			== Map construction ==

	An ASMap file is a compressed trie from IP prefix to ASN, produced from public routing data (BGP tables and related dumps). The Kartograf tooling used by the asmap-data project parses several sources deterministically so independent operators can rebuild the same file and compare hashes. Encoded maps suitable for Bitcoin Core are published in the bitcoin-core/asmap-data repository after coordinated reconstruction and review. When ASMap is enabled, AddrMan buckets and eviction use the ASN as the group identifier for IPv4 and IPv6 peers; Tor and I2P overlay addresses are not ASN-mapped the same way and keep their own network groups. The map is a snapshot. Routing tables change, so an old map mis-groups some prefixes; operators replace the file for a fresh map, and releases that embed a map update it around release time.		An ASMap file is a compressed trie from IP prefix to ASN, produced from public routing data (BGP tables and related dumps). The Kartograf tooling used by the asmap-data project parses several sources deterministically so independent operators can rebuild the same file and compare hashes. Encoded maps suitable for Bitcoin Core are published in the bitcoin-core/asmap-data repository after coordinated reconstruction and review. When ASMap is enabled, AddrMan buckets and eviction use the ASN as the group identifier for IPv4 and IPv6 peers; Tor and I2P overlay addresses are not ASN-mapped the same way and keep their own network groups. The map is a snapshot. Routing tables change, so an old map mis-groups some prefixes; operators replace the file for a fresh map, and releases that embed a map update it around release time.
Line 9:		Line 13:
	Operators who enable ASMap without trusting an embedded map can pass <code>-asmap</code> with a file whose hash they verified against asmap-data releases. Independent rebuilds that match the published hash increase confidence that the trie reflects the stated BGP inputs. A wrong ASN mapping does not steal funds. It only weakens or skews peer-diversity heuristics until the map is replaced.		Operators who enable ASMap without trusting an embedded map can pass <code>-asmap</code> with a file whose hash they verified against asmap-data releases. Independent rebuilds that match the published hash increase confidence that the trie reflects the stated BGP inputs. A wrong ASN mapping does not steal funds. It only weakens or skews peer-diversity heuristics until the map is replaced.

	AddrMan still combines several defenses. ASN bucketing is one input alongside feeler connections, eviction of underperforming peers, and limits on inbound slots from a single group. ASMap does not stop an attacker who controls many distinct ASNs or who sits on the victim's actual network path. It mainly raises the cost of packing many look-alike prefixes from one operator into every outbound bucket.		== Status ==

			AddrMan still combines several defenses. ASN bucketing is one input alongside feeler connections, eviction of underperforming peers, and limits on inbound slots from a single group. ASMap does not stop an attacker who controls many distinct ASNs or who sits on the victim's actual network path. It mainly raises the cost of packing many look-alike prefixes from one operator into every outbound bucket. Stale maps can mis-group new prefixes after routing changes. Operators who ship a custom asmap file should refresh it periodically and record which map hash the node loaded.

	== See also ==		== See also ==

NotATether: Expand See also links

2026-09-13T07:23:08Z

Expand See also links

← Older revision		Revision as of 07:23, 13 September 2026
Line 15:		Line 15:
	* [[Network]]		* [[Network]]
	* [[Erlay]]		* [[Erlay]]
			* [[Compact blocks]]

	== External links ==		== External links ==

NotATether: Add AddrMan context and residual eclipse risk

2026-09-13T07:23:06Z

Add AddrMan context and residual eclipse risk

← Older revision		Revision as of 07:23, 13 September 2026
Line 8:		Line 8:

	Operators who enable ASMap without trusting an embedded map can pass <code>-asmap</code> with a file whose hash they verified against asmap-data releases. Independent rebuilds that match the published hash increase confidence that the trie reflects the stated BGP inputs. A wrong ASN mapping does not steal funds. It only weakens or skews peer-diversity heuristics until the map is replaced.		Operators who enable ASMap without trusting an embedded map can pass <code>-asmap</code> with a file whose hash they verified against asmap-data releases. Independent rebuilds that match the published hash increase confidence that the trie reflects the stated BGP inputs. A wrong ASN mapping does not steal funds. It only weakens or skews peer-diversity heuristics until the map is replaced.

			AddrMan still combines several defenses. ASN bucketing is one input alongside feeler connections, eviction of underperforming peers, and limits on inbound slots from a single group. ASMap does not stop an attacker who controls many distinct ASNs or who sits on the victim's actual network path. It mainly raises the cost of packing many look-alike prefixes from one operator into every outbound bucket.

	== See also ==		== See also ==

NotATether: Add operator verification and failure mode

2026-09-13T07:23:04Z

Add operator verification and failure mode

← Older revision		Revision as of 07:23, 13 September 2026
Line 6:		Line 6:

	Bitcoin Core has accepted an ASMap file via <code>-asmap=<path></code> since version 0.20. Bitcoin Core 31.0 was the first release to embed a default map in the binary (the embedded dump was created on 5 March 2026). The feature remains off by default: <code>-asmap</code> or <code>-asmap=1</code> loads the embedded map, and <code>-asmap=filename</code> loads an external file. Builds can disable embedding with a compile option. ASMap does not encrypt traffic, authenticate peers, or stop an attacker who controls many independent ASNs, and it does not help if the victim has only one network path and that path is the adversary. It is one layer of eclipse mitigation alongside feeler connections, anchor connections, and optional overlay networks. No wallet behaviour depends on ASMap. Related [[Network]] topics include [[Erlay]] for transaction relay; Addr v2 and BIP324 are separate peer-address and transport work.		Bitcoin Core has accepted an ASMap file via <code>-asmap=<path></code> since version 0.20. Bitcoin Core 31.0 was the first release to embed a default map in the binary (the embedded dump was created on 5 March 2026). The feature remains off by default: <code>-asmap</code> or <code>-asmap=1</code> loads the embedded map, and <code>-asmap=filename</code> loads an external file. Builds can disable embedding with a compile option. ASMap does not encrypt traffic, authenticate peers, or stop an attacker who controls many independent ASNs, and it does not help if the victim has only one network path and that path is the adversary. It is one layer of eclipse mitigation alongside feeler connections, anchor connections, and optional overlay networks. No wallet behaviour depends on ASMap. Related [[Network]] topics include [[Erlay]] for transaction relay; Addr v2 and BIP324 are separate peer-address and transport work.

			Operators who enable ASMap without trusting an embedded map can pass <code>-asmap</code> with a file whose hash they verified against asmap-data releases. Independent rebuilds that match the published hash increase confidence that the trie reflects the stated BGP inputs. A wrong ASN mapping does not steal funds. It only weakens or skews peer-diversity heuristics until the map is replaced.

	== See also ==		== See also ==

NotATether: Fix ASMap snapshot sentence wording

2026-09-13T07:23:03Z

Fix ASMap snapshot sentence wording

← Older revision		Revision as of 07:23, 13 September 2026
Line 3:		Line 3:
	Bitcoin Core's address manager groups peers into netgroups and avoids filling outbound slots from a single group. The historical grouping is a /16 prefix for IPv4 (and analogous prefix cuts for IPv6). A single autonomous system, especially a large hosting provider or transit network, commonly originates many /16s. The Erebus attack (Tran et al., 2020) showed that an AS on the victim's path can occupy those groups with addresses it already legitimately announces, without BGP hijacking, and eventually supply all of a victim's outbound peers. Mapping each address to the originating ASN and using the ASN as the netgroup collapses those prefixes into one bucket, so outbound diversity tracks administrative control of address space more closely than the /16 cut.		Bitcoin Core's address manager groups peers into netgroups and avoids filling outbound slots from a single group. The historical grouping is a /16 prefix for IPv4 (and analogous prefix cuts for IPv6). A single autonomous system, especially a large hosting provider or transit network, commonly originates many /16s. The Erebus attack (Tran et al., 2020) showed that an AS on the victim's path can occupy those groups with addresses it already legitimately announces, without BGP hijacking, and eventually supply all of a victim's outbound peers. Mapping each address to the originating ASN and using the ASN as the netgroup collapses those prefixes into one bucket, so outbound diversity tracks administrative control of address space more closely than the /16 cut.

	An ASMap file is a compressed trie from IP prefix to ASN, produced from public routing data (BGP tables and related dumps). The Kartograf tooling used by the asmap-data project parses several sources deterministically so independent operators can rebuild the same file and compare hashes. Encoded maps suitable for Bitcoin Core are published in the bitcoin-core/asmap-data repository after coordinated reconstruction and review. When ASMap is enabled, AddrMan buckets and eviction use the ASN as the group identifier for IPv4 and IPv6 peers; Tor and I2P overlay addresses are not ASN-mapped the same way and keep their own network groups. The map is a snapshot ~~routing~~ tables change, so an old map mis-groups some prefixes; operators replace the file for a fresh map, and releases that embed a map update it around release time.		An ASMap file is a compressed trie from IP prefix to ASN, produced from public routing data (BGP tables and related dumps). The Kartograf tooling used by the asmap-data project parses several sources deterministically so independent operators can rebuild the same file and compare hashes. Encoded maps suitable for Bitcoin Core are published in the bitcoin-core/asmap-data repository after coordinated reconstruction and review. When ASMap is enabled, AddrMan buckets and eviction use the ASN as the group identifier for IPv4 and IPv6 peers; Tor and I2P overlay addresses are not ASN-mapped the same way and keep their own network groups. The map is a snapshot. Routing tables change, so an old map mis-groups some prefixes; operators replace the file for a fresh map, and releases that embed a map update it around release time.

	Bitcoin Core has accepted an ASMap file via <code>-asmap=<path></code> since version 0.20. Bitcoin Core 31.0 was the first release to embed a default map in the binary (the embedded dump was created on 5 March 2026). The feature remains off by default: <code>-asmap</code> or <code>-asmap=1</code> loads the embedded map, and <code>-asmap=filename</code> loads an external file. Builds can disable embedding with a compile option. ASMap does not encrypt traffic, authenticate peers, or stop an attacker who controls many independent ASNs, and it does not help if the victim has only one network path and that path is the adversary. It is one layer of eclipse mitigation alongside feeler connections, anchor connections, and optional overlay networks. No wallet behaviour depends on ASMap. Related [[Network]] topics include [[Erlay]] for transaction relay; Addr v2 and BIP324 are separate peer-address and transport work.		Bitcoin Core has accepted an ASMap file via <code>-asmap=<path></code> since version 0.20. Bitcoin Core 31.0 was the first release to embed a default map in the binary (the embedded dump was created on 5 March 2026). The feature remains off by default: <code>-asmap</code> or <code>-asmap=1</code> loads the embedded map, and <code>-asmap=filename</code> loads an external file. Builds can disable embedding with a compile option. ASMap does not encrypt traffic, authenticate peers, or stop an attacker who controls many independent ASNs, and it does not help if the victim has only one network path and that path is the adversary. It is one layer of eclipse mitigation alongside feeler connections, anchor connections, and optional overlay networks. No wallet behaviour depends on ASMap. Related [[Network]] topics include [[Erlay]] for transaction relay; Addr v2 and BIP324 are separate peer-address and transport work.

NotATether: Create ASMap stub: Bitcoin Core ASN-based peer netgroups (eclipse mitigation); -asmap since 0.20, embedded map in 31.0 off by default; not consensus

2026-09-12T21:18:15Z

Create ASMap stub: Bitcoin Core ASN-based peer netgroups (eclipse mitigation); -asmap since 0.20, embedded map in 31.0 off by default; not consensus

New page

'''ASMap''' (autonomous-system map) is a [[Bitcoin Core]] feature that maps IP address prefixes to autonomous system numbers (ASNs) so that peer selection can diversify by routing domain rather than by IP prefix alone. The goal is to make eclipse attacks that rely on many addresses in one network operator's space harder. ASMap is not a consensus rule.

Bitcoin Core's address manager groups peers into netgroups and avoids filling outbound slots from a single group. The historical grouping is a /16 prefix for IPv4 (and analogous prefix cuts for IPv6). A single autonomous system, especially a large hosting provider or transit network, commonly originates many /16s. The Erebus attack (Tran et al., 2020) showed that an AS on the victim's path can occupy those groups with addresses it already legitimately announces, without BGP hijacking, and eventually supply all of a victim's outbound peers. Mapping each address to the originating ASN and using the ASN as the netgroup collapses those prefixes into one bucket, so outbound diversity tracks administrative control of address space more closely than the /16 cut.

An ASMap file is a compressed trie from IP prefix to ASN, produced from public routing data (BGP tables and related dumps). The Kartograf tooling used by the asmap-data project parses several sources deterministically so independent operators can rebuild the same file and compare hashes. Encoded maps suitable for Bitcoin Core are published in the bitcoin-core/asmap-data repository after coordinated reconstruction and review. When ASMap is enabled, AddrMan buckets and eviction use the ASN as the group identifier for IPv4 and IPv6 peers; Tor and I2P overlay addresses are not ASN-mapped the same way and keep their own network groups. The map is a snapshot routing tables change, so an old map mis-groups some prefixes; operators replace the file for a fresh map, and releases that embed a map update it around release time.

Bitcoin Core has accepted an ASMap file via <code>-asmap=<path></code> since version 0.20. Bitcoin Core 31.0 was the first release to embed a default map in the binary (the embedded dump was created on 5 March 2026). The feature remains off by default: <code>-asmap</code> or <code>-asmap=1</code> loads the embedded map, and <code>-asmap=filename</code> loads an external file. Builds can disable embedding with a compile option. ASMap does not encrypt traffic, authenticate peers, or stop an attacker who controls many independent ASNs, and it does not help if the victim has only one network path and that path is the adversary. It is one layer of eclipse mitigation alongside feeler connections, anchor connections, and optional overlay networks. No wallet behaviour depends on ASMap. Related [[Network]] topics include [[Erlay]] for transaction relay; Addr v2 and BIP324 are separate peer-address and transport work.

== See also ==
* [[Bitcoin Core]]
* [[Network]]
* [[Erlay]]

== External links ==
* [https://asmap.org/ ASMap project]
* [https://github.com/bitcoin/bitcoin/blob/master/doc/asmap-data.md Bitcoin Core ASMap data documentation]
* [https://github.com/bitcoin-core/asmap-data bitcoin-core/asmap-data (encoded maps)]
* [https://bitcoincore.org/en/releases/31.0/ Bitcoin Core 31.0 release notes (embedded ASMap)]
* [https://github.com/bitcoin/bips/blob/master/bip-0324.mediawiki BIP 324 (encrypted P2P transport)]

[[Category:Technical]]