Forge Ecosystem runtime trust model: current server authority, reference-contract limits, and a chain-agnostic migration plan with testable gates.
Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path.
Live application state and user actions are enforced by the Express service and its PostgreSQL database. The Solidity contracts deployed to Sepolia are reference implementations, not the live runtime execution path. Wallet signatures authenticate and authorize requests, but the server applies balances, ownership, burns, staking, governance, treasury, reputation, certificates, bridge records, and validator-state transitions.
The Sepolia deployments provide inspectable reference contracts, public testnet addresses, and intended interfaces. GET /api/contracts publishes that metadata only; it does not execute transactions or prove that live application records match contract state. The current production release explicitly uses Substrate simulation mode, with PostgreSQL authoritative. Live chain submission is not enabled before a domain-level migration.
The current Crucible bridge workflow is a local simulation that records application data only; it does not connect to, move assets across, or settle transactions on external networks.
The migration order is token supply and burns; NFT ownership and ascension; reputation issuance; treasury transfers and governance finalization; then bridge verification. For each migrated domain, a selected chain must become the sole execution authority while PostgreSQL becomes an event-derived query projection with finality, idempotency, reorganization recovery, and reconciliation.
A migrated domain cannot retain a database mutation fallback. If the selected chain cannot execute or finalize an operation, the operation remains pending or fails. Cutover additionally requires independent review, transparent upgrades, scoped pause controls, timelocks, multi-party approval for privileged actions, emergency recovery, and a full projection rebuild from canonical events.