[Open Question] Versioning and immutability over a multi-year asset life

[oa-sarvesh]

Context

Some rails freeze token features at creation — most Solana Token-2022 extensions are immutable after mint (Whitepaper §4.3) — while tokenized bonds and funds live for years and the standard itself will evolve.

The question

How should the standard handle upgrades and behavior negotiation over an asset's multi-year life, given that some environments make token features immutable at creation?

How to contribute

• Propose a spec versioning scheme and how a token declares its spec version in the manifest (see the conformance-profile discussion).
• Analyze upgrade patterns per environment: EVM proxy upgrades, Sui policy replacement, Solana's immutability constraints, Fabric chaincode upgrades — and what the standard can safely assume.
• Address negotiation: how should a v2 counterparty interact with a v1 token?

Reference: Whitepaper §4.3, §5.2.