Large codebases, unnecessary abstractions, and stacks with too many external dependencies make systems harder to reason about and more fragile.
LambdaVM takes the opposite approach: keeping the design simple enough to fully understand and audit.
1/
Instead of relying on clever tricks and heavy optimizations like most zkVMs, LambdaVM takes the opposite approach: prioritizing simplicity and auditability, with a codebase of ~27,000 lines today and a target of ~35,000, following the same philosophy behind @ethrex_client, @class_lambda’s execution client.
1/
new demo of our waas at @alignedlayer: from creating an app to recovering an account, all on passkey-backed smart wallets.
- sign up as a developer and get org + app + publishable key
- create a user wallet: a passkey on the device (touch id) backs a smart-contract wallet, with a server-held guardian as a second key
- send a transaction signed 2-of-2 (passkey + guardian)
- add a new passkey, approved on-chain by an existing one
- recover an account: the server adds a new passkey under a timelock.
.@diego_aligned explains the philosophy behind LambdaVM: our minimalistic RISC-V zkVM with fewer dependencies and a small codebase that is easier to audit, understand, and formally verify.
1/