Replace hardcoded guild list with SDK-backed data

[Lakes41]

The guild list screen currently displays example guilds. Replace this with real guild data from the GuildPass SDK or API layer.

Suggested tasks

• Add a query for fetching guilds by wallet address
• Replace the hardcoded guild list
• Show loading, error, and empty states
• Keep example data only for development mocks if needed
• Add tests for the guild list query behaviour

Acceptance criteria

• Guilds are loaded from a real data source
• Hardcoded example guilds are removed from production flow
• Loading, error, and empty states work correctly

[YfengJ]

I would like to apply for this issue if it is still available.

If assigned, I would replace the example guild list with a real SDK/API-backed query scoped to the connected wallet, preserve development-only mocks if the project already uses them, and add clear loading, error, and empty states. I would also add focused coverage around the guild-list query behavior and the production path no longer using hardcoded example guilds.

I will wait for assignment or explicit maintainer confirmation before starting implementation or submitting a PR.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[leocagli]

Hi — Leo Cagliero here (Starmaker program, currently building on Cosmos LATAM and Open Stellar).

I dug into the actual code. app/guilds.tsx renders a hardcoded exampleGuilds array into the FlatList, and src/features/guilds/useGuilds.ts only exposes per-guild queries (useGuild, useGuildConfig, useRoles) — there's no wallet-scoped list query yet. Plan:

1. Add the SDK contract: a guilds.getGuilds({ walletAddress }) method on the @guildpass/sdk module in src/types/guildpass-sdk.d.ts, plus a spy in tests/fixtures/sdk.mock.ts and a GUILDS_LIST_FIXTURE in tests/fixtures/guild.fixtures.ts.
2. Add a list query to useGuilds.ts mirroring the existing factory/offlineFirst pattern:

const useGuildList = (walletAddress: string | null) =>
  useQuery({
    queryKey: ["guilds", walletAddress],
    queryFn: () => guildPassClient.guilds.getGuilds({ walletAddress: walletAddress! }),
    enabled: !!walletAddress,
    networkMode: "offlineFirst",
  });

3. In app/guilds.tsx, drop exampleGuilds, call useGuildList(walletAddress), feed data to the FlatList, and render the existing LoadingState / ErrorState (already imported but unused) on isLoading / isError, keeping EmptyState as ListEmptyComponent.
4. Add useGuilds – getGuilds tests in tests/hooks/useGuilds.test.ts pinning the ["guilds", walletAddress] key and the enabled guard, matching the existing queryFn-boundary style.

Could you assign this to me? I can turn the PR around quickly.

[GBOYEE]

I can take this. I'll replace the hardcoded guild list with SDK-backed data — fetch from the existing guildpass SDK and wire it into the list component. Focused change.

[GBOYEE]

I can do this. Replacing the hardcoded guild list with live SDK-backed data — fetching from guildpass-sdk using the existing config, adding a loading state and error fallback. Will keep the UI consistent.