💬 ADAMANT Messenger — ETH/BTC/etc. in-chat payments, open source and secure

[adamant.im]

Learn more about ADAMANT Messenger and why it is profitable to invest. The Whitepaper https://adamant.im/whitepaper/adamant-whitepaper-en.pdf

[snowblack]

WP Adamant Vietnamese v1.5.0

https://drive.google.com/open?id=1bY5Mhjj3Pfr9ifRNN6Byg2tlo9atf99B

Enjoy it!

[adamant.im]

You can trust ADAMANT. The Source Code is public https://github.com/adamant-im

[realbonus]

Adamant iOS 0.3.4 released
* Reading QR codes from photos and images from Photo library
* Saving generated QR codes to Photo library
* Improved connection status handling
* Many background bugs fixed

You can join Adamant iOS TestFlight:
https://adamant.im/adamant-messenger-for-ios/

[adamant.im]

The most secure and anonymous messenger, encrypted with Blockchain — try ADAMANT Messenger right now! https://msg.adamant.im/

[adamant.im]

Adamant iOS 0.3.5 released
* Showing transfer transactions right in chat view. Tap on transfer bubble for details
* Localisation (booth en & ru) updates

You can join Adamant iOS TestFlight:
https://adamant.im/adamant-messenger-for-ios/

[adamant.im]

Dear ADAMANT Messenger users and everyone interested in the project!
You probably already know about today's Telegram unavailability. Telegram users could not send messages and files for three hours.



The ADAMANT messenger works on blockchain and has a distributed system of nodes, which is extremely resistant to various problems, including blockings. Blockchain and ADAMANT — the future of messaging.

We remind you that no one has access to your encryption keys, even the ADAMANT developers. Your personal data is safe and you don't have to worry about it at all.
All who have not connected yet, are invited to try our messenger: msg.adamant.im
You can also join the ADAMANT iOS beta test: adamant.im/en-adamant-messenger-for-ios

[adamant.im]

More than half of the ADM tokens have already been sold!
We invite you to participate in the ICO and to buy what is left.
ADAMANT Messenger is a unique solution for messaging: it cannot be blocked, it is anonymous, completely secure and open source.
The ADAMANT project has found a lot of supporters during its development and the messenger app continues to develop.

[adamant.im]

Join the ADAMANT referral campaign

This is an opportunity to support the project and earn from 10% in the currency with which you bought your ADM tokens.
For example, if someone buys ADM tokens on 1 BTC using your link, you will get 0.1 BTC.
For participants with 500 conversions per day and more we set the referral percentage and present the Dashboard: ref.adamant.im. Use these credentials to login: blca / aclb.

You do not have to register to participate in the ADAMANT referral program!
1. Create your ADM-wallet on msg.adamant.im and copy your identifier; example: U12365234723472324
2. Use your unique referral link ?referal=ADMWALLET; example: ?referal=U12365234723472324
3. Specify this link on your resource (blog, media, banner, etc.) that leads to any page of adamant.im website; example: adamant.im/ico/?referal=U12365234723472324

Referral payments are paid every two weeks. If your referral balance is not empty, you will be contacted via ADAMANT Messenger.

[adamant.im]

We present the parameters storage in blockchain and the new transaction type!
The technologies used in messengers have been being developed for a long time, and the creation of a similar product is an ordinary thing now. However, when the time comes for a paradigm shift, every small improvement requires research, design, development, testing — this is just about ADAMANT.
We are pleased to announce that the ADAMANT team implemented a mechanism for storing contact data (KVS) in blockchain and the new transaction type.
KVS (key-value store) is a way to store information. For each key (for example, the contact name U324242353425354) a certain value can be stored ("John", for example).
The process of storing contact information in case of common client-server technology is simple and clear. ADAMANT is built on blockchain unlike classic messengers, and each operation requires the generation of a transaction on the client side, the transfer of the signed transaction to a node and the distribution to other nodes with agreement and consensus.
KVS is currently used to store the address book, user settings and anti-spam, but the real scope of application is bigger. Thus, we have built this mechanism for the future uses.
KVS transactions are stored in the blockchain along with transactions of other types and are only available to their owners since transaction's content is encrypted with a private key. ADAMANT provides incremental data storage so the client application only transmits the address book changes, not the entire address book. This is very important for blockchain data storage.
KVS and the new transaction type are now implemented in ADAMANT test network and in the console. As soon as the testing is complete they will be released to the live network within 10 days.
What to expect? Soon you will finally be able to save contact names (the address book) and settings, including anti-spam settings.

[adamant.im]

ADAMANT iOS 0.3.7 released
* iPhone X Face ID related crash fixed
* New transfers marks as ‘unread'
* Fixed background fetch and notifications
* In-app notification with messages and transfers


You can join Adamant iOS TestFlight:
https://adamant.im/adamant-messenger-for-ios/

[d34thkn3ll]

TL;DR.
You say you store messages on the blockchain. Yeah, DPoS, improved speed compared to PoW, but: have you ever considered the amounts of data the full nodes will have to store if your messenger will become popular? Wouldn't it lead to centralization, because only a small amount of nodes will be able to process large amounts of data?

upd:
Ok, I've looked through the WP.

I think that the assumption of 300 bytes per message is not very precise, because you also have to store sender and receiver addresses, the signature, probably some additional metadata.
If sender can read sent messages, they should be encrypted and stored twice (encrypted with receiver's private key and sender's private key).
Transactions of other types will also consume hard disk space.

Telling that your messenger is "secure" and "anonymous" is not very correct too.
1) Assuming that one user has his private key compromised, the stealer gains access to the full message history.
2) As I understand the concept, the fact of conversation between two pseudonymous users can be easily proven. It is possible to build a graph on user's connections.
3) At the moment, browser version of the messenger connects to the public server. The client requests transactions belonging to him with his public key. So at the server (full-node) side it is possible to correlate IP-address with the public key. I'd strongly recommend to use this app only via proxy/tor/vpn.

[adamant.im]

TL;DR.
You say you store messages on the blockchain. Yeah, DPoS, improved speed compared to PoW, but: have you ever considered the amounts of data the full nodes will have to store if your messenger will become popular? Wouldn't it lead to centralization, because only a small amount of nodes will be able to process large amounts of data?

upd:
Ok, I've looked through the WP.

I think that the assumption of 300 bytes per message is not very precise, because you also have to store sender and receiver addresses, the signature, probably some additional metadata.
If sender can read sent messages, they should be encrypted and stored twice (encrypted with receiver's private key and sender's private key).
Transactions of other types will also consume hard disk space.

Telling that your messenger is "secure" and "anonymous" is not very correct too.
1) Assuming that one user has his private key compromised, the stealer gains access to the full message history.
2) As I understand the concept, the fact of conversation between two pseudonymous users can be easily proven. It is possible to build a graph on user's connections.
3) At the moment, browser version of the messenger connects to the public server. The client requests transactions belonging to him with his public key. So at the server (full-node) side it is possible to correlate IP-address with the public key. I'd strongly recommend to use this app only via proxy/tor/vpn.

Thanks for joining our Slack!

I'll post a reply here also.

Aleksei Lebedev [11 minutes ago]
Hello! Thanks for your deep interest in ADAMANT.


Aleksei Lebedev [7 minutes ago]
Yeah, we store messages in blockchain, as well as other transaction types. But as ADAMANT do not plan to replace Facebook, we'll have limited, but specified users auditory. As all of transactions need few disk space, and disk space is cheap enough, that will be not a problem we think.


Aleksei Lebedev [7 minutes ago]
As I know all the database sized about 200 MB.


Aleksei Lebedev [6 minutes ago]
1) Yes. We plan to have a possiblity for changing keys within chats.


Aleksei Lebedev [4 minutes ago]
2) You are right again. First thing user can understand there is no way to hide if there is no deep IT knowledge. ADAMANT provide anonymous ID, but it still can be revealed. Later we plan to hide chat transactions in blockchain, like Monero does.


Aleksei Lebedev [2 minutes ago]
3) Yes, but later client will be connected to random node. If there will be many nodes, it will be hard to get IP-public key link. And Tor can be used for sure.


Aleksei Lebedev [2 minutes ago]
> If sender can read sent messages, they should be encrypted and stored twice (encrypted with receiver's private key and sender's private key). — No, we generate common key for both recepient and sender.


Aleksei Lebedev [1 minute ago]
Anyway, there is much space to develop. :slightly_smiling_face:

[adamant.im]

Read about the success of the ADAMANT Messenger in the following publication:
https://neironix.io/news/main/view?id=900

[adamant.im]

Here are the news:
Russia may block WhatsApp, Viber, Telegram even tomorrow
See more at http://www.pravdareport.com/business/companies/02-05-2017/137639-messaging_service_russia-0/

[adamant.im]

Dear supporters of decentralized messaging!
We are glad to inform you that the ADAMANT team is going to Poland (Gdansk) and Germany (Berlin). We are going to visit the BlockYard conference blockyardconference.io/indexEN.html in Poland on April 13-14 and meet our partners in Germany on April 14-15. If you are nearby and are interested to meet the ADAMANT team in person, contact us via ADAMANT Messenger: U15738334853882270577.
Together to the future of messaging!

[adamant.im]

Dear ADAMANT Token (ADM) holders, we are glad to tell you good news.
First iteration of ADAMANT Grows campaign is completed! Thank you for your contribution to the project. Next iteration will run on 05/11/2018. You can get details in the Whitepaper.
Together to the future of messaging!

[adamant.im]

Dear users of ADAMANT Messenger and all interested!
Pavel Evgenov (ADAMANT TECH LABS (ADAMANT Messenger) CEO) will speak at BCI 2018 conference cbcompany.ru/ru/our-events.html in Rostov-on-Don on April 22. If you are nearby and are interested to meet Pavel and ask him some questions, contact us via ADAMANT Messenger: U15738334853882270577.
Together to the future of messaging!

[adamant.im]

Do you want to learn about Future of Messaging more?
Guys from Tokenhunters https://www.youtube.com/channel/UC3c-dWIeVzJrFwpEOxr5PAA made a video interview with ADAMANT Messenger Team in Berlin. The developers answered questions about how blockchain messenger works, shared their opinion on Telegram ban, and told what to do if Internet will be blocked. Now the video is processing, and soon you’ll be able to see interview on English, German and Russian languages. Thanks to Sasha Zilber for the event in Germany.

[adamant.im]

Dear users of ADAMANT Messenger and all interested!
Pavel Evgenov (ADAMANT TECH LABS (ADAMANT Messenger) CEO) will speak at BCI 2018 conference cbcompany.ru/ru/our-events.html in Rostov-on-Don on April 22. If you are nearby and are interested to meet Pavel and ask him some questions, contact us via ADAMANT Messenger: U15738334853882270577.
Together to the future of messaging!