Skip to content

feat(transport): add ECAD relay servers to NORTH_AMERICA_WEST#956

Closed
jevonearth wants to merge 1 commit intoairgap-it:masterfrom
ECADInfra:feat/add-ecad-relay-servers
Closed

feat(transport): add ECAD relay servers to NORTH_AMERICA_WEST#956
jevonearth wants to merge 1 commit intoairgap-it:masterfrom
ECADInfra:feat/add-ecad-relay-servers

Conversation

@jevonearth
Copy link
Contributor

Summary

  • Adds four ECAD Infrastructure relay servers (beacon-{1-4}.ecadinfra.com) to the NORTH_AMERICA_WEST region
  • Improves relay coverage in western North America (currently only one node in the region)
  • ECAD servers are running Synapse v1.147.1 with the standard crypto_auth_provider and beacon_info_module

Changes

Single file change to packages/beacon-transport-matrix/src/communication-client/P2PCommunicationClient.ts, adding four servers to the existing REGIONS_AND_SERVERS constant.

Test plan

  • Verify ECAD servers respond to /_synapse/client/beacon/info with valid region, known_servers, and timestamp
  • Verify federation between ECAD and existing AirGap relay servers
  • Test dApp-wallet pairing with SDK client selecting an ECAD server

Add four ECAD Infrastructure relay servers (beacon-{1-4}.ecadinfra.com)
to the NORTH_AMERICA_WEST region, improving relay coverage in western
North America.
@jevonearth
Copy link
Contributor Author

Blocked by airgap-it/beacon-node#6 — ECAD servers need the updated beacon_info_module config with our hostnames in known_servers before SDK clients start probing them.

Federation testing between ECAD and AirGap relay servers is also required before this ships.

@jevonearth jevonearth closed this Mar 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant