No Tor, no asmap, no block filters — network resilience features a low-peer chain needs more than Bitcoin does #42

New issue

Open

opened 2026-09-15 01:51:26 +00:00 by btcbob · 0 comments

btcbob commented

2026-09-15 01:51:26 +00:00

Owner

Roadmap section 5 (forum topic 24, msg 68), filed so it is tracked rather than prose.

Where we are

Confirmed absent from src/:

No Tor control support. There is no torcontrol.cpp. The node cannot create
or advertise an onion service, so reachability depends entirely on a clear-net
IP and whatever the hosting provider does.
No asmap. src/addrman.cpp buckets peers by IP range only; there is no
ASN-aware bucketing.
No compact block filters (BIP157/158) and no BIP324 v2 encrypted transport.

Why this matters more here than upstream

Every one of these is worth more to a chain with few honest peers than to Bitcoin,
for the same reason: the smaller the honest peer set, the cheaper it is to
surround a node.

asmap (Core 0.20) buckets by network topology rather than address, which is
the specific defence against an eclipse attack mounted from one provider. On a
network where a single operator could plausibly run a large fraction of reachable
nodes, this is cheap insurance with an outsized payoff.
Tor v3 (0.21) gives nodes that survive a hostile or censoring network, and
removes the assumption that being reachable means exposing a static IP.
Compact block filters (0.19) are the groundwork for a real (BOB) light
wallet — they let an SPV client sync privately against our own nodes instead of
leaking its addresses to whatever server it asks.
BIP324 (0.27 → 0.28) is opportunistic P2P encryption; it defeats trivial
traffic analysis and on-path tampering.

Scope

All four are non-consensus and node-local. None of them forks the chain, none
needs coordination with miners, and any of them can ship in a point release
without an activation height. That makes this the cheapest section on the roadmap
to act on, and the one least entangled with anything else.

Suggested order, not a decision

asmap and Tor v3 first: both are small, both are pure resilience, and neither
changes any external interface. Block filters are the larger piece because they
imply an index and a light-client story to go with it.

Roadmap section 5 (forum topic 24, msg 68), filed so it is tracked rather than prose. ### Where we are Confirmed absent from `src/`: - **No Tor control support.** There is no `torcontrol.cpp`. The node cannot create or advertise an onion service, so reachability depends entirely on a clear-net IP and whatever the hosting provider does. - **No asmap.** `src/addrman.cpp` buckets peers by IP range only; there is no ASN-aware bucketing. - **No compact block filters** (BIP157/158) and no BIP324 v2 encrypted transport. ### Why this matters more here than upstream Every one of these is worth more to a chain with few honest peers than to Bitcoin, for the same reason: the smaller the honest peer set, the cheaper it is to surround a node. - **asmap** (Core 0.20) buckets by network topology rather than address, which is the specific defence against an eclipse attack mounted from one provider. On a network where a single operator could plausibly run a large fraction of reachable nodes, this is cheap insurance with an outsized payoff. - **Tor v3** (0.21) gives nodes that survive a hostile or censoring network, and removes the assumption that being reachable means exposing a static IP. - **Compact block filters** (0.19) are the groundwork for a real (BOB) light wallet — they let an SPV client sync privately against our own nodes instead of leaking its addresses to whatever server it asks. - **BIP324** (0.27 → 0.28) is opportunistic P2P encryption; it defeats trivial traffic analysis and on-path tampering. ### Scope All four are **non-consensus and node-local**. None of them forks the chain, none needs coordination with miners, and any of them can ship in a point release without an activation height. That makes this the cheapest section on the roadmap to act on, and the one least entangled with anything else. ### Suggested order, not a decision asmap and Tor v3 first: both are small, both are pure resilience, and neither changes any external interface. Block filters are the larger piece because they imply an index and a light-client story to go with it.

No labels

do-not-open-till-X-Day

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

SubGeniusFinance/dobbscoin-source#42

No description provided.

Rows
Columns