Part of #111. Depends on 3/7.
Maintain a preferred ION-peer pool for anchor/content data, layered over a diverse Bitcoin-peer pool for headers/blocks. Critical constraint: preferring ION peers must not shrink header-chain diversity — that's the eclipse trust anchor. Two pools, two purposes; the ION pool informs fast-sync/gossip, the Bitcoin pool guards the PoW header sync (reuse netgroup diversity + min-chain-work). Tests: ION-peer preference does not reduce Bitcoin-peer netgroup diversity below target; ION pool churn doesn't affect header sync.
Part of #111. Depends on 3/7.
Maintain a preferred ION-peer pool for anchor/content data, layered over a diverse Bitcoin-peer pool for headers/blocks. Critical constraint: preferring ION peers must not shrink header-chain diversity — that's the eclipse trust anchor. Two pools, two purposes; the ION pool informs fast-sync/gossip, the Bitcoin pool guards the PoW header sync (reuse netgroup diversity + min-chain-work). Tests: ION-peer preference does not reduce Bitcoin-peer netgroup diversity below target; ION pool churn doesn't affect header sync.