multi-vm rollups demonstrate how execution layers are evolving beyond today’s limitations. evm + wasm + svm on one chain yk but the uncomfortable truth is, cross-vm is not composability the zk layer exposes the cracks. let’s see how in a typical multi-vm rollup: evm contracts -> traced in revm wasm contracts -> traced in wasmer svm programs -> traced in rPBF (elf binaries). each runtime executes as a separate state transition what does zk see? >> 3 different traces >> 3 different instruction ...

multi-vm rollups demonstrate how execution layers are evolving beyond today’s limitations. evm + wasm + svm on one chain yk but the uncomfortable truth is, cross-vm is not composability the zk layer exposes the cracks. let’s see how in a typical multi-vm rollup: evm contracts -> traced in revm wasm contracts -> traced in wasmer svm programs -> traced in rPBF (elf binaries). each runtime executes as a separate state transition what does zk see? >> 3 different traces >> 3 different instruction ...

right now, closed ai giants are sitting on valuations that look impossible to compete with >> openai at 500b >> anthropic at 130b >> elon’s xai valued 24b >> perplexity at 18b they look really good tbh but if you zoom out, history says something very different, open source always wins > linux beat microsoft and unix in servers > apache beat netscape and iis in web servers > android beat blackberry and symbian in mobile > kubernetes became the default in infrastructure, beating all proprietary...

right now, closed ai giants are sitting on valuations that look impossible to compete with >> openai at 500b >> anthropic at 130b >> elon’s xai valued 24b >> perplexity at 18b they look really good tbh but if you zoom out, history says something very different, open source always wins > linux beat microsoft and unix in servers > apache beat netscape and iis in web servers > android beat blackberry and symbian in mobile > kubernetes became the default in infrastructure, beating all proprietary...