Use MAMv2 to register/resolve TangleID DID

[ender503]

Due to IOTA announce MAMv2, we decide no longer to use MAMv1 for identity registration.

The MAMv2 currently only support C language, we'll need Tangle Accelerator to provide the MAMv2 API for new identity registration.

[ender503]

After a few discussions with @wusyong, we will not design the API for TangleID in Tangle Accelerator.

We'll wait for the entangled: JavaScript bindings, and use it for new identity registration.

[jserv]

The descriptions should be revised and reflected to latest engineering decisions.

[DougAnderson444]

So is this TangleID deprecated then? Or can it be used?

[jserv]

There is no JavaScript binding to MAMv2 yet, and we can still exploit Tangle-Accelerator to provide the bridge APIs. @DougAnderson444, would you like to collaborate on MAM2 enablement?

[DougAnderson444]

@jserv I'm very new to IOTA, so it's going to take me time to get up to speed on this project

[DougAnderson444]

Announcement of MAMv2 is here https://blog.iota.org/mam-update-c-libraries-and-release-2b98f135a0f4

[jserv]

Announcement of MAMv2 is here https://blog.iota.org/mam-update-c-libraries-and-release-2b98f135a0f4

The major problem of MAMv2 (or MAM+) is the lacking of JavaScript language binding. At the moment, only entangled/mam implemented MAMv2 with C interface. However, to support language binding as JavaScript, parameter passing and serialization have to be taken into considerations.

[DougAnderson444]

Ok, I am a bit confused then, as iotaledger/entangled#1183 was closed by iotaledger/entangled#1279 , so are we waiting for additional js bindings apart from those? Maybe I don't understand what differences are part of the "entangled" branch?

[jserv]

Ok, I am a bit confused then, as iotaledger/entangled#1183 was closed by iotaledger/entangled#1279 , so are we waiting for additional js bindings apart from those? Maybe I don't understand what differences are part of the "entangled" branch?

Using emscripten to translate C-based MAMv2 implementation into JavaScripts was known to work, but the major problem is explicit parameter pass and object manipulation. It was not clearly defined. Therefore, no official JavaScript package for MAMv2 appears at the moment.