S
social-and-communicationsinfrastructureapplicationsdefi
solDM — a serverless, E2E-encrypted private chat with zk compression & quantum resistance on Solana (powered by Light Protocol)
Ecosystems:
S
Use Cases:
infrastructuremessaging
Openness
| Project Phase | MAINNET |
| Project Launch Day | JAN 2ND, 2026 |
| Assets Used | SOL |
| Native Token | NOT AVAILABLE |
Technology
| Open Source | Yes |
| Decentralized Storage | Yes |
| Upgradability | No |
| Peer to Peer (P2P) | Supported |
| Asset Custody | non-custody |
| Technology Type | No data available |
PrivacyEnabled by default
| Know Your Customer (KYC) | Not Required |
| Privacy Policy | Not Defined |
| Compliance | No data available |
| Sign-in Requirements | No data available |
| Collected Data | None |
| Data Usage | None |
Security
| Technical Dependency | We’ve designed solDM to avoid “one server goes down → chat dies” and “one database leak → messages leak”, but there are still a few realistic failure modes to acknowledge: 1. If a user’s device/keystore is compromised, their messages can be decrypted (same as any E2EE system). 2. Individual RPCs can rate-limit, but users can switch providers, the protocol does not require a single RPC. |
| Social Dependency | solDM does not custody user private keys. Message encryption keys live client-side only. We will run an external security audit and publish a threat model + audit summary. Open-sourcing is planned to make the system verifiable by the community. |
| Third-party Dependency | solDM is built natively on Solana and depends on a small number of external components: 1. Solana mainnet / RPC providers for submitting transactions and reading on-chain state 2. Light Protocol for zk-compressed state (the message-state / inbox commitments are compressed and anchored on Solana via Light’s infrastructure). 3. Dialect for optional wallet-native notifications (push/alerts for new message events without exposing plaintext) 4. Content storage layer for ciphertext blobs (currently IPFS via Pinata in prototype). Critical note: encryption happens client-side, these dependencies don't have access to plaintext. |
Audits
No security audits available for this project.