release: dev → main (Red ATM kill · avalanche cleanup · deposit rails · pix/p2p fixes)

.github/workflows/update-content.yml

@@ -13,7 +13,14 @@ jobs:
     update:
         runs-on: ubuntu-latest
         steps:
+            # Base the bump on `dev` (the PR target), NOT the repo default branch.
+            # Branching off a different branch than the base is what let unrelated
+            # code drift leak into the auto-PR (#2226) and made it conflict with dev
+            # once dev's content pointer moved (#2247). Off `dev`, the PR is
+            # content-only by construction and always cleanly mergeable.
             - uses: actions/checkout@v4
+              with:
+                  ref: dev
 
             - name: Init and update submodule
               env:
@@ -34,14 +41,19 @@ jobs:
                     echo "changed=true" >> "$GITHUB_OUTPUT"
                   fi
 
-            - name: Create PR
+            - name: Create PR + auto-merge (content-only)
               if: steps.check.outputs.changed == 'true'
+              # Prefer a PAT (CONTENT_BOT_TOKEN) so the PR triggers CI and auto-merge
+              # can fire on green checks. Falls back to GITHUB_TOKEN — the PR still
+              # opens, but GITHUB_TOKEN-created PRs don't trigger CI, so auto-merge
+              # won't fire until the PAT is configured (no regression vs today).
               env:
-                  GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+                  GH_TOKEN: ${{ secrets.CONTENT_BOT_TOKEN || secrets.GITHUB_TOKEN }}
               run: |
+                  set -euo pipefail
                   BRANCH="auto/update-content-$(date -u +%Y%m%d-%H%M%S)"
                   SUBMODULE_SHA=$(git -C src/content rev-parse HEAD)
-                  PARENT=$(git rev-parse HEAD)
+                  PARENT=$(git rev-parse HEAD)   # dev tip — bump is content-only vs dev
                   BASE_TREE=$(gh api repos/${{ github.repository }}/git/commits/$PARENT --jq '.tree.sha')
                   # Create tree via API with updated submodule pointer
                   TREE=$(gh api repos/${{ github.repository }}/git/trees \
@@ -64,8 +76,18 @@ jobs:
                     --method POST \
                     -f "ref=refs/heads/$BRANCH" \
                     -f "sha=$COMMIT_SHA"
-                  gh pr create \
+                  PR_URL=$(gh pr create \
                     --head "$BRANCH" \
                     --base dev \
                     --title "Update content submodule" \
-                    --body "Auto-generated: updates content submodule to latest peanut-content main."
+                    --body "Auto-generated: bumps the content submodule to latest peanut-content main. Based on dev, so it's content-only and auto-merges once checks pass.")
+                  # Guard: only auto-merge when the PR touches NOTHING but the submodule
+                  # pointer. If anything else slipped in, leave it for a human.
+                  FILES=$(gh pr diff "$PR_URL" --name-only)
+                  if [ "$FILES" = "src/content" ]; then
+                    gh pr merge "$PR_URL" --auto --squash \
+                      || echo "::warning::auto-merge not enabled/permitted — left for manual merge ($PR_URL)"
+                  else
+                    echo "::warning::PR touches more than src/content — left for manual review:"
+                    echo "$FILES"
+                  fi

.verify-content-baseline

@@ -1 +1 @@
-745
+740

e2e/flows/add-money.spec.ts

@@ -81,4 +81,69 @@ test.describe('Add money flow', () => {
         consoleLogs.flush(testInfo, 'add-money-us-bank')
         await context.close()
     })
+
+    // Regression: the NavHeader back button must LEAVE the amount screen on the first tap.
+    // Before fix/addmoney-back-nuqs-replace the flow used nuqs { history: 'push' }, so every
+    // amount keystroke stacked a same-screen history entry and useSafeBack's router.back()
+    // only stepped through stale amounts — the back button looked dead (MP/bank reports).
+    test('add-money/AR/bank — back button leaves the amount screen after typing (verified-ar)', async ({
+        browser,
+    }, testInfo) => {
+        const context = await browser.newContext({ ...devices['Pixel 7'] })
+        await usePersona(context, 'verified-ar')
+
+        const page = await context.newPage()
+        const consoleLogs = collectConsoleLogs(page)
+        await installApiMocks(page)
+
+        await page.goto('/add-money/AR/bank')
+
+        // amount step renders (verified persona skips the "country not found" gate)
+        const amountInput = page.locator('input[inputmode="decimal"]').first()
+        await amountInput.waitFor({ state: 'visible', timeout: 15000 })
+
+        // typing writes ?amount= — with the old { history: 'push' } this stacked back-stack
+        // entries; with the default 'replace' it does not.
+        await amountInput.fill('100')
+        await captureStep(page, testInfo, { name: '01-add-money-ar-bank-amount-typed' })
+
+        // one tap must exit to the country page, not linger on /bank with a stale amount
+        await page.locator('[data-testid="nav-back"]').first().click()
+        await expect(page).toHaveURL(/\/add-money\/AR(?:\?.*)?$/)
+        await captureStep(page, testInfo, { name: '02-add-money-ar-bank-back-left-screen' })
+
+        consoleLogs.flush(testInfo, 'add-money-ar-bank-back')
+        await context.close()
+    })
+
+    // Same regression, the originally-reported flow: Manteca (MP) AR deposit at
+    // /add-money/argentina/manteca. Both add-money amount screens shared the
+    // { history: 'push' } bug; this covers the reported variant directly.
+    test('add-money/argentina/manteca — back button leaves the amount screen after typing (verified-ar)', async ({
+        browser,
+    }, testInfo) => {
+        const context = await browser.newContext({ ...devices['Pixel 7'] })
+        await usePersona(context, 'verified-ar')
+
+        const page = await context.newPage()
+        const consoleLogs = collectConsoleLogs(page)
+        await installApiMocks(page)
+
+        await page.goto('/add-money/argentina/manteca')
+
+        // amount step renders (verified persona; currency rate is mocked)
+        const amountInput = page.locator('input[inputmode="decimal"]').first()
+        await amountInput.waitFor({ state: 'visible', timeout: 15000 })
+
+        await amountInput.fill('100')
+        await captureStep(page, testInfo, { name: '01-add-money-manteca-amount-typed' })
+
+        // one tap must exit to the country page, not linger on /manteca with a stale amount
+        await page.locator('[data-testid="nav-back"]').first().click()
+        await expect(page).toHaveURL(/\/add-money\/argentina(?:\?.*)?$/)
+        await captureStep(page, testInfo, { name: '02-add-money-manteca-back-left-screen' })
+
+        consoleLogs.flush(testInfo, 'add-money-manteca-back')
+        await context.close()
+    })
 })

eslint.config.js

@@ -127,6 +127,16 @@ module.exports = [
                     message:
                         "window.history.length is the pre-useSafeBack idiom (history.length > 1 ? back : push). It misfires on cold-load from external referrers — useSafeBack's pushState counter is more accurate. See PR #1965.",
                 },
+                {
+                    // nuqs `history: 'push'` stacks a browser-history entry on every URL write.
+                    // For per-keystroke params (e.g. `amount`) that poisons the back stack:
+                    // useSafeBack → router.back() then steps through stale same-screen states
+                    // and the back button looks dead (add-money MP/bank reports, June 2026).
+                    selector:
+                        "CallExpression[callee.name=/^useQueryStates?$/] Property[key.name='history'][value.value='push']",
+                    message:
+                        "Don't pass { history: 'push' } to nuqs useQueryState(s) — a history entry per URL write breaks the back button (useSafeBack steps through same-screen states instead of leaving). Use the default 'replace'; the URL stays shareable. If a flow genuinely needs push-per-step, add a scoped file exemption with a comment (see useNativePlugins).",
+                },
             ],
         },
     },

public/llms-full.txt

@@ -1,77 +1,78 @@
 # Peanut — Full Product Description
 
-> Instant global peer-to-peer payments in digital dollars.
+> Spend, send, and cash out digital dollars anywhere — pay local QR codes in Argentina and Brazil with just your passport, spend on a card, and move money across borders without a local bank account or local tax ID.
 
 ## Overview
 
-Peanut is a peer-to-peer payments app that lets users send and receive money globally using digital dollars (USDC stablecoins). It provides a consumer-grade UX on top of blockchain infrastructure — users never need to understand crypto, manage wallets, or handle gas fees.
+Peanut is a self-custody money app built on digital dollars (USDC). Users hold dollars in an account that only they control and spend them like a local — scanning the same QR codes locals use, paying with a card, sending a link, or cashing out to a bank. The experience is consumer-grade: users never manage wallets, seed phrases, or gas fees. Where identity verification is needed it takes a passport and under two minutes — no local ID, bank account, or residency required. Core crypto features require no verification at all.
 
-## Key Features
+## Headline differentiators
 
-### Instant P2P Transfers
-Send digital dollars to any Peanut user instantly. No waiting for bank processing, no wire fees.
+### Pay PIX in Brazil without a CPF
+PIX is Brazil's instant payment network — ~150 million people use it daily. Normally it requires a CPF (Brazilian tax ID) and a Brazilian bank account, which locks out tourists, nomads, and expats. Peanut lets anyone scan a merchant PIX QR and pay in BRL using a passport-verified account funded with digital dollars. The merchant receives BRL in seconds and sees an ordinary PIX payment. The conversion isn't subject to IOF (Brazil's financial-operations tax), saving up to ~3.5% versus cards and bank transfers. Free, 24/7/365, QR scan only.
 
-### Payment Links
-Generate a shareable link containing funds. The recipient clicks the link to claim the money — no account needed. Links work across messaging apps, email, and social media.
+### Pay MercadoPago in Argentina without a DNI
+MercadoPago QR is accepted at 1,000,000+ merchants in Argentina. Locals need a DNI to open an account; Peanut gives access to the payment network without one — pay in pesos with a passport-verified account. Conversion uses the cripto dólar rate (a direct dollar-to-peso market rate that beats the regulated MEP rate cards use), typically several percent to ~11% more pesos per dollar. Free, instant, rate locked at payment.
 
-### Bank Cash-Out
-Connect a local bank account and convert digital dollars to local currency. Supported rails:
-- **Argentina**: Bank transfer, MercadoPago
-- **Brazil**: PIX, bank transfer
-- **Mexico**: SPEI, bank transfer
-- **Colombia**: Bank transfer
-- **Peru**: Bank transfer
-- **Bolivia**: Bank transfer (via Meru)
+### The Peanut Card
+A virtual Visa card that spends the user's digital-dollar balance anywhere Visa is accepted. Free to issue and top up; the only cost is the exchange-rate spread on currency conversion. Available in most countries (the US, Europe, the UK, Latin America, Africa, and more) and requires identity verification. A short list of regions is excluded — the card issuer's restricted-issuance list (China, India, Russia, Turkey, Vietnam, Iran, Israel, and a handful of others).
 
-### Crypto Deposit
-Fund your account by depositing crypto from any exchange (Coinbase, Binance, Kraken, Bybit, OKX, etc.) or external wallet.
+## Core features
 
-### Card Payments
-Physical and virtual debit cards for spending digital dollars at any merchant that accepts card payments.
+### Peanut Links
+Put money in a shareable link or QR; the recipient claims it with no account needed. Works across messengers, email, and social. Unclaimed links are reclaimable; claimed is final.
 
-### QR Payments
-Generate and scan QR codes for in-person payments.
+### Peanut Requests
+A collection link for splitting bills, tips, or donations. Multiple contributors, funds arrive instantly to the balance.
 
-## Security Model
+### Add money (deposit)
+- Crypto: USDC or USDT (and ETH on major EVM networks, auto-converted) from any exchange or wallet on Solana, Arbitrum, Base, Tron, Polygon, or Ethereum. No verification. Gas covered.
+- Bank: SEPA (EUR), ACH (USD), SPEI (MXN), Faster Payments (GBP), and incoming wires (USD/EUR).
+- All deposits free.
 
-- **Self-custodied smart accounts**: User funds sit in ERC-4337 smart accounts, not on Peanut servers
-- **Biometric passkeys**: Account access is secured by the device's Secure Enclave (face/fingerprint). The private key never leaves the device
-- **No server-side keys**: Peanut cannot access, freeze, or move user funds — even under regulatory pressure
-- **Independent recovery**: If Peanut goes offline, users can recover access via any ERC-4337-compatible wallet
+### Cash out (withdraw)
+- Bank: SEPA, ACH, SPEI, Faster Payments — to your own or any third party.
+- Crypto: to any wallet on any supported network; gas covered.
+- Argentina: MercadoPago or a local account.
+- All withdrawals free from Peanut.
 
-## KYC / Compliance
+### Direct bank transfers
+Send from balance straight to any third-party bank account, and receive into the balance, via SEPA/ACH/SPEI/Faster Payments — no link required.
 
-- Core features (send, receive, payment links) work without KYC
-- Bank connections trigger a one-time identity check via Persona (SOC2 Type 2, GDPR, ISO 27001)
-- Peanut only receives a pass/fail result — no documents stored on Peanut servers
+## Security & custody
 
-## Fee Structure
+- Non-custodial smart accounts (ERC-4337) on Arbitrum. User funds never sit on Peanut servers.
+- Biometric passkey auth: the private key is generated from device biometrics and sealed in the device Secure Enclave — never exported, never sent to Peanut.
+- Peanut cannot freeze, seize, or move user funds. If Peanut went offline, users keep full control via any ERC-4337-compatible wallet.
+- Every transaction requires an on-device biometric signature.
 
-- Peer-to-peer transfers: minimal fees
-- Bank cash-out: small conversion spread
-- No monthly subscription or account fees
-- Merchant payments planned with fees lower than Visa/Mastercard
+## Verification & limits
 
-## Target Markets
+- Required only for bank deposits/withdrawals and local QR payments. Passport or national ID from any country (US driver's license accepted for US users). No local ID anywhere.
+- Crypto deposits, crypto withdrawals, and browsing require no verification.
+- Limits: Latin America ~$2,000/month combined (raisable with documents); US/Europe/Mexico/UK no hard limit (very large transactions reviewed); crypto unlimited.
 
-Primary focus on Latin America:
-- Argentina, Brazil, Mexico (largest markets)
-- Colombia, Peru, Bolivia, Chile, Ecuador
+## Fees
 
-Use cases: remittances, freelancer payments, cross-border transfers, savings in stable currency, merchant payments.
+- No per-transaction fee from Peanut. Same-currency moves (USD↔USDC) are free; cross-currency conversions carry a small spread embedded in the displayed, locked rate. Gas is always covered. No monthly or account fees.
 
-## Technical Stack
+## Where Peanut works
 
-- Next.js web application (progressive web app)
-- ERC-4337 smart accounts on Base (Ethereum L2)
-- Biometric passkeys via WebAuthn / Secure Enclave
-- Licensed banking partners for fiat on/off ramps
+- Local QR spending live: Argentina (MercadoPago), Brazil (PIX).
+- Bank rails live: 36 SEPA-zone countries (EUR), US (ACH/wire), Mexico (SPEI), UK (Faster Payments).
+- Crypto deposit/withdraw: global, all non-restricted countries.
+- Card: available in most countries; excludes a short restricted-issuance list (China, India, Russia, Turkey, Vietnam, and others).
+- Roadmap (not live): local payment methods in many more countries (CoDi, Transfiya, Yape, Bizum, MB WAY, UPI, and others). Only Argentina and Brazil have live local spending today.
+
+## Who it's for
+
+Tourists, digital nomads, expats, remote workers, freelancers, and families moving money across borders — especially anyone wanting to spend or save in dollars in Latin America without a local ID or bank account.
 
 ## Company
 
-- Founded by Konrad Kononenko and Hugo Montenegro
-- Based in Europe, serving Latin America
 - Website: https://peanut.me
-- Twitter: https://twitter.com/PeanutProtocol
+- Twitter/X: https://twitter.com/PeanutProtocol
 - GitHub: https://github.com/peanutprotocol
 - LinkedIn: https://www.linkedin.com/company/peanut-trade/
+- Careers: https://peanut.me/careers
+- Support: https://peanut.me/support