Track and filter which regions each repeater forwards.
Summary
Add the ability to track which transport-scoped regions each repeater forwards, and enable filtering repeaters on the map (or node list) by the regions they allow through. This would help identify which repeaters have region scope configured and which regions they support.
Critical constraint: Only trust hop resolutions that are unambiguous (unique prefix match) to avoid false positives from hash prefix collisions.
Background
I think CoreScope currently tracks transport scope at the packet level. It also tracks the path of repeaters each packet passes through. However, there is no combined relationship that links "repeaters" to "regions they forward."
API Endpoint suggestions
GET /api/nodes?role=repeater&hashRegion=#be,#eu
GET /api/nodes?role=repeater&hasScope=true
GET /api/nodes?role=repeater&hasScope=false
UI Enhancements
On the map page:
- Add a "Region Filter" dropdown to filter visible repeaters by which regions they forward
- Add a "Has Scope" toggle to show/hide repeaters that have never forwarded scoped packets
- Display region badges on repeater markers showing which regions they forward
Use Cases
- Identify unconfigured repeaters: Filter for repeaters with hasScope=false to find nodes that may not have region scope configured yet
- Verify region coverage: See which repeaters forward #eu vs #be to understand regional partitioning
- Troubleshooting: If a region isn't reaching an area, check which repeaters along the path don't forward that region
Track and filter which regions each repeater forwards.
Summary
Add the ability to track which transport-scoped regions each repeater forwards, and enable filtering repeaters on the map (or node list) by the regions they allow through. This would help identify which repeaters have region scope configured and which regions they support.
Critical constraint: Only trust hop resolutions that are unambiguous (unique prefix match) to avoid false positives from hash prefix collisions.
Background
I think CoreScope currently tracks transport scope at the packet level. It also tracks the path of repeaters each packet passes through. However, there is no combined relationship that links "repeaters" to "regions they forward."
API Endpoint suggestions
UI Enhancements
On the map page:
Use Cases