Mainnet and Upgrades

This topic is aimed at readers who need to understand how live protocol upgrades are tracked and consumed safely.

PaperProof has mainnet deployments for its protocol modules and official capability registries. During the early protocol phase, upgrades and deployment changes remain possible. Why manifests matter Package IDs may change during upgrades. Applications should load the active deployment manifest and verify object relationships rather than scattering hardcoded IDs through UI code. Compatibility boundary If only package bindings change and entry signatures remain compatible, a manifest update may be sufficient for many clients. If entry signatures, object layouts, event schemas, or semantic rules change, SDKs and indexers may require new releases. Historical events Indexers should preserve package history so they can explain historical events without mixing them into current canonical state....