___|  _ \   |  |    |   |_ _|\ \     / ____|
 |     |   |  |  |    |   |  |  \ \   /  __|
 |   | |   | ___ __|  ___ |  |   \ \ /   |
\____|\___/     _|   _|  _|___|   \_/   _____| 

 --- A GOPHER-LIKE INTERFACE FOR HIVE BLOCKCHAIN ---

Hive-Mail updated to v. 2.1: file encryption added!

BY: @hassemer | CREATED: March 15, 2026, 12:22 p.m. | VOTES: 19 | PAYOUT: $1.30 | [ VOTE ]

Hello friends, hoping you guys are safe and well!

Dropping by just to let you know that Hive-Mail has been updated to version 2.1:

https://hassemer-g.github.io/hive-mail/

*In case you missed the previous posts:
The original post (presenting a prototype)
The first version with a GUI (v. 1.0)

A quick recap: What is Hive-Mail?

Hive-Mail is a project I initiated in early 2025 with the modest aim of improving the built-in Hive encrypted Memo messages, especially to make use of post-quantum cryptography.

Initially meant for the use of just myself and some people I know IRL, later decided to make it openly available to all.

After the publication of the "prototype" in August 2025, and listening to feedback and criticism from several people, I decided to make Hive-Mail simpler by removing on-chain sending of messages (arguably unnecessary and a potential security risk) and add a very easy-to-use GUI so anyone could encrypt messages and safely send them to the desired recipients by any means, including e-mail and messaging apps. This all was implemented in version 1.0.

In sum, Hive-Mail is a protocol that allows anyone to exchange encrypted messages (and now, in v. 2.1, also files!), for free, using any communication means, requiring just a Hive account.

What's new in Version 2.1?

First and foremost: file encryption. Now, in addition to the ability to encrypt text content, Hive-Mail can also encrypt files.

But that's not all! The new version brings a lot of improvements, such as:

• Encrypted output can now be a file or encoded text (user can choose), irrespective of the "plaintext" itself being text or a file (encrypted output as a file requires no encoding, thus considerably more economic)

• All keys, private and public, are now encoded using a custom Base87 implementation, optimised for Hive-Mail

• The use of HQC (Hamming Quasi-Cyclic — a post-quantum asymmetric encryption algorithm) is discontinued. This was a hard decision, but the gargantuan size of the HQC keys was causing more harm than good. Ultimately, Hive-Mail continues fully quantum-resistant, as ML-KEM-1024 (Kyber) remains in use.

• Several improvements applied to our customised hashing routines and the symmetric encryption pipeline, aiming at stronger security and reduced encrypted outputs

Important: if you already have a Version 1 Hive-Mail key registered to your Hive account, you will need to update it to Version 2. This is very simple, just generate a new Hive-Mail key using the button "Create or Change Hive-Mail Key". And that's all, no further action required.

So now you can very easily encrypt not only text but also files, to send by e-mail or whatsapp or however you like 🥳

Enjoy! 🥰

TAGS: [ #hive ] [ #development ] [ #communication ] [ #cybersecurity ]

Replies

@aala.twist | March 17, 2026, 6:32 a.m. | Votes: 0 | [ VOTE ]

Looks a nice addition to #Hive #ecosystem. I have a question. How will the receiver decrypt the mail? Is it mandatory for the receiver to use Hive account for decryption?

@hassemer | March 17, 2026, 7:01 p.m. | Votes: 1 | [ VOTE ]

Thanks! Decrypting a message is super easy, you just use the "Decrypt" button.

A Hive account is not required from the sender of an encrypted message, but the addressee must have an account, because the Public Key is stored onchain. So a Hive account isn't required to encrypt, but it is necessary to perform decryption.

@aala.twist | March 21, 2026, 9:22 a.m. | Votes: 0 | [ VOTE ]

Thank you for spending time to reply a noob

[ BACK TO TRENDING ] [ BACK TO MENU ]
CMD>