[chin0312]

Summary

Activates the verified X Layer Testnet bindings for NVDAx, SPYx, and AAPLx in the canonical deployment manifest and backend capability registry.

Architecture

• One shared ValtideValidationRegistry: 0x1A53C85C66EA212693d36bF842574643C4d9B635
• One shared ValtideRiskGuard: 0x8e17a4eB93074ea74d05D9bc316d85AD3B540CE7
• One DemoCollateralVault per asset/reference pair
• Existing NVDAx vault remains 0x4beC6Bc1DF651f36758216cA02db62b5603349ce
• No core Solidity source or bytecode changes

Verified Testnet deployment (chainId 1952)

Asset	DemoVault	Deployment tx	Policy tx
SPYx	0x260884c5a8977E47aabB6FF9EDE62B2Ce4E027bb	0xb9c53fbf1d364b77739e6d29557d12b4b10964783eebe90f3fc0cac2bb9170cd	0xf92a17044adaf42c1b39efd34c8fb0cf90a97eec1ca6830d16f5973c9026aae3
AAPLx	0xb15eB7cB90C203A84E520b70Dde1d2553D3bac6e	0xff4e771deda4f98eab1b4ae92e75a0a91ee003ea82f3f5af043cd5caf53d2483	0x2f35b92edafb1261d18841854562f54d6fe5b73fe367a913fb1ddb816286ac66

The four receipts have status 1. The verified non-secret receipt records blocks and UTC timestamps. Both new vaults point to the shared RiskGuard and use the common 900-second policy: SUPPORTED→ALLOW, INCONCLUSIVE→REQUIRE_REVIEW, CHALLENGED→RESTRICT_NEW_RISK, STALE→REQUIRE_REVIEW. The existing NVDA binding and publisher authorization were also read-only verified.

Scope and safety

• Canonical manifest now contains exactly NVDAx, SPYx, and AAPLx under assets, with asset-specific IDs, model versions, and explicit v2 publication compatibility.
• SPYx/AAPLx backend onchain capability is enabled; QQQx stays research-only and offchain.
• Multi-asset resolution, asset-scoped API routes, manual-publish-disabled behavior, and worker/publisher routing are covered by tests.
• No Railway settings or deployment changed in this PR. PUBLISH_ENABLED=false and automatic publication has not been enabled by this change.
• Frontend PR fix: align validation console with Evidence State v2 #32 is untouched.

Validation

• Backend: 356 passed
• Foundry: 26 passed
• Frontend regression: 41 passed; production build passed
• Ruff: passed
• Python compileall: passed
• Deterministic manifest rebuild and read-only chain verification: passed

Next step

After owner review and merge, deploy latest main to the existing Railway service, verify the three read-only /api/onchain/{asset} bindings and runtime state, then enable scheduler-owned publication only after those checks pass. Manual POST /api/publish/{asset} remains disabled.

[vercel]

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

Project	Deployment	Actions	Updated
valtide	Ready	Preview	Oct 6, 2026 6:56pm UTC