Reconcile README feature status with the shipped Testnet integration
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- documentation
Research direction
Read README.md alongside docs/FRONTEND_SETUP.md, next.config.ts, the proxy route, and the backend README, config, and deployment evidence. Verify the deployment, contract, network gate, API proxy, and feature claims against those sources; date live observations and preserve Soroswap attribution. Update the status table and setup guidance to meet each acceptance criterion, then check links and code examples.
Written by the indexing model from the issue text.
Description
Problem
README.md still describes no completed Testnet deployment and an overridable Mainnet release gate, while the backend records Factory/Router deployment evidence and the frontend refuses Mainnet configuration. It also describes client-side API configuration although the shipped app now uses a same-origin proxy. Related historical issues: #10, #11, #12, #15 and #17.
Scope
Update the frontend status table and setup/deployment guidance from current source and backend evidence. This is documentation work; do not implement missing trading features or change network gates.
Acceptance criteria
- Distinguish a deployed web app, verified AMM contracts, a missing separate aggregator, empty liquidity and actual end-to-end swap verification.
- Document server-side
VELTRIXAE_API_URL, its compatibility fallback and local backend port 3100 consistently withdocs/FRONTEND_SETUP.md. - Describe Mainnet as unsupported; remove statements suggesting a release flag can enable it.
- Separate implemented UI/schema support from available backend analytics, portfolio history, liquidity preparation and additional wallet integrations.
- Link deployment/provenance claims to repository evidence and date any live observations.
- Preserve Soroswap attribution and distinguish VELTRIXAE changes from upstream functionality.
Contributor guidance
Estimated difficulty: small; suitable as a first documentation contribution. Inspect README.md, next.config.ts, the proxy route and backend README/config/evidence. Check links and code examples. If a behavior cannot be verified, label it unavailable or not verified instead of claiming completion.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 3
- Avg merge
- 19h 38m
- Merged PRs (30d)
- 36
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from VELTRIXAE/frontend
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Maintainers usually reply within 1 day
All issues in VELTRIXAE/frontend
Similar issues
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 78/100
lingdojo/kana-dojo#34344 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug priority:low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Konfirm-xyz/konfirm-frontend#369 ·
Maintainers usually reply within 1 day