[platform] New member gateways now default to the gent02 gateway node #308

Open
opened 2026-06-19 20:01:12 +00:00 by mik-tf · 1 comment
Owner

For the testing organization, the deployer now mints new member gateways on the gent02 gateway node instead of gent01. gent01's gateway seeding kept failing for some members, and gent03 is not present on this network, so gent02 is the working default. This is a configuration value on the running admin instance. Recording it here so the change is tracked outside of session notes. Revisit if gent01 seeding is fixed or another network is used.

For the testing organization, the deployer now mints new member gateways on the gent02 gateway node instead of gent01. gent01's gateway seeding kept failing for some members, and gent03 is not present on this network, so gent02 is the working default. This is a configuration value on the running admin instance. Recording it here so the change is tracked outside of session notes. Revisit if gent01 seeding is fixed or another network is used.
Author
Owner

Update

  • We foresee and want to use gent03 on mainnet and not gent02 on qa
# Update - We foresee and want to use gent03 on mainnet and not gent02 on qa
Sign in to join this conversation.
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
lhumina_code/home_lhumina#308
No description provided.