Community Calls
Compiling Go to WebAssembly: Embedding NATS in wash
The April 16, 2025 wasmCloud community call is a study in Go WebAssembly done in anger. Brooks Townsend demos compiling the Go-based NATS server to a WebAssembly module and embedding it directly in the wash CLI — no separate binary, no Docker, no process forked off — so that wash dev can stand up a full local wasmCloud platform from a single static binary. Before that, maintainer Masoud (ossfellow) walks through his provenance-and-attestation RFC — SLSA levels, SBOMs, and the cost of bolting supply-chain security onto a complex monorepo CI pipeline — and the call closes with a heads-up that Q2 roadmap planning lands next week.
WebAssembly Kubernetes Workload Identity with SPIFFE & SPIRE
The April 9, 2025 wasmCloud community call centers on WebAssembly Kubernetes workload identity. Fresh off back-to-back wasm.io Barcelona and KubeCon London, Joonas Bergius demos the work he and Colin presented on stage: using SPIFFE and SPIRE to give WebAssembly workloads a verifiable identity, then exchanging short-lived SPIFFE JWTs for temporary AWS credentials — no static secrets in the mix. Bailey Hayes and Liam Randall co-host, walking through how this solves first- and third-party multi-tenancy and cross-cloud deployment, before a community Q&A on WASI version compatibility, Helm/NATS deployments, and the capability boundaries of the WebAssembly component model.
WasmPay Demo: The Wasm Component Model for Cross-Language Payments
The April 2, 2025 wasmCloud community call streams live from the wasmCloud booth in the CNCF Project Pavilion at KubeCon + CloudNativeCon Europe 2025 in London. Brooks walks through the team's conference schedule — including talks on wasmCloud's road to the standards, SPIFFE workload identity, and WebAssembly on Kubernetes — and then demos WasmPay, a cross-language, cross-country payment processing platform. WasmPay shows the Wasm component model at work: banks supply transaction validators written in any language that compiles to WebAssembly, and wasmCloud composes each untrusted validator with a "platform harness" component that handles HTTP, NATS messaging, and the validation contract.
wasmCloud Q1 Roadmap, WASI Preview 3 & the Wasm Component Model
The March 26, 2025 wasmCloud community call is the last of the quarter, so Brooks Townsend walks the Q1 roadmap end to end — what shipped, what's in flight, and what slipped — with the Wasm component model and WASI Preview 3 dominating where maintainer time went. Open-source benchmarking Helm charts and a combined wash CLI/lib landed; a cron-job provider, logging-buffer error counts, and bundling are in progress; and a big chunk of the team's effort went upstream into Wasmtime and JCO to push WASI P3 across the line. The call closes with a look ahead to WASM I/O Barcelona and KubeCon + CloudNativeCon EU in London.
WebAssembly Composition & the Wasm Component Model in wasmCloud
The March 19, 2025 wasmCloud community call centers on the Wasm component model — both at build time and over the lattice. Brooks Townsend demos how to compose WebAssembly components with the wac plug tool, then shows new wash build functionality (in a PR) that performs the same composition automatically using WAC's Rust library, so developers never have to install or learn the CLI. The call then turns to a community proposal from LUK3ARK: "virtual components," a way for components to route invocations over wRPC to services that live outside the lattice — and the security questions that raises.