Protocols alert users via email, Telegram, and SMS — without ever learning their contact info. Users stay in control. Always.
How it works
Three steps. No email stored anywhere. Every delivery provably on-chain.
Your protocol sends a wallet address and message payload. No email address required — ever.
Herald resolves the wallet to an encrypted contact stored on-chain via the Privacy Registry PDA.
Herald's secure decryption layer processes the encrypted payload in-memory, then delivers via Email, Telegram, or SMS before writing a ZK receipt.
Interactive Comparison
See how Herald eliminates database vulnerabilities. For the protocol, implementation is simplified down to a single wallet connection.
Users are forced to manually enter private contact details alongside their wallet signature, creating a permanent mapping on your servers.
Simulate the Web2 user register flow
Simplify user onboarding. Users simply click one button to connect. Your backend saves only their standard wallet address — no email database required.
No email forms. No phone inputs.
All PII is encrypted on-chain.
Click "Connect" to subscribe securely
Two audiences. One infrastructure.
Alert your users without ever touching their contact data. Herald handles routing, delivery, and compliance.
Register once. Receive DeFi alerts from any Herald-integrated protocol — without sharing your email with anyone.
Under the hood
Registry, delivery, and on-chain proof — the parts that keep contact data private.
On-chain identity via Anchor PDAs. You own the record — Herald can read it to route a message, but can never modify or delete it.
Every delivery writes an immutable ZK-compressed leaf to Solana. Provable, permanent, and $0.0001 each.
Email, Telegram, and SMS — whichever channel your users prefer.
First notification live in under 5 minutes. The SDK handles encryption and resolution.
Native USDC streaming. No credit cards, no invoices.
Multi-AZ AWS with Helius RPC. 99.9% SLA on Growth and Scale tiers.
Developer experience
Our SDK handles the complex encryption, on-chain identity resolution, and ZK receipt writing. You just call notify().
Under the Hood
Deep dive into the cryptographic architecture and routing layers powering privacy-first notifications.
Herald's on-device key sealer ensures that sensitive user contact details (emails, phone numbers, Telegram handles) never touch a centralized database. The sealing handshake encrypts user details directly in their browser before recording the cipher on the Solana blockchain.
Your email or Telegram handle is fully encrypted before it leaves your device. No protocol, not even Herald, can view or access your plaintext contact details without your authorization.
Call notify() using only the user's wallet address. Herald automatically resolves the on-chain registry record, decrypts the destination inside secure enclaves, and delivers the notification.

Pricing
No credit card required. Pay with any Solana wallet via native USDC streaming.
For building and testing your integration.
Email delivery, sandbox & ZK receipts included.
For protocols with an active user base.
Everything in Developer, plus more channels, seats & SLA.
For high-volume protocols and growing teams.
Everything in Growth, plus more channels, seats & SLA.
Custom volume, SLAs, and dedicated support.
Everything in Scale, plus more channels, seats & SLA.
All tiers include ZK receipts · No hidden fees · Cancel anytime
Pay with USDC via any Solana wallet — view full pricing details →
Community · Early Believers
Orynth is where Solana builders and early believers signal conviction in products they believe in. Herald is listed — join the community shaping what gets built.
Real-time upvote count from the Orynth community. Updates automatically.
Early believer benefits
Install the SDK, call notify(), and Herald handles encryption, on-chain resolution, and delivery.
npm i @herald-protocol/sdk