P0: Config endpoints return empty arrays #27

New Issue

shoko · 2026-04-09T07:11:53+02:00

shoko commented

2026-04-09 07:11:53 +02:00

Problem

The /api/config/chains and /api/config/tokens endpoints return empty arrays, making it impossible for frontend to populate dropdowns.

Current Implementation (config.py:6-13)

@router.get("/chains")
def get_chains():
    return {"chains": []}  # Always empty

@router.get("/tokens")
def get_tokens():
    return {"tokens": []}  # Always empty

Solution

`/chains` Endpoint

Return ["bsc"] only - BNB Chain is the only supported chain for Phase 1.

`/tokens` Endpoint

Query AVE Cloud API directly to get available tokens.

Acceptance Criteria

/api/config/chains returns {"chains": ["bsc"]}
/api/config/tokens returns list of tokens from AVE API
Frontend can populate chain/token dropdowns

## Problem The `/api/config/chains` and `/api/config/tokens` endpoints return empty arrays, making it impossible for frontend to populate dropdowns. ### Current Implementation (config.py:6-13) ```python @router.get("/chains") def get_chains(): return {"chains": []} # Always empty @router.get("/tokens") def get_tokens(): return {"tokens": []} # Always empty ``` ## Solution ### `/chains` Endpoint Return `["bsc"]` only - BNB Chain is the only supported chain for Phase 1. ### `/tokens` Endpoint Query AVE Cloud API directly to get available tokens. ## Acceptance Criteria - [ ] `/api/config/chains` returns `{"chains": ["bsc"]}` - [ ] `/api/config/tokens` returns list of tokens from AVE API - [ ] Frontend can populate chain/token dropdowns

shoko added the frontend label 2026-04-09 07:11:53 +02:00

shoko referenced a pull request that will close this issue

2026-04-09 08:18:40 +02:00

fix: populate config endpoints with chain and token data #33

shoko closed this issue

2026-04-09 08:23:44 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: shoko/randebu#27

P0: Config endpoints return empty arrays #27