Repository navigation
fix(wasm-sdk): update hardcoded testnet DAPI node addresses #3484
Description
Problem
The default testnet DAPI addresses hardcoded in packages/wasm-sdk/src/sdk.rs are all stale. This causes requests in js-evo-sdk to time out, since the SDK attempts to connect to nodes that no longer exist at those IPs.
The 8 hardcoded IPs were sourced from https://quorums.testnet.networks.dash.org/masternodes but none appear in the current live response:
| Stale IP | Status |
|---|---|
52.12.176.90 |
Not found |
35.82.197.197 |
Not found |
44.240.98.102 |
Not found |
52.34.144.50 |
Not found |
44.239.39.153 |
Not found |
34.214.48.68 |
Not found |
54.149.33.167 |
Not found |
52.24.124.162 |
Not found |
Symptom
SDK calls via js-evo-sdk time out when using the default testnet configuration, since all default addresses resolve to unreachable hosts.
Proposed Fix
Replace the stale IPs in default_testnet_addresses() with current enabled nodes from https://quorums.testnet.networks.dash.org/masternodes (DAPI port 1443). As of 2026-04-13, active nodes are in the 68.67.122.x range.
Activity
fix(wasm-sdk): update stale default testnet DAPI node addresses
thephez commentedon Jul 1, 2026
Fixed on
v4.0-dev. Commit964ab60cff("feat(sdk): source mainnet/testnet bootstrap from dash-network-seeds", backport of #3533 via #3570) removed the hardcodeddefault_testnet_addresses()function frompackages/wasm-sdk/src/sdk.rsentirely. Testnet addresses are now sourced dynamically from thedash-network-seedscrate (WasmSdkBuilder::testnet()→SdkBuilder::new_testnet()→default_address_list_for_network(Network::Testnet)), so there is no longer a stale hardcoded IP list to maintain.A grep for the 8 original stale IPs across
packages/wasm-sdk/now returns nothing. Closing as resolved.