Installation

Beo JavaScript and WebAssembly bindings for building zero-knowledge web applications.

Rust compiles easily to WebAssembly but creating the glue code necessary to use compiled WebAssembly binaries from other languages such as JavaScript is a challenging task. wasm-bindgen is a tool that simplifies this process by auto-generating JavaScript bindings to Rust code that has been compiled into WebAssembly.

This crate uses wasm-bindgen to create JavaScript bindings to Beo source code so that it can be used to create zero knowledge proofs directly within web browsers and NodeJS.

Functionality exposed by this crate includes:

  • Beoaccount management objects

  • Beo primitives such as Records, Programs, and Transactions and their associated helper methods

  • A ProgramManager object that contains methods for authoring, deploying, and interacting with Beo programs

More information on these concepts can be found at the Beo Developer Hub.

The wasm-pack tool is used to compile the Rust code in this crate into JavaScript modules which can be imported into other JavaScript projects.

Install Wasm-Packarrow-up-right

curl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh

Build Instructionsarrow-up-right

The general syntax for compiling rust into WebAssembly based JavaScript modules with wasm-packarrow-up-right is as follows:

wasm-pack build --target <target> --out-dir <out-dir> -- --features <crate-features>

Invoking this command will build a JavaScript module in the current directory with the default name pkg (which can be changed as necessary using the --out-dir flag). This folder can then be imported directly as a JavaScript module by other JavaScript modules.

There are 3 possible JavaScript modules that wasm-pack can be used to generate

when run within this crate:

  1. NodeJS module: Used to build NodeJS applications.

  2. Single-Threaded browser module: Used to build browser-based web applications.

  3. Multi-Threaded browser module: Used to build browser-based web applications which use web-worker based multi-threading to achieve significant performance increases.

These 3 modules and how to build them are explained in more detail below.

1. NodeJS Modulearrow-up-right

This module has the features of the NodeJS environment built-in. It is single-threaded and unfortunately cannot yet be used to generate Beo program executions or deployments due to current Beo protocol limitations. It can however still be used to perform Beo account, record, and program management tasks.

Build Instructionsarrow-up-right

2. Single-Threaded browser modulearrow-up-right

This module is very similar to the NodeJS module, however it is built to make use browser-based JavaScript environments and can be used for program execution and deployment.

If used for program execution or deployment, it is suggested to do so on a web-worker as these operations are long-running and will cause a browser window to hang if run in the main thread.

Build Instructionsarrow-up-right

If you are intending to use this for program execution or deployment, it is recommended to build with maximum or close to maximum memory allocation (which is 4 gigabytes for wasm).

3. Multi-Threaded browser modulearrow-up-right

This module is also built for browser-based JavaScript environments, however it is built to make use of Rust-native threading via web-workers (using the approach outlined in the rayon-wasm-bindgen crate). It is the most complex to use, but it will run significantly faster when performing Beo program executions and deployments and should be the choice for performance-critical applications.

To build with threading enabled, it is necessary to use nightly Rust and set certain RUSTFLAGS to enable the necessary threading features. The wasm-pack build command is shown below.

Run tests in NodeJS

Run tests in a browser

Building Web Appsarrow-up-right

Further documentation and tutorials as to how to use the modules built from this crate to build web apps will be built in the future. However - in the meantime, the provable.tools website is a good example of how to use these modules to build a web app. Its source code can be found in the Provable SDK repo in the website folder.

Last updated