🐛 Governance Action Page Fails When Index Is Missing in URL and wallet not connected

[bosko-m]

Area

Voting Pillar

Domain

gov.tools

Which wallet were you using?

No response

Context

When accessing governance actions directly without providing an index (e.g., #0), the app behaves inconsistently depending on wallet state and environment. This can result in console errors and blank pages, or failed backend calls.

• Issue is likely due to lack of default index handling in frontend routing and backend API calls.
• Some browsers treat missing index as part of the URL path instead of a parameter if not properly encoded.

Steps to reproduce

1. With wallet not connected:
   • Open a governance action link without an index at the end (e.g., .../governance_actions/<txhash> instead of .../governance_actions/<txhash>#0).
   • Observe that the page fails to load properly, shows a blank screen, and console logs errors.
2. With wallet connected:
   • Open a governance action link without index.
   • Sometimes the backend call for that governance action fails, producing the same broken state.

Example URL: https://gov.tools/connected/governance_actions/90cf51975f9c19c291bac3e57364a89507e64daa0a2d35e356f87e6684821556

Actual behavior

• Wallet disconnected:
  Blank page is shown, console shows errors, index is not assumed to default to 0.
• Wallet connected:
  Backend call fails intermittently when index is missing.
• Behavior is inconsistent across browsers; some browsers may misinterpret missing #0 in the URL if not properly encoded.

Expected behavior

• When accessing a governance action without specifying index, the system should:
  • Default to index 0.
  • Load governance action details consistently across connected and disconnected states.
• No console errors or backend failures should occur.
• Shared links without index should resolve correctly.