@eversdk/lib-web

Building ever-sdk-js WASM inside docker

To build WASM you need clang v8. Use this workaround if you encounter a problem when building wasm binaries on your platform (MacOSX or Windows).

Pulling build image

docker pull tonlabs/build-tonclient-wasm

Change your current location to ever-sdk-js project. It is important because the next command will use this location to mount the volume with source code inside the docker container with build environment.

cd ever-sdk-js

Run build container in background. First attempt will take a long time.

docker run -v $(pwd):/tonlabs/TON-SDK --name build-tonclient-wasm -dt build-tonclient-wasm tail -f /dev/null

Build WASM

docker exec -ti build-tonclient-wasm "build-tonclient-wasm.sh"

Location of binaries

After successful build process, binaries will be located here

ever-sdk-js/packages/lib-web/index.js
ever-sdk-js/packages/lib-web/eversdk.wasm
Compressed
ever-sdk-js/packages/lib-web/publish/eversdk_1_31_wasm.gz
ever-sdk-js/packages/lib-web/publish/eversdk_1_31_wasm_js.gz

Changelog

[1.37.2] – 2022-08-10

New

• crypto.encryption_box_get_info returns nacl box public key in info.public field.
• Gosh instruction are supported in local VM and executor:
  • execute_diff
  • execute_diff_patch_not_quiet
  • execute_zip
  • execute_unzip
  • execute_diff_zip
  • execute_diff_patch_zip_not_quiet
  • execute_diff_patch_quiet
  • execute_diff_patch_zip_quiet
  • execute_diff_patch_binary_not_quiet
  • execute_diff_patch_binary_zip_not_quiet
  • execute_diff_patch_binary_quiet
  • execute_diff_patch_binary_zip_quiet

Improvement

• create_crypto_box optimisation. When a user creates a crypto box, library encrypts provided secret information using provided password and salt. When library encrypts the secret, it calculates encryption key from password and salt using scrypt function which takes a lot of CPU time (about 1 second). So when a user creates many crypto boxes using the same password and salt, it takes a lot of time (about 12 seconds for 10 crypto boxes). With the optimisations introduced in this version the library stores the pair (password+salt => encryption key) in internal cache for approximately 2 seconds. So when a user creates many crypto boxes at a time using the same password and salt, library uses cached information to skip heavy calculations. As a result now it takes only a second to create 10 crypto boxes.

Fixed

• Some enum types were not properly presented in api.json (some types that use serde(content="value"))