Stellar protocol developers discussed Jump Cannon smart contract upgrades, including CAPs 46-53. Key decisions: removing the Box type, renaming u63 to positive i64, merging contract code and data ledger entries, and defining the footprint type. Asset interoperability remains unresolved with debate over wrapping, representation, and classic asset integration.
The Stellar Development Foundation held an open protocol meeting focused on Jump Cannon, the upcoming smart contract protocol upgrade. Developers reviewed multiple CAPs (46-53) and made several technical decisions: removing the Box object type to simplify the XDR structure, reverting the u63 type back to u63 (rejecting positive i64 and non-neg alternatives), and merging separate contract code and data ledger entries into a single representation. A major discussion centered on mutable contracts, with concerns raised about undefined semantics for code mutation during execution. The team deferred mutability decisions, making code immutable for now. The footprint type was approved as a read-write set for contract execution. Asset interoperability sparked extensive debate with no consensus, covering wrapping vs non-wrapping, classic asset representation in smart contracts, and exchange/service provider compatibility concerns.