Stellar Protocol meeting discussing Project Jump Cannon smart contracts. Focus on CAP 50 (transaction signing model), account architecture differences between classic and smart sides, and contract lifecycle parameters. Key debate over single-signer vs multi-sig account models and migration complexity.
The Stellar Protocol team held a public meeting to discuss upcoming changes for Project Jump Cannon, which brings smart contracts to Stellar. The discussion centered on five CAPs (46-50) that modularize the engineering work needed. CAP 50 introduces a new invoke contract transaction type with a simplified account model based on single signatures, similar to Ethereum's message.sender pattern. Key tensions emerged around whether Jump Cannon should use completely separate accounts from classic Stellar or maintain some interoperability. The team debated account migration paths, multi-sig support, and the risk of users accidentally sending funds to incompatible addresses. Additional discussion covered contract lifecycle parameters like code size limits, with disagreement over whether these should be fixed in the protocol or configurable by validators.