Stellar protocol meeting discussing three CAPs for native smart contracts: CAP 53 on smart contract data storage with static footprints and deterministic scheduling, CAP 52 on minimal smart contract interactions shifting authorization to contracts, and CAP 47 on contract lifecycle including mutability and versioning questions.
The Stellar protocol team met to discuss three Capability Advancement Proposals (CAPs) for Project Jump Cannon, which introduces native smart contracts to Stellar. CAP 53 formalizes smart contract data storage using key-value pairs with static footprints to enable parallel execution through deterministic scheduling. CAP 52 presents a minimal interaction model that removes built-in authorization, pushing responsibility to contract developers to implement their own signature verification and replay prevention. CAP 47 covers contract lifecycle including ID calculation via hashing and raises open questions about contract mutability and removal. Key tensions emerged around developer burden for authorization logic, versioning of mutable contracts, and data migration between contract versions.