fix: update Insight API URLs for sweep balance#605
Conversation
The old Insight API endpoints are no longer valid, causing "Couldn't sweep balance" errors when importing private keys. Update all three URLs to their current endpoints. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review infoConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThree Insight API endpoint URLs are updated in the DSInsightManager configuration file. The changes redirect the primary, failover, and testnet API calls to updated endpoint addresses, with modifications to both the domain and API path structures. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
INSIGHT_URLfrominsight.dash.org/insight-api-dash(404) toinsight.dash.org/insight-api(200)INSIGHT_FAILOVER_URLfrominsight.dash.show/api(unreachable) toinsight.dash.org/insight-api(200)TESTNET_INSIGHT_URLfromtestnet-insight.dashevo.org/insight-api-dash(502) toinsight.testnet.networks.dash.org/insight-api(200)Context
Users reported "Couldn't sweep balance - Unexpected response from (null)" when using Import Private Key. All three Insight API endpoints were returning errors (404, connection refused, 502).
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit