Skip to content

About Obsidian Secure Messenger

Pixxl edited this page Jun 28, 2018 · 1 revision

What is the Obsidian Secure Messenger

For a more detailed look on the Obsidian Secure Messenger and to try out the ongoing Beta, please view our OSM Launch Website: https://osm.obsidianplatform.com/


The Identity Problem

The Obsidian Secure Messenger, or OSM, started with a very typical problem in the communication industry. When creating an account for your favorite chat service, you often need to sacrifice some sort of personal information about yourself such as an **email **or **mobile **number in order to use their service.

This might not seem like a problem as you may be used to giving up information about yourself in day to day transactions. You might not think twice when you're confronted by a checkbox which waives your privacy.

What you may not realize however, is that you just created a link between your online actions and a piece of Personally Identifiable Information, or PII. The Obsidian Platform and The Obsidian Secure Messenger will focus on ensuring that the power and control of your information and privacy is put back into your hands once again.

OSM Security

The Obsidian Secure Messenger was built from the ground up to focus on state-of-the art applied cryptography to give an edge over currently feasible and future attacks. The OSM also does not require any PII that could compromise your identity and all text messages are encrypted end to end ensuring complete protection from middleware attacks.

The end goal of the OSM is to run on a global network of decentralized Obsidian Messaging nodes which will be coupled to the Obsidian Network making it difficult to be targeted by bad actors.

We're currently working on an application specific Whitepaper for the OSM which will go into granular detail about encryption standards used, and the problems the OSM is working to solve. Please follow our social channels for updates.

Link collection secure messengers

Signal admits there is a contact leaking problem:

https://www.wired.com/story/signal-contact-lists-private-secure-enclave/