SettlementForm hardcodes "USDC" as its initial and reset asset default, ignoring availableLiquidity

[Jagadeeshftw]

📌 Description

SettlementForm (src/components/SettlementForm.tsx) initializes const [asset, setAsset] = useState("USDC"); and its reset() function does setAsset("USDC"); — both hardcode the literal string "USDC" as the asset field's default value. The component already receives an availableLiquidity?: Record<string, number> prop (populated by SettlementsPanel from the real pool list via fetchPools) specifically enumerating the assets this deployment actually supports, but the hardcoded default never consults it. On a deployment whose pools don't include a USDC pool at all, the form's default (and every reset) presents a value that isn't actually one of the supported assets, and submitting without changing it would immediately fail the availableLiquidity liquidity check that validate() already performs for asset codes present in the record.

🧩 Requirements and context

• The asset field's initial value and reset() default should prefer an asset that's actually known to be available (e.g. the first key of availableLiquidity when it's populated), falling back to the current "USDC" literal only when availableLiquidity is absent/empty (e.g. before pools have loaded).
• No change to the field's free-text nature — the user must still be able to type any asset code regardless of the default.
• The existing validation behavior (required field, liquidity check) must be unchanged.

🛠️ Suggested execution

• In src/components/SettlementForm.tsx, derive a defaultAsset (e.g. Object.keys(availableLiquidity ?? {})[0] ?? "USDC") and use it both for the initial useState value and inside reset(), recomputing it if availableLiquidity changes after mount (e.g. via a useEffect that only updates the field when it still holds the previous default, so it doesn't clobber a user's in-progress edit).
• Extend src/components/SettlementForm.test.tsx with a test supplying an availableLiquidity whose keys don't include "USDC" and asserting the field's initial/reset value is one of the actually-available assets instead.

✅ Acceptance criteria

• The asset field's default value reflects an actually-available asset when availableLiquidity is populated.
• The field falls back to "USDC" when availableLiquidity is absent or empty, matching current behavior.
• Test coverage for both cases.

🔒 Security notes

No new attack surface; a client-side default-value correctness fix using data already fetched and displayed elsewhere on the page.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[felladaniel36-hash]

I'd like to claim this issue. I have reviewed the details and can begin working on a fix right away. Please assign it to me if it's still available. Thanks!

[github-actions]

Assigned @felladaniel36-hash to this issue. Please open a PR referencing this issue (e.g. Closes #307) when you're ready.

[grantfox-oss]

🦊 GrantFox — @felladaniel36-hash has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #307)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.