Skip to content

chore(deploy): record staging cashapp retirement, pin lane 42 - #316

Merged
Kartik4152 merged 2 commits into
mainfrom
kartik/record-cashapp-staging-retirement
Sep 2, 2026
Merged

chore(deploy): record staging cashapp retirement, pin lane 42#316
Kartik4152 merged 2 commits into
mainfrom
kartik/record-cashapp-staging-retirement

Conversation

@Kartik4152

Copy link
Copy Markdown
Contributor

Summary

Base staging executed lane 42's Cash App risk-window retirement on 2026-09-02 via the deployer EOA (tx 0x5cde17a0c59ba4b606b19b9d09b468af06cd283d256984160e9627aaff4dc451, run from merged main dfe1060). Verified on-chain afterwards: cashapp 0 / paypal 1209600 / venmo 1209600 on both networks (Base was zeroed by the Safe at nonce 80 on 2026-08-28). This PR records that state repo-side — the standard post-execution recording flip.

Changes

  • deployments/dispute-stack-evidence.json: staging cashapp row → "0".
  • packages/contracts/scripts/extractors/disputeStack.ts: remove fix: keep Cash App outside dispute protection #311's staging LIVE_DISPUTABLE_PAYMENT_METHODS override ("until its governed policy update is executed" — it now has); configuredRiskWindows derives from DISPUTABLE_PAYMENT_METHODS again.
  • scripts/active-dispute-stack.spec.cjs: drop the matching staging cashapp override row.
  • deployments/immutableDeploymentLanes.ts: pin 42_retire_dispute_risk_windows.ts (deployedSourceSha dfe1060, sha256 5aeddc6c…ad014; not retired — the lane stays mounted and its skip reads live windows, so tagged runs are no-ops while every retired window is zero).
  • deployments/parameters.ts comment + README/AGENTS/CLAUDE: both networks executed; lane 42 immutable and pinned.

Test Plan

  • yarn pkg:build + yarn pkg:test (manifest now says cashapp 0 on both networks)
  • node --test scripts/active-dispute-stack.spec.cjs — 13/13
  • yarn test:retire-dispute-risk-windows 8/8, yarn test:method-scoped-vault-deployment 8/8
  • yarn typecheck:dispute-deployment

Next

After this merges, @zkp2p/contracts-v2@0.4.1-rc.10 (#312 already merged) can be published via the trusted workflow with the fully-flipped manifest.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Mk9kaLm8nkbBN1TPbdNU1b

Base staging executed lane 42's deployer write on 2026-09-02
(tx 0x5cde17a0...dc451, source dfe1060), so Cash App reads a zero risk
window on both live networks. Flip the staging evidence and spec rows,
drop the extractor's staging LIVE_DISPUTABLE_PAYMENT_METHODS override
from #311 (configuredRiskWindows derives from DISPUTABLE_PAYMENT_METHODS
again), pin lane 42 as immutable-but-mounted, and update the docs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mk9kaLm8nkbBN1TPbdNU1b

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 67233c983f

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

},
// Executed on Base staging 2026-09-02 from dfe1060 (tx 0x5cde17a0…4dc451); the Base window was zeroed by the
// Safe at nonce 80 on 2026-08-28 before this lane's first run. Lane stays mounted; its skip reads live windows.
"42_retire_dispute_risk_windows.ts": {

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Update the exact immutable-lane manifest fixture

Whenever the release-surface checks run yarn test:dispute-lifecycle-deployment, the exact assert.deepEqual(IMMUTABLE_DEPLOYMENT_LANES, ...) assertion in scripts/test-opt-in-dispute-lifecycle-deployment.cjs:410-511 fails because its expected object still ends at lane 40 and does not contain this new lane 42 entry. Add lane 42 to that fixture so the required deployment-lane check and Release readiness workflow can pass.

AGENTS.md reference: AGENTS.md:L237-L238

Useful? React with 👍 / 👎.

@Kartik4152
Kartik4152 merged commit 265ea33 into main Sep 2, 2026
4 checks passed
Kartik4152 added a commit that referenced this pull request Sep 2, 2026
* chore(deploy): record staging cashapp retirement, pin lane 42

Base staging executed lane 42's deployer write on 2026-09-02
(tx 0x5cde17a0...dc451, source dfe1060), so Cash App reads a zero risk
window on both live networks. Flip the staging evidence and spec rows,
drop the extractor's staging LIVE_DISPUTABLE_PAYMENT_METHODS override
from #311 (configuredRiskWindows derives from DISPUTABLE_PAYMENT_METHODS
again), pin lane 42 as immutable-but-mounted, and update the docs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mk9kaLm8nkbBN1TPbdNU1b

* test(deploy): add lane 42 to the immutable-manifest pin fixture

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mk9kaLm8nkbBN1TPbdNU1b

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant