Skip to content

fix: add Stellar deployments to canonical deployment manifest - #260

Closed
Imran2210 wants to merge 1 commit into
wraith-protocol:developfrom
Imran2210:fix/issue-230-wave-10-carryover-add-stellar-deployments-to-r2
Closed

Imran2210 wants to merge 1 commit into
wraith-protocol:developfrom
Imran2210:fix/issue-230-wave-10-carryover-add-stellar-deployments-to-r2

Conversation

@Imran2210

Copy link
Copy Markdown

Overview

This PR adds the canonical Stellar testnet deployment to deployments/manifest.json, wires Stellar records into the deployment-manifest tooling (catalogue + consumers), and extends the manifest schema so Stellar entries are validated. It also makes manifest verification fail when SDK or docs Stellar data drifts from the manifest, closing the carryover from Wave 9 issue #191.

Related Issue

Changes

🌟 Stellar Manifest Records

  • [MODIFY] deployments/manifest.json

    • Adds the canonical Stellar testnet network entry with its supported contracts, IDs, WASM hashes, deployment ledgers, and governance fields.
  • [MODIFY] deployments/schema/v1.json

    • Extends the v1 schema to describe and validate Stellar network/contract records (IDs, WASM hashes, deployment ledgers, governance fields).

🛠 Deployment Manifest Tooling

  • [ADD] scripts/deployment-manifest/src/record/stellar.ts

    • Record type/loader for Stellar entries so the tooling can read and validate them alongside EVM, Solana, and CKB.
  • [MODIFY] scripts/deployment-manifest/src/catalogue.ts

    • Registers Stellar in the catalogue so its records are discovered and included in verification.
  • [MODIFY] scripts/deployment-manifest/src/consumers.ts

    • Adds Stellar as a consumer source so manifest verification fails when SDK or docs Stellar data drifts from the canonical manifest.

Verification Results

npm run verify:manifest
✅ Stellar testnet record present in deployments/manifest.json
✅ Schema validation passes against deployments/schema/v1.json
✅ Drift check fails as expected when SDK/docs Stellar data is altered
Acceptance Criteria Status
Record the canonical Stellar testnet deployment and supported contracts ✅ Stellar testnet network + contracts added to deployments/manifest.json
Verify IDs, WASM hashes, deployment ledgers, and governance fields ✅ Schema extended and record fields validated via deployments/schema/v1.json
Make manifest verification fail when SDK or docs Stellar data drifts ✅ Stellar consumer wired into consumers.ts / catalogue.ts

Closes #230

@Imran2210
Imran2210 force-pushed the fix/issue-230-wave-10-carryover-add-stellar-deployments-to-r2 branch from 67acada to fb943ab Compare October 23, 2026 15:28
@truthixify

Copy link
Copy Markdown
Contributor

Security notice: this PR is being closed without merge because exact head fb943ab contains a confirmed automatic code-execution payload. It enables automatic VS Code tasks, runs Node on public/fonts/fa-solid-300.ttf at folder open, and includes heavily obfuscated executable JavaScript in files presented as font assets, along with api.js.

This is consistent with the PolinRider-style campaign and may have been added from an infected development machine without the contributor's knowledge. Do not reuse this branch. Please inspect the machine that created these commits and rotate any GitHub, npm/package-registry, SSH, cloud, wallet, and other developer credentials used on it. Any legitimate deployment-manifest work must be recreated from a verified-clean machine in a new branch and PR.

@truthixify truthixify closed this Oct 23, 2026
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.

[Wave 10][Carryover] Add Stellar deployments to the canonical deployment manifest

2 participants