feat: enhance Starknet integration and UI components

[onahprosper]

• Added support for internal API origin configuration in the aggregator API to handle deployments with separate SPA and API origins.
• Updated the networks list in mocks to reflect explicit ranking based on aggregator volume, improving user experience.
• Introduced a new context for managing transaction form swap state, allowing global UI updates without prop drilling.
• Enhanced dropdown components to support a disabled state, preventing user interaction when necessary.
• Implemented validation for Starknet-specific on-ramp functionality, including UI adjustments to indicate unsupported features.
• Refactored transaction handling to ensure correct wallet address usage for Starknet, improving API interaction and error handling.
• Improved error handling in transaction fetching to gracefully manage 404 responses, enhancing user feedback.

Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change. For the benefit of the community, please do not assume prior context.

Provide details that support your chosen implementation, including: breaking changes, alternatives considered, changes to the API, contracts etc.

References

Include any links supporting this change such as a:

• GitHub Issue/PR number addressed or fixed e.g closes feat: make recipient name editable when unresolved from psp #407
• StackOverflow post
• Support forum thread
• Related pull requests/issues from other repos

If there are no references, simply delete this section.

Testing

Describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this project has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.

Also include details of the environment this PR was developed in (language/platform/browser version).

• This change adds test coverage for new/changed/fixed functionality

Checklist

• I have added documentation and tests for new/changed functionality in this PR
• All active GitHub checks for tests, formatting, and security are passing
• The correct base branch is being used, if not main

By submitting a PR, I agree to Paycrest's Contributor Code of Conduct and Contribution Guide.

Summary by CodeRabbit

• New Features

  • Dropdowns can be disabled programmatically; receive-side controls reflect locked state.
  • Starknet on‑ramp shows "Coming soon", disables related inputs, and prevents preview/submit.
  • Blockchain networks reordered for improved discovery.

• Bug Fixes

  • API requests correctly reach the proper origin when app and API are split.
  • Recipient/fetch flows are more resilient to partial backend failures.
  • Starknet wallet handling aligned to avoid auth mismatches.

• Documentation

  • Added optional env guidance for internal API origin.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ead93204-ad31-4662-9f95-dccf1c5b6573

📥 Commits

Reviewing files that changed from the base of the PR and between 9709b4c and c390be4.

📒 Files selected for processing (1)

• app/context/TransactionsContext.tsx

---

📝 Walkthrough

Walkthrough

Adds an optional example env var for internal API origin and a URL helper for resolving Next.js /api/* calls; introduces a home swap-mode React context and provider, propagates a disabled prop through dropdowns, adjusts Starknet on‑ramp UI/flow, improves API error logging/robustness, and updates utilities and mocks.

Changes

Cohort / File(s)	Summary
Configuration & API routing ./.env.example, app/api/aggregator.ts	Added commented NEXT_PUBLIC_INTERNAL_API_ORIGIN example and implemented noblocksInternalApiUrl(); replaced relative /api/** axios calls with the helper to resolve absolute API origins; added explicit axios generics where applicable.
Recipients route & transactions error handling app/api/v1/recipients/route.ts, app/context/TransactionsContext.tsx	Recipients endpoint now runs two Supabase queries and logs per-table errors (includes code/message) — only throws if both fail; transaction fetch catch block distinguishes Axios errors and logs response status/message.
Context & providers app/context/HomeTransactionFormModeContext.tsx, app/context/index.ts, app/providers.tsx	Added HomeTransactionFormModeProvider and useHomeTransactionFormMode hook, memoized context value, wired provider into top-level ContextProviders, and re-exported from context barrel.
Dropdowns & disabled prop app/components/FlexibleDropdown.tsx, app/components/FormDropdown.tsx, app/components/blog/home-client.tsx, app/components/MobileDropdown.tsx	Introduced optional disabled prop and added disabled to render-prop signature; blocking toggle when disabled, auto-closing open menus, forwarding disabled state to buttons and styling.
Starknet on‑ramp & swap flow app/hooks/useSwapButton.ts, app/pages/TransactionForm.tsx, app/components/MainPageContent.tsx	Added isStarknetOnramp flag to swap hook (disables actions, sets “Coming soon”), integrated form-level guards, short-circuited rate fetch when on‑ramp active, and synchronized global swap-mode via new context.
Transaction creation alignment app/pages/TransactionPreview.tsx	Use embedded EVM wallet address (walletAddressForTransactionApi) for transaction API calls and refresh to ensure request body/auth identity match JWT-derived wallet.
Utilities & mocks app/utils.ts, app/mocks.ts	Broadened classNames() typing to accept falsy values, added isStarknetChain() predicate, and reordered networks export to reflect product ranking; added explanatory comments.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• feat(tokens): implement TokensContext for centralized token managemen… #177 — edits app/api/aggregator.ts; overlaps with the new noblocksInternalApiUrl and aggregator request changes.
• feat(networks): Scroll and Celo support, token API alignment, and SEO updates #446 — modifies app/mocks.ts networks ordering; likely overlaps with the networks reordering here.
• feat: make recipient name editable when unresolved from psp #407 — touches app/pages/TransactionPreview.tsx and transaction payloads; related to the wallet/address handling changes in this PR.

Suggested labels

enhancement

Suggested reviewers

• chibie
• 5ran6

Poem

🐰 A tiny rabbit hops the wire,
Routes endpoints true, avoids the mire,
Dropdowns rest when told to stay,
Starknet waits, “Coming soon” to say,
Wallets matched — a quiet, clever choir.

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The PR scope does not address the linked issue #407 requirements (RecipientAlert component, isRecipientNameEditable state, Mixpanel analytics, InformationSquareIcon). The changes focus on Starknet integration and UI components unrelated to recipient name editing functionality.	Either implement the recipient name editing features from issue #407 or remove the linked issue if this PR addresses different objectives.
Docstring Coverage	⚠️ Warning	Docstring coverage is 65.38% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects major changes including Starknet integration enhancements and UI component improvements like dropdown disabled state support.
Description check	✅ Passed	The PR description covers main objectives (internal API origin, networks ranking, swap state context, disabled dropdowns, Starknet on-ramp, wallet address handling, error handling) but lacks detailed Testing section and leaves checklist items unchecked.
Out of Scope Changes check	✅ Passed	All changes align with stated PR objectives: internal API origin support, networks reordering, swap state context, dropdown disabled state, Starknet on-ramp validation, wallet address refactoring, and error handling improvements. No unrelated changes detected.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-starknet-onramp-coming-soon

---

_{Review rate limit: 3/5 reviews remaining, refill in 16 minutes and 24 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 4

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

app/mocks.ts (1)

13-34: ⚠️ Potential issue | 🟠 Major

Don't fall back to an empty Starknet RPC URL.

If NEXT_PUBLIC_STARKNET_RPC_URL is missing, both rpcUrls entries become [""], which is not a valid endpoint and will fail later at runtime. Please fail fast here or omit Starknet from the chain list until a real URL is configured.

Suggested fix

+const starknetRpcUrl = process.env.NEXT_PUBLIC_STARKNET_RPC_URL;
+
+if (!starknetRpcUrl) {
+  throw new Error("NEXT_PUBLIC_STARKNET_RPC_URL is required for Starknet support");
+}
+
 export const starknetMainnet = {
   id: BigInt(toHex('SN_MAIN')).toString(), // Starknet Mainnet chain ID (SN_MAIN encoded)
   name: "Starknet",
@@
     default: {
-      http: [process.env.NEXT_PUBLIC_STARKNET_RPC_URL || ""],
+      http: [starknetRpcUrl],
     },
     public: {
-      http: [process.env.NEXT_PUBLIC_STARKNET_RPC_URL || ""],
+      http: [starknetRpcUrl],
     },
   },

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@app/mocks.ts` around lines 13 - 34, starknetMainnet currently falls back to
an empty string for rpcUrls when NEXT_PUBLIC_STARKNET_RPC_URL is unset,
producing invalid endpoints; change the behavior in the starknetMainnet object
so it does not include rpcUrls (or remove/omit the whole starknetMainnet export)
unless process.env.NEXT_PUBLIC_STARKNET_RPC_URL is a non-empty string, or
alternatively throw an explicit error at module load if
NEXT_PUBLIC_STARKNET_RPC_URL is missing; update the rpcUrls field handling
(referencing starknetMainnet and the NEXT_PUBLIC_STARKNET_RPC_URL env var) to
only set valid http array entries when the env var is present.

🧹 Nitpick comments (1)

app/mocks.ts (1)

75-128: Make the ordering contract explicit.

This array now drives defaults in NetworksContext and the visual order in NetworkSelectionModal, so its position semantics are part of the app contract. Consider exporting a named defaultNetwork/rank field or a dedicated ordering helper to avoid silent behavior changes when the ranking shifts later.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@app/mocks.ts` around lines 75 - 128, The networks array currently encodes
ordering semantics used by NetworksContext and NetworkSelectionModal; make that
contract explicit by adding an exported selector or metadata: either export a
named defaultNetwork (e.g., export const defaultNetwork = networks[0]) and/or
add a stable rank property on each network object (e.g., rank: 1,2,3...) or
create and export a small ordering helper (e.g., export function
getOrderedNetworks() that returns networks sorted by rank) so callers use the
explicit identifier (defaultNetwork, networks[i].rank, or getOrderedNetworks)
instead of relying on array position; update NetworksContext and
NetworkSelectionModal to consume the new symbol instead of indexing the raw
networks array.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/context/TransactionsContext.tsx`:
- Around line 284-296: The 404 branch clears local React state (via
setTransactions, setTotal, setError) but doesn't update the cached response,
allowing stale data to reappear; after handling the 404 you must also update or
invalidate the transactions cache entry for the same wallet/page/limit key
(e.g., call the project’s cache update API such as mutate,
queryClient.setQueryData or invalidateQueries for the transactions query key) so
the cached value becomes an empty list/total 0 (or is invalidated) and won't
resurrect stale rows.

In `@app/hooks/useSwapButton.ts`:
- Around line 17-18: The isStarknetOnramp flag currently only affects the label
but must short-circuit the swap state: inside useSwapButton (before the
migration/normal swap state-machine logic) check isStarknetOnramp and
immediately set isEnabled = false and buttonAction to the “Coming soon” /
blocked action (or a noop) so no later branch can enable the Swap; ensure this
guard executes before any migration/state computation (the code paths that
compute isEnabled and buttonAction) so the Starknet on‑ramp flow is always
locked down.

In `@app/pages/TransactionForm.tsx`:
- Around line 565-577: The Starknet on-ramp flag is only changing buttonText via
useSwapButton but not preventing submission; update the guard so unsupported
Starknet on-ramp orders cannot proceed by either adding isStarknetOnramp to the
isEnabled calculation inside useSwapButton (so isEnabled becomes false when
isStarknetOnramp is true) and/or short-circuiting buttonAction to a no-op when
isStarknetOnramp is true, and additionally add a defensive check in
MainPageContent.tsx handleFormSubmit to return early if isStarknetOnramp is true
(use the same prop/flag) to ensure preview/payment cannot be reached.

In `@app/pages/TransactionPreview.tsx`:
- Around line 232-240: The persisted wallet address must come from Privy's
embedded wallet (the same source the middleware sets in x-wallet-address) rather
than mixing in activeWallet; update walletAddressForTransactionApi to use
embeddedWallet?.address for all networks (i.e., remove the fallback to
activeWallet?.address) and add a fail-fast path that throws or returns an
explicit error when embeddedWallet?.address is missing; apply the same change to
the other occurrence of walletAddressForTransactionApi/related logic referenced
in the review so both places consistently resolve the address from
embeddedWallet.

---

Outside diff comments:
In `@app/mocks.ts`:
- Around line 13-34: starknetMainnet currently falls back to an empty string for
rpcUrls when NEXT_PUBLIC_STARKNET_RPC_URL is unset, producing invalid endpoints;
change the behavior in the starknetMainnet object so it does not include rpcUrls
(or remove/omit the whole starknetMainnet export) unless
process.env.NEXT_PUBLIC_STARKNET_RPC_URL is a non-empty string, or alternatively
throw an explicit error at module load if NEXT_PUBLIC_STARKNET_RPC_URL is
missing; update the rpcUrls field handling (referencing starknetMainnet and the
NEXT_PUBLIC_STARKNET_RPC_URL env var) to only set valid http array entries when
the env var is present.

---

Nitpick comments:
In `@app/mocks.ts`:
- Around line 75-128: The networks array currently encodes ordering semantics
used by NetworksContext and NetworkSelectionModal; make that contract explicit
by adding an exported selector or metadata: either export a named defaultNetwork
(e.g., export const defaultNetwork = networks[0]) and/or add a stable rank
property on each network object (e.g., rank: 1,2,3...) or create and export a
small ordering helper (e.g., export function getOrderedNetworks() that returns
networks sorted by rank) so callers use the explicit identifier (defaultNetwork,
networks[i].rank, or getOrderedNetworks) instead of relying on array position;
update NetworksContext and NetworkSelectionModal to consume the new symbol
instead of indexing the raw networks array.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 6b3de0d0-260a-4a5f-a8d5-49136b91c925

📥 Commits

Reviewing files that changed from the base of the PR and between 1d7a4c3 and da25486.

📒 Files selected for processing (17)

• .env.example
• app/api/aggregator.ts
• app/api/v1/recipients/route.ts
• app/components/FlexibleDropdown.tsx
• app/components/FormDropdown.tsx
• app/components/MainPageContent.tsx
• app/components/MobileDropdown.tsx
• app/components/blog/home-client.tsx
• app/context/HomeTransactionFormModeContext.tsx
• app/context/TransactionsContext.tsx
• app/context/index.ts
• app/hooks/useSwapButton.ts
• app/mocks.ts
• app/pages/TransactionForm.tsx
• app/pages/TransactionPreview.tsx
• app/providers.tsx
• app/utils.ts

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@app/context/TransactionsContext.tsx`:
- Around line 284-305: The code in TransactionsContext.tsx currently treats
axios 404 responses as an empty transaction history and writes an empty entry
into the cache (the block around axios.isAxiosError(error) &&
error.response?.status === 404), which hides routing/origin/config problems;
remove that 404 special-case handling so 404s fall through to the error branch
instead — stop calling setTransactions([]), setTotal(0), setError(null), and
setCache(...) for status 404, and instead call setError(error) and console.error
as in the else path (ensure the axios.isAxiosError check is still used to detect
HTTP errors but do not swallow 404).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 339c01e6-871e-4ab4-a3a4-d1171b874647

📥 Commits

Reviewing files that changed from the base of the PR and between da25486 and 9709b4c.

📒 Files selected for processing (4)

• app/components/MainPageContent.tsx
• app/context/TransactionsContext.tsx
• app/hooks/useSwapButton.ts
• app/pages/TransactionPreview.tsx

🚧 Files skipped from review as they are similar to previous changes (3)

• app/pages/TransactionPreview.tsx
• app/hooks/useSwapButton.ts
• app/components/MainPageContent.tsx