fix(sifchain): restore explorer REST access through ANODE

[jkbrooks]

Summary

Restore Sifchain's REST-backed explorer views by replacing the unavailable REST endpoint list with https://sifchain.api.m.anode.team (ANODE.TEAM). The public explorer currently displays a disconnected Sifchain dashboard when using Polkachu. Merely adding another endpoint would still allow random selection of a failing provider.

Checks on 2026-09-07: Polkachu REST hostname did not resolve; Allnodes and AutoStake REST latest-block requests returned HTTP 403 from the test environment. ANODE returned live sifchain-1 data and Access-Control-Allow-Origin: *, including with Origin: https://ping.pub.

Validation

• Tested upstream ping-pub/explorer at ca4adc028c796bd076a756544497aa391808f805 with this Sifchain REST configuration in a real browser, without a proxy or application-code changes.
• Dashboard loaded live height, 16 validators, supply and node version. Blocks advanced through heights 30101464–30101469; block list displayed proposers.
• Public account sif1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk70fgk displayed approximately 8,000 ROWAN (the UI rounds the raw balance of 8,000.0000001), account number 17530, sequence 0, no delegations, and a received transaction.
• Staking table loaded 16 active validators (115 total records).
• yarn install --frozen-lockfile, yarn build (type-check and production build), git diff --check, and scripts/check-config-format.sh HEAD~1 HEAD passed.

Scope and limitations

Only api changes. Existing RPC entries are unchanged. ANODE's separate RPC responds to server-side queries but lacked a CORS allow-origin header on /status; this PR does not claim to repair RPC-dependent features, wallet signing/broadcast, or all explorer pages. No wallet was connected and no transaction was signed or broadcast. USD pricing is not validated; the test account page displayed $0 despite a nonzero ROWAN balance.

Existing users may retain a previously selected endpoint in browser settings. After deployment they should select ANODE.TEAM from the chain's REST endpoint dropdown; updating the config alone does not migrate a saved endpoint. This has been tested against current upstream source, not an identified SHA of the live ping.pub deployment.

Checklist

• I changed only the files needed for this update.
• I verified the chain config format.
• I confirmed the changed REST endpoint supports CORS for browser reads.
• Logos unchanged.
• Wallet connection, transfers, delegation, redelegation, unbonding and reward/commission withdrawals: not tested; outside this read-only endpoint recovery.