Bridging CosmWasm Panel
summary
Panel focuses on concrete bridges: a claimed $2B of bridge hacks motivates using proven IBC stacks and new tooling rather than bespoke bridges. Details: IBC solidity plus a hardware-backed LCP light client proxy (remote attestation TEE) aim to bring IBC to EVM chains; Composable reports a full CosmWasm reimplementation on Substrate, found bugs in the Go stack and plans IBC support in months; examples include attacks of ~$80M, $200M and ~$600M cited, and a launched Cosmosome Academy for dev training.
AI-written summary · about
chapters (14)
- 0:00CosmWasm bridging panel intro
- 1:06Biggest bridging challenges
- 2:30Composable Finance Polkadot bridge
- 3:56DataChain IBC to EVM chains
- 5:45IBC for cross-chain calls
- 7:07Bridging security risks
- 12:05Contract IBC calls future
- 15:16IBC for traditional finance
- 16:24Secure bridging solutions
- 19:40CosmWasm SDK vs Substrate
- 22:29Expanding CosmWasm risks
- 23:30Multi-chain governance
- 25:15CosmWasm to EVM challenges
- 26:43CosmWasm Japan community
related talks
21mCOSMWASM Powerups!
29mPanel Discussion: National Association of W Lovers: How We Can Create a Thriving Wasm Ecosystem
31mHow We Can Create a Thriving Wasm Ecosystem
07mBeyond The Browser: Wasm in Your Cloud Development Workflow
37mBridging the Architecture Divide: How Hardware Limits Wasm, and How We Can Do Better
33mC# and Wasm Interface Types: Hands Across the C
05mClosing Remarks
05mClosing Remarks