Stellar Development Foundation hosted an open protocol meeting to discuss Jump Cannon smart contract implementation. The team presented CAP 46-49, four core advancement proposals covering WebAssembly runtime, smart contract lifecycle, and two competing approaches (CAP 48 vs CAP 49) for classic asset interoperability with smart contracts.
The Stellar Development Foundation held its first open protocol meeting on Discord to discuss Project Jump Cannon, which brings smart contracts to Stellar. The meeting covered four core advancement proposals (CAPs 46-49) necessary for smart contract implementation. CAP 46 establishes WebAssembly runtime vocabulary, CAP 47 defines smart contract lifecycle management, and CAPs 48 and 49 present competing approaches to classic asset interoperability. CAP 48 offers frictionless integration where classic assets work directly in smart contracts, while CAP 49 introduces explicit wrap/unwrap mechanics for cleaner ERC-20 compatibility. The team discussed authorization models, asset versioning, contract mutability, and downstream system implications like Horizon data access layers. Key tensions emerged around user experience, scalability, exchange compatibility, and whether to push complexity to downstream systems or encode it on-chain.