# Triton VM becomes WebAssembly compatible

**URL:** <https://talk.neptune.cash/t/triton-vm-becomes-webassembly-compatible/285>\
**Category:** News and Announcements\
**Tags:** triton-vm\
**Created:** [May 11, 2026, 3:25pm UTC](https://talk.neptune.cash/t/triton-vm-becomes-webassembly-compatible/285 "2026-05-11T15:25:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jfs](https://talk.neptune.cash/user_avatar/talk.neptune.cash/jfs/32/6_2.png) [@jfs](https://talk.neptune.cash/u/jfs)\
**Post date:** [May 11, 2026, 3:25pm UTC](https://talk.neptune.cash/t/triton-vm-becomes-webassembly-compatible/285/1 "2026-05-11T15:25:49Z")

</div>

[Triton VM](https://triton-vm.org/), the cryptographic backbone of Neptune Cash, is [now](https://github.com/TritonVM/triton-vm/releases/tag/v3.0.0) compatible with WebAssembly (`wasm32`). This enables modern web-browsers to run Triton VM and paves the way for more powerful web wallets. We’re excited to see what you’ll be building with it!

---

<div class="post-metadata">

**Author:** ![LostInTranslation](https://talk.neptune.cash/letter_avatar_proxy/v4/letter/l/e5b9ba/32.png) [@LostInTranslation](https://talk.neptune.cash/u/LostInTranslation)\
**Post date:** [May 11, 2026, 7:02pm UTC](https://talk.neptune.cash/t/triton-vm-becomes-webassembly-compatible/285/2 "2026-05-11T19:02:57Z")

</div>

Great progress, thanks for sharing!

What parts of Triton VM are currently practical in-browser: program execution, proof generation, proof verification, or all three?

With Triton VM becoming WASM-compatible, what is the intended developer route for writing applications: hand-written TASM, Rust-to-TASM via tasm-lang, or something else? In particular, how hard is it today to write, debug, test, and maintain a non-trivial TASM application?

---

<div class="post-metadata">

**Author:** ![jfs](https://talk.neptune.cash/user_avatar/talk.neptune.cash/jfs/32/6_2.png) [@jfs](https://talk.neptune.cash/u/jfs)\
**Post date:** [May 12, 2026, 7:42am UTC](https://talk.neptune.cash/t/triton-vm-becomes-webassembly-compatible/285/3 "2026-05-12T07:42:23Z")

</div>

> [@LostInTranslation](#):
>
> What parts of Triton VM are currently practical in-browser: program execution, proof generation, proof verification, or all three?

In principle, all three, with the caveat that proof generation of long-running programs requires a _lot_ of RAM and will almost certainly exhaust the memory available to the WebAssembly environment (which, as far as I know, is 4GiB, but I’m not an expert on this front).\[1\] Proof verification and program execution should not be affected by this at all.

> [@LostInTranslation](#):
>
> what is the intended developer route for writing applications: hand-written TASM, Rust-to-TASM via tasm-lang, or something else?

Right now, I’d say the best way is to hand-write TASM and rely on [`tasm-lib`](https://github.com/TritonVM/tasm-lib) as a standard library wherever possible. I’d love to have better tooling, but so far, other things have always been more important. If you need help, please don’t hesitate to reach out. 🙂

* * *

1. Lowering the resource requirements of Triton VM is something we have been and are still working on.