diff --git a/components/Savings/NewSavings/SavingsScreenNew.tsx b/components/Savings/NewSavings/SavingsScreenNew.tsx
index ef48c4bc..7298e2c6 100644
--- a/components/Savings/NewSavings/SavingsScreenNew.tsx
+++ b/components/Savings/NewSavings/SavingsScreenNew.tsx
@@ -94,7 +94,7 @@ export default function SavingsScreenNew() {
-
+
diff --git a/components/Savings/NewSavings/VaultFaqCard.tsx b/components/Savings/NewSavings/VaultFaqCard.tsx
index 1400397b..31f7b7c9 100644
--- a/components/Savings/NewSavings/VaultFaqCard.tsx
+++ b/components/Savings/NewSavings/VaultFaqCard.tsx
@@ -8,10 +8,22 @@ import {
AccordionTrigger,
} from '@/components/ui/accordion';
import { Text } from '@/components/ui/text';
-import faqs from '@/constants/faqs';
+import { getVaultFaqs } from '@/constants/vault-faqs';
+import { VaultType } from '@/lib/types';
+
+type VaultFaqCardProps = {
+ vaultType: VaultType;
+};
+
+/**
+ * Figma 24805:8738 / 24805:8760 — compact FAQ card for the vault detail screen.
+ *
+ * The questions are vault-specific: the ETH and FUSE vaults answer for soETH
+ * and soFUSE rather than reusing the soUSD list.
+ */
+const VaultFaqCard = ({ vaultType }: VaultFaqCardProps) => {
+ const faqs = getVaultFaqs(vaultType);
-/** Figma 24805:8738 / 24805:8760 — compact FAQ card for the vault detail screen. */
-const VaultFaqCard = () => {
return (
@@ -21,7 +33,14 @@ const VaultFaqCard = () => {
{faqs.map((faq, index) => (
-
+ // Scoped to the vault so switching vaults on the same mounted
+ // screen collapses the rows instead of leaving an index expanded
+ // onto a different question.
+
+import VAULT_FAQS, { getVaultFaqs } from '@/constants/vault-faqs';
+import { VaultType } from '@/lib/types';
+
+/**
+ * The vault detail screen used to render one soUSD list on all three vaults, so
+ * someone on the ETH vault was told what soUSD is. These lock the split.
+ */
+describe('vault FAQs', () => {
+ it('answers for every vault we actually have', () => {
+ for (const vaultType of Object.values(VaultType)) {
+ const faqs = getVaultFaqs(vaultType);
+
+ expect(faqs.length).toBeGreaterThan(0);
+ for (const faq of faqs) {
+ expect(faq.question.trim()).not.toBe('');
+ expect(faq.answer.trim()).not.toBe('');
+ }
+ }
+ });
+
+ it('names its own vault token in the opening question', () => {
+ expect(VAULT_FAQS[VaultType.USDC][0].question).toContain('soUSD');
+ expect(VAULT_FAQS[VaultType.ETH][0].question).toContain('soETH');
+ expect(VAULT_FAQS[VaultType.FUSE][0].question).toContain('soFUSE');
+ });
+
+ it('never explains soUSD on the ETH or FUSE vault', () => {
+ for (const vaultType of [VaultType.ETH, VaultType.FUSE]) {
+ const copy = getVaultFaqs(vaultType)
+ .map(faq => `${faq.question} ${faq.answer}`)
+ .join(' ');
+
+ expect(copy).not.toMatch(/what is soUSD/i);
+ expect(copy).not.toMatch(/1 soUSD per 1 USDC/i);
+ }
+ });
+
+ it('ties the FUSE vault to Skip the Line, which is what that deposit unlocks', () => {
+ const copy = getVaultFaqs(VaultType.FUSE)
+ .map(faq => faq.answer)
+ .join(' ');
+
+ expect(copy).toContain('Skip the Line');
+ expect(copy).toContain('50,000 FUSE');
+ expect(copy).toContain('400,000');
+ });
+
+ it('falls back to the USDC vault for a type that is not a vault', () => {
+ expect(getVaultFaqs('doge' as VaultType)).toBe(VAULT_FAQS[VaultType.USDC]);
+ });
+});
diff --git a/constants/vault-faqs.ts b/constants/vault-faqs.ts
new file mode 100644
index 00000000..191f14d5
--- /dev/null
+++ b/constants/vault-faqs.ts
@@ -0,0 +1,96 @@
+import { Faq, VaultType } from '@/lib/types';
+
+/**
+ * Per-vault FAQ copy for the vault detail screen.
+ *
+ * The savings screen used to show one soUSD-centric list on all three vaults,
+ * so someone opening the ETH or FUSE vault was told what soUSD is and why they
+ * didn't receive 1 soUSD per USDC. Each vault answers for itself here instead.
+ *
+ * Copy is product-owned (Monday 12943830277) and reproduced verbatim — edit it
+ * there, not here.
+ */
+const VAULT_FAQS: Record = {
+ [VaultType.USDC]: [
+ {
+ question: 'What is soUSD?',
+ answer:
+ "Your yield-bearing dollar. Deposit USDC or USDT and receive soUSD. Your soUSD count doesn't change, each soUSD becomes worth more over time.",
+ },
+ {
+ question: 'Where does the yield come from?',
+ answer:
+ 'Your deposit is deployed across diversified, blue-chip DeFi lending and fixed-yield strategies (Morpho, Pendle and others), managed under vault-level risk controls. Allocation is adjusted over time to balance yield and safety.',
+ },
+ {
+ question: 'Can I spend from this vault?',
+ answer:
+ 'Yes. soUSD backs your Solid card balance. Your dollars keep earning until the moment you spend them, and you can spend against soUSD without withdrawing it.',
+ },
+ {
+ question: 'Is soUSD a stablecoin?',
+ answer:
+ "It's a yield-bearing representation of USD. Its value in dollars rises with accrued yield rather than staying fixed at 1.00.",
+ },
+ {
+ question: 'How fast can I withdraw?',
+ answer:
+ 'Withdrawals are processed on demand. Most complete within minutes, with no exit fee or waiting period.',
+ },
+ ],
+ [VaultType.ETH]: [
+ {
+ question: 'What is soETH?',
+ answer:
+ 'Your yield-bearing ETH. Deposit ETH and receive soETH, which grows in ETH terms as staking rewards and strategy yield accrue.',
+ },
+ {
+ question: 'Where does the yield come from?',
+ answer:
+ 'Your ETH is put to work through liquid staking and a focused set of conservative ETH strategies. The goal is to beat standard liquid staking returns without adding meaningful risk.',
+ },
+ {
+ question: 'Do I still have exposure to the ETH price?',
+ answer:
+ 'Yes. soETH tracks ETH. If ETH goes up or down, so does the dollar value of your position. The vault adds yield on top of that exposure.',
+ },
+ {
+ question: 'Can I use soETH with the card?',
+ answer:
+ 'Not directly today. Card spending is powered by your USD balance. You can withdraw ETH and swap to USDC in-app whenever you want to spend it.',
+ },
+ ],
+ [VaultType.FUSE]: [
+ {
+ question: 'What is soFUSE?',
+ answer:
+ 'Your yield-bearing FUSE. Deposit FUSE and receive soFUSE. Your soFUSE grows in value as staking rewards compound, so you never need to claim anything.',
+ },
+ {
+ question: 'Where does the yield come from?',
+ answer:
+ 'Your FUSE is staked to secure the Fuse Network, the chain Solid runs on, earning native staking rewards. Solid adds a boost on top from the Fuse treasury, which is why this vault pays more than staking FUSE anywhere else.',
+ },
+ {
+ question: 'Do I still have exposure to the FUSE price?',
+ answer:
+ 'Yes. soFUSE tracks FUSE. The vault adds yield in FUSE terms, the dollar value still moves with the market.',
+ },
+ {
+ question: 'Is this the same as Skip the Line staking?',
+ answer:
+ 'Yes. Your FUSE Vault deposit is what counts for Skip the Line. Hold 50,000 FUSE in the vault to unlock Prime, or 400,000 to unlock Ultra. You earn yield and unlock your tier with the same deposit.',
+ },
+ {
+ question: 'Why hold FUSE in the vault rather than just holding FUSE?',
+ answer:
+ 'Idle FUSE earns nothing. The same FUSE in the vault earns network rewards plus the treasury boost, keeps earning Solid Rewards points, and counts toward Prime or Ultra through Skip the Line. One deposit, three benefits.',
+ },
+ ],
+};
+
+/** FAQ list for a vault, falling back to the USDC vault for an unknown type. */
+export const getVaultFaqs = (vaultType: VaultType): Faq[] =>
+ VAULT_FAQS[vaultType] ?? VAULT_FAQS[VaultType.USDC];
+
+export default VAULT_FAQS;