Conversation
Flips enableFullMaintenance to true so all routes redirect to /maintenance while we run the decomplexify ledger cutover migrations on prod DB. Merge this PR immediately before kicking off migrations. To exit maintenance, either revert this PR or wait for the dev->main release PR to merge (note: dev still has enableFullMaintenance: false, so the release merge will conflict on this file — resolve to false).
…-for-release chore: enable full maintenance mode for prod release
Production Release: Peanut Card UI + Decomplexify + Native app + Manteca collateral
The decomplexify cutover migrations + backfill completed successfully at 2026-05-14 19:50 UTC. BE PR #747 + FE PR #1984 merged. Flipping maint off so users come out of the /maintenance redirect. Why this needs a separate PR: PR #1985 (enable maint) was merged into main but never synced to dev. When PR #1984 merged dev -> main, the 3-way merge kept main's true (dev didn't touch the line).
…e-post-release chore: disable maintenance mode post-release
Pre-2025-09-18 users sit at a legacy V0_0_2-derived smart-account
address (migrated in place to V0_0_3 by `createKernelMigrationAccount`,
which forces the historical address). Their actual on-chain wallet
and USDC live at that address.
The grant flow built the session-key kernel via plain
`createKernelAccount({plugins: {sudo: newValidator}})` with no
address override, so the resulting counterfactual address was the
natural V0_0_3-of-new-validator hash — a brand-new, never-funded
address that the rebalancer would later try to deploy and transfer
from. Simulation reverted with `ERC20: transfer amount exceeds
balance` and auto-balance was broken for every pre-migration user.
Forcing `address: kernelClient.account!.address` binds the approval
to the real wallet for both cohorts (post-migration users already
had address == natural counterfactual, so no behavior change there).
…-legacy-address hotfix(card): bind session-key approval to real wallet address
The server enforces a lifetime cap of one grant per user. Without this gate the CTA stays visible after a successful claim and the next tap just bounces off 'already_granted' — confusing for the user and noisy for support.
…ta-after-grant hotfix(carousel): hide bug-bounty CTA once SUPPORT_SURVIVOR badge earned
Post-decomplexify the BE splits a single SEND_LINK into two intents — SEND_LINK (sender's deposit) and SEND_LINK_CLAIM (recipient's claim). The registry was never updated to map the new kind, so claimed-link entries fell through to intentFallback, emitting an "unhandled TRANSACTION_INTENT kind" Sentry warn (PEANUT-UI-QCX, 3 events / 2 users since cutover) and rendering as a degraded "Transaction" card. The existing sendLink strategy already handles the RECIPIENT branch correctly (`direction: 'receive'`, sender identifier as nameForDetails), so the fix is a one-line mapping. Baseline snapshot fixture for send_link_claim-peanut-completed-recipient updated — the old expected values captured the broken fallback output, not the correct receive-side rendering.
…link-claim fix(history): route SEND_LINK_CLAIM through sendLink strategy
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Branch Sync
main is 11 commits ahead of dev.
Commits to sync:
• chore: enable full maintenance mode for prod release migrations
• Merge pull request #1985 from peanutprotocol/chore/enable-maintenance-for-release
• Merge pull request #1984 from peanutprotocol/dev
• chore: disable maintenance mode post-release
• Merge pull request #2036 from peanutprotocol/chore/disable-maintenance-post-release
• fix(card): bind session-key approval to user's real wallet address
• Merge pull request #2037 from peanutprotocol/hotfix/grant-session-key-legacy-address
• hotfix(carousel): hide bug-bounty CTA once SUPPORT_SURVIVOR badge earned
• Merge pull request #2038 from peanutprotocol/hotfix/hide-bug-bounty-cta-after-grant
• fix(history): route SEND_LINK_CLAIM through sendLink strategy
• Merge pull request #2039 from peanutprotocol/hotfix/transformer-send-link-claim
Auto-generated by Chip 🐿️