Skip to content

latency-collector: contributor-provided ripeatlas probes #973

@nikw9944

Description

@nikw9944

The internet latency collector only uses Atlas anchor probes because they have better availability characteristics than probes provided by other Atlas users. RIPE Atlas has anchor probe coverage for all of our target mainnet-beta sites except for Salt Lake City and Buenos Aires. We could use other users' probes in these cities that do not have anchor probes, but there's no guarantee of those probes' availability.

Let's add a feature to internet-latency-collector that allows us to configure a list of DoubleZero contributor-provided probe IDs. If this feature proves popular it will make sense to store probe IDs on-chain, but at this stage let's do something simple (load IDs from command line flag or config file).

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions