[Docs] FAQ.tsx claims chains we don't support (Ethereum/Arbitrum/Optimism/Polygon/Base)

[ogazboiz]

Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0

Labels: good first issue, frontend, docs

The landing-page FAQ tells visitors we support a bunch of EVM chains we don't.

FlowFi is a Soroban/Stellar project. But frontend/src/components/FAQ.tsx lines 10-11 answers "Which chains do you support?" with "We are currently live on Ethereum Mainnet, Arbitrum, and Optimism. Polygon and Base support is coming in Q3 2026." That contradicts the README, the contracts directory, and the wallet integrations.

What the fix has to hold to

• No EVM chain names in the answer
• If there's no multi-chain roadmap, say so plainly

Done when

• Answer rewritten to Stellar (testnet/mainnet via Soroban), or whatever the team wants to say
• Lint + CI green

Where to start
Just lines 10-11 of frontend/src/components/FAQ.tsx. Don't restructure the FAQ or touch other questions. One-line copy fix.

[silentgeckoaudit3801]

I can take this if maintainers are still accepting work here. I prepared the one-line FAQ copy fix on a no-PR branch while the issue is unassigned:

Compare: main...silentgeckoaudit3801:docs-faq-stellar-chain-support

Scope:

• changes only rontend/src/components/FAQ.tsx
• removes the unsupported Ethereum / Arbitrum / Optimism / Polygon / Base claim
• rewrites the answer to Stellar + Soroban testnet/mainnet support and says there is no announced EVM multi-chain roadmap
• leaves the other FAQ questions untouched

Static validation via GitHub API: branch is 1 commit ahead / 0 behind, only that FAQ file changed, no EVM chain names remain in the answer, and no local dependency install or command execution was used. I have not opened a PR yet so I do not bypass assignment/coordination.

[codeX-james]

@codeX-james has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello! I’d love to take on this issue. I’ve reviewed the requirements and have a clear path forward for the implementation. I estimate I can have a PR ready within about 3 hours of being assigned. Could you please assign this to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @codeX-james to this issue.

[drips-wave]

Congratulations, @codeX-james! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @codeX-james: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @codeX-james as part of the Stellar Wave Program's 7th Wave 🥳

😎 @codeX-james: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.