Masked Authenticated Messaging (MAM) support

[yillkid]

According to IOTA R&D roadmap, IOTA Foundation is planning to rewrite the Masked Authenticated Message (MAM) implementation. Once iota.lib.py completes the transition, dev-team will work on adding that functionality to PyOTA. Therefore the MAM temporarily workaround of python is implement it with iota.lib.js and running as an independent daemon that can access via REST API by swarm-node.

[yillkid]

See the iota-mam-transaction-agent for swarm MAM workaround.

[jserv]

MAM v1 was written in Rust, and its C wrapper can be utilized. Check 產生 IOTA 函式庫: 自 Rust.

[jserv]

We have to split this task into several functional sub-tasks. @HexRabbit, can you help?

[yillkid]

The possible steps to implement MAM along with swarm nodes can be enumerated as following:

1. sign transactions locally at endpoint (usually IoT or client devices);
2. never creating any keys (channel and sideKey) within swarm node
3. accelerate PoW with swarm nodes

Unfortunately, we can not satisfy both (2) and (3) following the scheme of MAM protocol due to resource constraints resulting from IoT devices, which prevent sideKey from being generated efficiently. Swarm nodes could generated keys while endpoint would suffer from the risk of key exposure, that should not be taken into consideration from the perspective of end-to-end security.

Alternatively, it would be strengthful to evaluate solutions other than MAM, especially regarding IOTA Palantír Messaging (IPM), and preliminary evaluation of IPM is available here: IOTA Palantír Messaging (IPM) on Chiota

[jserv]

NOTE: MAM v2 is WIP.