We don't use WASM, we use an entirely new computational model called PLAN and a new Lispy/Haskelly functional language called Sire. The core of our system is an SSI (solid state Interpreter), Kinode's is not. (We'll have a blog post with a frendlier definition of the SSI soon, but for now there is this whitepaper that introduced this concept to the world: https://media.urbit.org/whitepaper.pdf . Disclaimer though that we are not building on Urbit, it's just that the SSI is a general concept.)

We've got some explanation of PLAN here: https://vaporware.gitbook.io/vaporware/overview/overview#persistence-plan

Kinode's identity/networking layer requires blockhain integration. Our networking and identity are optional, freely-chosen by the user, and compatible with standard, blockchain-less cryptographic keypairs very much like Nostr. In fact, you'll be able to use your Nostr keys as identy in our system!