[PR #57] Add Voidly Messenger - federated E2E messenger #292

New Issue

GiteaMirror · 2026-06-19T23:46:56-05:00

GiteaMirror commented

2026-06-19 23:46:56 -05:00

📋 Pull Request Information

Original PR: https://github.com/croqaz/awesome-decentralized/pull/57
Author: @EmperorMew
Created: 4/23/2026
Status: 🔄 Open

Base: master ← Head: add-voidly-messenger

📝 Commits (1)

10098ec Add Voidly Messenger

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Adds Voidly Messenger to the Applications list, in alphabetical position between Vdo.Ninja and webcat.

What it is

E2E-encrypted messenger PWA, client-side-only crypto, federated across independent relay operators.

Why it fits this list (decentralization angle)

Federation, not a single server. The SDK (@voidly/agent-sdk) connects to multiple relay nodes. The relay-node is part of the monorepo and self-hostable - anyone can stand one up, and peers federate (peer discovery + cross-relay routing).
The relay is untrusted infrastructure, not a central authority. All crypto happens in the client. Private keys never leave the device. The relay is a metadata-stripping transport: from_did, thread, and type are stripped before storage/forwarding, so a relay operator cannot link sender, recipient, or conversation thread. This is the same "dumb pipe" posture that makes existing entries like Databag and SimpleX Chat fit the list.
No central identity issuer. Identities are did:voidly:<hash-of-ed25519-pubkey> generated locally. There is no account server, no phone number, no email.

Crypto

Signal Protocol: Double Ratchet + X3DH (per-message forward secrecy, post-compromise recovery, async key agreement with signed prekeys).
ML-KEM-768 + X25519 post-quantum hybrid key exchange (NIST FIPS 203) - harvest-now-decrypt-later resistant.
Deniable authentication (HMAC-SHA256 over shared DH secret - both parties can produce the MAC).
Sealed sender, message padding, cover traffic options.

Line added

* [Voidly Messenger](https://msg.voidly.ai): Federated E2E-encrypted messenger PWA. Signal Protocol (Double Ratchet + X3DH) + ML-KEM-768 post-quantum hybrid, metadata-stripping relay the operator cannot link sender/recipient/thread, self-hostable relay-node, client-side-only crypto so the relay is untrusted infrastructure rather than a central authority.

Alphabetical placement respected (the list is wrapped in <sortLines>).

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/croqaz/awesome-decentralized/pull/57 **Author:** [@EmperorMew](https://github.com/EmperorMew) **Created:** 4/23/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `add-voidly-messenger` --- ### 📝 Commits (1) - [`10098ec`](https://github.com/croqaz/awesome-decentralized/commit/10098eca768eb17af2afd2d721ac308db65467a6) Add Voidly Messenger ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description Adds [Voidly Messenger](https://msg.voidly.ai) to the Applications list, in alphabetical position between `Vdo.Ninja` and `webcat`. ## What it is E2E-encrypted messenger PWA, client-side-only crypto, federated across independent relay operators. ## Why it fits this list (decentralization angle) - **Federation, not a single server.** The SDK (`@voidly/agent-sdk`) connects to multiple relay nodes. The relay-node is part of the monorepo and self-hostable - anyone can stand one up, and peers federate (peer discovery + cross-relay routing). - **The relay is untrusted infrastructure, not a central authority.** All crypto happens in the client. Private keys never leave the device. The relay is a metadata-stripping transport: `from_did`, `thread`, and `type` are stripped before storage/forwarding, so a relay operator cannot link sender, recipient, or conversation thread. This is the same "dumb pipe" posture that makes existing entries like Databag and SimpleX Chat fit the list. - **No central identity issuer.** Identities are `did:voidly:<hash-of-ed25519-pubkey>` generated locally. There is no account server, no phone number, no email. ## Crypto - Signal Protocol: Double Ratchet + X3DH (per-message forward secrecy, post-compromise recovery, async key agreement with signed prekeys). - ML-KEM-768 + X25519 post-quantum hybrid key exchange (NIST FIPS 203) - harvest-now-decrypt-later resistant. - Deniable authentication (HMAC-SHA256 over shared DH secret - both parties can produce the MAC). - Sealed sender, message padding, cover traffic options. ## Line added ``` * [Voidly Messenger](https://msg.voidly.ai): Federated E2E-encrypted messenger PWA. Signal Protocol (Double Ratchet + X3DH) + ML-KEM-768 post-quantum hybrid, metadata-stripping relay the operator cannot link sender/recipient/thread, self-hostable relay-node, client-side-only crypto so the relay is untrusted infrastructure rather than a central authority. ``` Alphabetical placement respected (the list is wrapped in `<sortLines>`). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-06-19 23:46:56 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-decentralized#292