Deprecations
During pre-launch alpha, contract changes are cutovers. Earlier request and response shapes do not have a compatibility window.
Current Stage
Do not assume a twelve-month overlap, an earlier alpha endpoint remaining available, or a locked
/v1 shape. Keep your integration aligned with the current API and SDK contracts.
XKOVA has not established a production deprecation schedule on this page.
Upgrade Steps
- Review the current versions and release notes.
- Compare your operations with the current API Reference.
- Update SDK packages and any affected request construction or response parsing.
- Exercise success, review, rejection, retry, and timeout paths in sandbox before production.
Deprecation Signals
Deprecation and Sunset are useful when a published retirement schedule
exists. This page does not claim the alpha API emits these headers or guarantees an overlap period.
A future production retirement policy must state affected operations, replacements, and dates.
See Versioning for the distinction between a namespace, a component release, and an immutable on-chain deployment.