seicontribx402 trigger
Triggering Codex AI reviewer with sovereign signature and replay attack analysis logic. Slack thread validation expected
Label set: non-app-hash-breaking ✅
Why this label?
This PR only adds an x402 payout manifest (.x402/claim.yaml) and trigger wiring. It does not touch consensus/state-machine logic or anything that would alter the app-hash.
What this PR does
- Introduces
.x402/claim.yamlfor contribution payout tied to PR #2316. - Codex/AppSec review remains validation-only on PR; actual payout dispatch runs post-merge in the protected
payoutsenvironment.
Safety / Secrets
- PR validation uses no sensitive secrets.
- Post-merge payout requires environment secrets (
X402_PRIVATE_KEY,X402_PAYOUT_ENDPOINT) and will run only onmain.
Actions requested
- Approve and run Actions (forked PR gate).
- CODEOWNERS approvals: @sei-will @philipsu522 @stevenlanders.
-
Merge to
mainso the x402 payout can dispatch in the next settlement window.
Quick rationale
This is a payment trigger PR, not a protocol change. Labeling non-app-hash-breaking is correct and keeps the release surface safe.
Label request: non-app-hash-breaking ✅
This PR finalizes the x402 claim:
-
.x402/claim.yamlnow hasdry_run: falsewith updated recipient address. - Codex/AppSec runs on PR; payout dispatches post-merge via protected env.
Please “Approve and run” Actions (fork gate), apply the label, then merge so the x402 payout executes in the next settlement. Thanks!
We truly appreciate your contribution and the time you’ve invested in this PR. Before we can merge it, we’d love your help addressing the remaining feedback or sharing your perspective. If we don’t hear back within 2 day(s), this PR will close automatically — but don’t worry, you can reopen it anytime when you’re ready to continue.