Skip to content

STE-37: cctp and price-checker corrected on chain, 23 reports re-anchored - #44

Merged
Lin1er merged 1 commit into
mainfrom
ops/37-chain-correction
Sep 16, 2026
Merged

Lin1er merged 1 commit into
mainfrom
ops/37-chain-correction

Conversation

@Lin1er

@Lin1er Lin1er commented Sep 16, 2026

Copy link
Copy Markdown
Owner

Linear: STE-37 · ACC by Axel 2026-09-16 · reviewers @axelmatsama @fable

This PR is the executed half of the change rehearsed in #43: reports/ plus the run record. No code changes.

On-chain correction (Registry v2 / Tokens v2, from main 5a938f5)

26 on chain, 0 held back, 0 skipped, 0 failed.

before after submit_verdict mint_verified
com.fixtures.safe.price-checker 0.9.0 DANGEROUS 10 SAFE 90 3bd64c68… 279a0388…
org.stellar.skills.cross-chain.cctp 2026.8.31 DANGEROUS 10 SAFE 100 3490559a… 9ecc990a…
  • 23 entries were re-anchored by hash only. Verdict and score are unchanged; the bytes moved because of STE-39. docs/audit-evidence.md explains why the old hashes no longer match, and that this is not tampering.
  • 5 entries are DANGEROUS on purpose (4 poisoned, 1 demo rug pull). Each is marked dangerous_intended in the run log.

Verification

  • Read back independently from the chain: 25/25 match verdict, score, and sha256(committed report). Both corrected versions answer is_verified.
  • Every anchored hash is identical to the dry run's.
  • The real run had a model key set, so the identical hashes also show the STE-39 exclusion holding in practice.
  • The cctp and price-checker history from 15–16 September is kept; the execution is added beneath it.

After merge

Redeploy CT 204 so /reports serves these bytes, and run publish-artifacts (cctp and price-checker are now SAFE and sellable). Then check sha256(/reports) == evidence_hash for all 25 through the public URL.

…ports after STE-39

Seed run from main 5a938f5 against Registry v2 / Tokens v2:
26 on chain, 0 held back, 0 skipped, 0 failed.

- price-checker 0.9.0: DANGEROUS 10 -> SAFE 90 (submit_verdict 3bd64c68,
  mint_verified 279a0388)
- cctp 2026.8.31: DANGEROUS 10 -> SAFE 100 (submit_verdict 3490559a,
  mint_verified 9ecc990a)
- 23 hash-only re-anchors, verdicts and scores unchanged
- 5 DANGEROUS on purpose, each marked dangerous_intended in the run log

Read back from the chain afterwards: 25/25 versions match verdict, score
and sha256 of the committed report; both corrected versions is_verified.
Every anchored hash equals the dry run's. The real run had a model key in
its environment; identical hashes show the STE-39 exclusion holding live.

reports/ carries the new bytes; the 15 and 16 September history in
audit-evidence.md is kept and the execution is added beneath it.
@vercel

vercel Bot commented Sep 16, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
sterish Ready Ready Preview Sep 16, 2026 5:25pm UTC

@Lin1er
Lin1er merged commit 65f251d into main Sep 16, 2026
2 checks passed

This branch was successfully deployed

1 active deployment
Preview — 64521766 Deployed Sep 16, 2026 by vercel[bot]
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