Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Why this matters
The repo has scattered design docs (DESIGN.md, LANDING_PAGE_DESIGN.md) and three wiki pages, but no single architecture overview that shows how the Soroban contracts, the backend API, the event indexer, the Postgres database, and the Next.js frontend fit together. New contributors cannot form a mental model of the system.
Acceptance criteria
Files to touch
- architecture.md (new)
- wiki/README.md
- wiki/indexer-sync-flow.md
Out of scope
- Per-service deep dives (separate issues)
- Sequence diagrams for every endpoint
Why this matters
The repo has scattered design docs (DESIGN.md, LANDING_PAGE_DESIGN.md) and three wiki pages, but no single architecture overview that shows how the Soroban contracts, the backend API, the event indexer, the Postgres database, and the Next.js frontend fit together. New contributors cannot form a mental model of the system.
Acceptance criteria
Files to touch
Out of scope