mobilecoin VS libsignal

On this day last month, v.4.1.0 of the protocol was released, enabling atomic swaps on the MobileCoin blockchain.

There is a distinction between "begin wrong" and "being so absolutely wrong that making a statement transparently communicates how small one's understanding is". The second applies here. He is absolutely wrong here. SGX is one aspect that has some beneficial contribution to the overall ideas in MobileCoin. It is not at all an elementary part. You can read here in detail what happens if SGX would be totally pwned: https://github.com/mobilecoinfoundation/mobilecoin/blob/master/fog-threat-model-2.1.0.md

General thoughts for a MobileCoin Fog Threat Model can be found here: https://github.com/mobilecoinfoundation/mobilecoin/blob/master/fog-threat-model-2.1.0.md E.g. you find a summary of what an 'SGX-compromising Adversary with root on Fog Infrastructure' can achieve.

Since you're passionate about the topic, it might make sense to read a bit about why Signal chose MobileCoin as well as MobileCoin's design goals.

You are welcome to audit the code yourself.

Link here: https://github.com/mobilecoinfoundation/mobilecoin#consensus

I am in the process of building a Go implementation of the libsignal-protocol, which powers the Signal app.

How is twitter intending to use libsignal? I doubt it would be via the primary AGPL license[1], forcing them to publish the source code of their server source code. Does signal sell private licenses?

[1] https://github.com/signalapp/libsignal/blob/main/LICENSE

The Signal Protocol is licensed under AGPLv3 (see here).

Signal protocol is AGPL3 https://github.com/signalapp/libsignal

This is the license for libsignal: https://github.com/signalapp/libsignal/blob/main/LICENSE

The only reference to trademark is:

> Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: