Contract readiness

Contract readiness

Vault, router, strategy, execution, oracle, and risk boundaries are interface-ready; no fake address or ABI is included.

Server-side adapters and caches protect browser clients from provider schema changes and duplicate calls. Shared types define production-grade normalized contracts for every UI surface.

Operational controls

Validate inputs and upstream payloads. Keep secrets server-side and public configuration explicit. Use chain ID 4663 and no localhost runtime dependency.

Limits and risk

A Reown project ID and future deployed contract addresses are external configuration; neither should be fabricated in source.