Harden cross-chain guild exploration against per-chain RPC failures

[Lakes41]

Difficulty: Advanced
Type: performance

Background
"Cross-Chain Support: Explore guild configurations and role requirements across supported EVM networks" is a checked-in Key Feature, implying the app already queries multiple EVM networks for guild/role data via @guildpass/sdk.

Problem
It's not evident the app handles a single chain's RPC being slow or unavailable gracefully — if guild data is aggregated across chains and one chain's lookup hangs or errors, it likely blocks or breaks the entire guild-exploration view rather than degrading gracefully for just that chain's data.

Expected outcome
When exploring guild configurations across chains, a failure or timeout on any single chain's data source degrades gracefully: that chain's section shows a clear "unavailable" state with a retry option, while data from other chains still renders normally, and the overall screen never blocks indefinitely on one failing chain.

Suggested implementation

• Identify the cross-chain data-fetching logic (likely a set of parallel @guildpass/sdk / TanStack Query calls keyed by chain) and ensure each chain's query is independent (Promise.allSettled-style handling, or separate TanStack Query hooks per chain) rather than one combined promise that fails entirely if any chain errors.
• Add a per-chain timeout so a hanging RPC doesn't block the whole screen indefinitely.
• Add a per-chain "unavailable, tap to retry" UI state distinct from a global loading/error state.
• Add tests simulating one chain succeeding and another failing/timing out, asserting the UI renders partial results correctly.

Acceptance criteria

• A single failing/slow chain never blocks data from other chains from rendering
• Each chain has an independent, retryable failure state
• Timeout behavior is configurable and tested
• Verified with at least a two-chain failure simulation in tests

Likely affected files/directories

• src/ (guild/cross-chain data hooks)
• app/ (guild exploration screens)

[Goodnessoj]

Hi @maintainers, I'll be happy to work on this issue. I'll improve the cross-chain data fetching flow so each network is handled independently, ensuring failures or timeouts on one chain don't affect the others. I'll add configurable timeouts, retryable per-chain error states, and comprehensive tests to verify graceful degradation and reliable cross-chain performance.

[Goodnessoj]

Hi @maintainers, I'll be happy to work on this issue. I'll make the cross-chain data fetching resilient by isolating each network request, adding configurable timeouts and retryable per-chain error states, and ensuring partial results continue to render even when individual RPCs fail. I'll also add test coverage to validate graceful degradation across multiple chain scenarios.

[grantfox-oss]

🦊 GrantFox — @Goodnessoj has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #245)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign | FWC26 campaign!

@Goodnessoj's PR #273 was approved and merged by @Lakes41.

🏆 @Goodnessoj: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (331 total points). Track your full progress on GrantFox.

👏 Great work, @Goodnessoj! Keep contributing to Adamantine-guild.