pezkuwichain d0b3947254 Add OnFinality as a second RPC node for Aleph Zero, enable failover ...

Aleph Zero was configured with a single node (wss://ws.azero.dev,
the Foundation's own endpoint) and no nodeSelectionStrategy, so any
outage there fails the chain outright with no fallback - confirmed
live via direct curl (502 Bad Gateway from the endpoint's own nginx,
backend unreachable), which is what was timing out
BalancesIntegrationTest.testBalancesLoading/testFeeLoading[Aleph Zero]
in wallet-android CI. Aleph Zero itself is healthy and active (live
Foundation site/explorer, active aleph-node development, OnFinality/
Dwellir both offer public RPC for it) - this was a config gap, not a
dead chain. Added OnFinality's public endpoint as a second node with
roundRobin selection, matching the pattern already used for our own
Pezkuwi chain's 2-node setup.

2026-07-14 09:12:26 -07:00

..

android

Add OnFinality as a second RPC node for Aleph Zero, enable failover

2026-07-14 09:12:26 -07:00

preConfigured

chore: sync from nova-base (ee89e832)

2026-07-09 22:22:37 -07:00

chains_dev.json

fix: point Bitcoin icon URLs at pending/post-fix-release, not master

2026-07-12 20:25:25 -07:00

chains.json

fix: point Bitcoin icon URLs at pending/post-fix-release, not master

2026-07-12 20:25:25 -07:00

evm_assets.json

Update chains.json with correct Pezkuwi chain IDs and order

2026-01-24 15:41:28 +03:00