It is possible to publish transactions to the Tangle that contain only messages, with no value. This introduces many possibilities for data integrity and communication, but comes with the caveat that message-only signatures are not checked. What we introduce is a method of symmetric-key encrypted, signed data that takes advantage of merkle-tree winternitz signatures for extended public key usability, that can be found trivially by those who know to look for it.

This is wrapper library for the WASM/ASM.js output of the IOTA Bindings repository. For a more in depth look at how Masked Authenticated Messaging works please check out the Overview

This is a work in progress. The library is usable, however it is still evolving and may have some breaking changes in the future. These will most likely be minor, in addition to extending functionality.

After downloading the mam.client.js file for your project, importing the library will provide access to the functions described below.

For a simple user experience you are advised to call the init() function to enable to tracking of state in your channels.When calling init() you should also pass in your initialised IOTA library. This will provide access to some extra functionality including attaching, fetching and subscribing.

Note: When using with React-Native use the rn-nodify package to shim the library to ensure it works correctly To import the library, use either require("mam.client.js") or import * as Mam from 'mam.client.js'

Please see example/index.js for a working example

This initialises the state. This will return a state object that tracks the progress of your stream and streams you are following

Mam.init(provider, seed, security)

1. provider: String Network provider.
2. seed: String Tryte-encoded seed. Null value generates a random seed
3. security: Integer Security of the keys used. Null value defaults to 2

1. Object - Initialised state object to be used in future actions

This takes the state object and changes the default stream mode from public to the specified mode and sidekey. There are only three possible modes: public, private, & restricted. If you fail to pass one of these modes it will default to public. This will return a state object that tracks the progress of your stream and streams you are following

Mam.changeMode(state, mode, sidekey)

1. state: Object Initialised IOTA library with a provider set.
2. mode: String Intended channel mode. Can be only: public, private or restricted
3. sideKey: String Tryte-encoded encryption key, any length. Required for restricted mode

1. Object - Initialised state object to be used in future actions

Creates a MAM message payload from a state object, tryte-encoded message and an optional side key. Returns an updated state and the payload for sending.

Mam.create(state, message)

1. state: Object Initialised IOTA library with a provider set.
2. message: String Tryte-encoded payload to be encrypted.

1. state: Object Updated state object to be used with future actions/
2. payload: String Tryte-encoded payload.
3. root: String Tryte-encoded root of the payload.
4. address: String Tryte-encoded address used as an location to attach the payload.

Enables a user to decode a payload

Mam.decode(payload, sideKey, root)

1. payload: Object Initialised IOTA library with a provider set.
2. sideKey: String Tryte-encoded encryption key. Null value falls back to default key
3. root: String Tryte-encoded string used as the address to attach the payload.

1. state: Object Updated state object to be used with future actions.
2. payload: String Tryte-encoded payload.
3. root: String Tryte-encoded root used as an address to attach the payload.

These actions require an initialised IOTA library with a provider to be passed in when calling Mam.init(iota).

Attaches a payload to the tangle

await Mam.attach(payload, address)

1. payload: String Tryte-encoded payload to be attached to the tangle.
2. address: String Tryte-encoded string returned from the Mam.create() function.

1. Object Transaction objects that have been attached to the network.

Fetches the stream sequentially from a known root and optional sidekey. This call can be used in two ways: Without a callback will cause the function to read the entire stream before returning. With a callback the application will return data through the callback and finally the nextroot when finished.

See examples: fetchSync.js & fetchAsync.js usage examples.

await Mam.fetch(root, mode, sidekey, callback)

1. root: String Tryte-encoded string used as the entry point to a stream. NOT the address!
2. mode: String Stream mode. Can be only: public, private or restricted Null value falls back to public
3. sideKey: String Tryte-encoded encryption key. Null value falls back to default key
4. callback: Function Tryte-encoded encryption key. Null value will cause the function to push payload into the messages array.

1. nextRoot: String Tryte-encoded string pointing to the next root.
2. messages: Array Array of Tryte-encoded messages from the stream. NOTE: This is only returned when the call is not using a callback

Compiled binaries are included in the repository. Compiling the Rust bindings can require some complex environmental setup to get to work, so if you are unfamiliar just stick to the compiled files.

The below command will build a file called mam.client.js in the lib/ directory.

// Install dependencies
yarn

// Build
yarn build

The below command will build mam.web.js in the lib/ directory, that can be included in the browser.

 // Install dependencies
 yarn

 // Build
 yarn web

You can use the browser version like this

  <script src="mam.web.js"></script>
  <script type="text/javascript">
      var Mam = require('mam.web.js');
  </script>

1. Install Rust

curl https://sh.rustup.rs -sSf | sh

See https://www.rustup.rs/

2. Update to nightly

rustup default nightly
rustup update

3. Install Emscripten

cd
# Get the emsdk repo
git clone https://github.com/juj/emsdk.git

# Enter that directory
cd emsdk

# Fetch the latest registry of available tools.
./emsdk update

# Download and install the latest SDK tools.
./emsdk install latest

# Make the "latest" SDK "active" for the current user. (writes ~/.emscripten file)
./emsdk activate latest

# Activate PATH and other environment variables in the current terminal
source ./emsdk_env.sh

See https://kripken.github.io/emscripten-site/docs/getting_started/downloads.html

4. Clone latest iota-bindings Repo, then compile content of the emscripten to IOTA.js

git clone [email protected]:iotaledger/iota-bindings.git
cd iota-bindings/emscripten
rustup target install asmjs-unknown-emscripten
cargo build --release --target asmjs-unknown-emscripten

5. Navigate to iota-bindings/emscripten/target/asmjs-unknown-emscripten/release and look for IOTA.js

6. Add module.exports = Module; at the very end of IOTA.js file