Chat with no backend to trust.
One canister. Every message signed.
WASP Bzzz is a Discord-style community platform that runs entirely inside one Internet Computer canister. No servers, no database, no passwords — every action is a signed transaction you can verify.
free · no email · no password · no wallet
shipping the on-chain build today #launch
every post is a signed update call now?
yep — @Ada verified by msg_caller
msg_callerServers, channels, threads.
A real workspace, not a demo. Servers hold channels; channels hold threads; everything is a signed message living inside the canister.
shipping the on-chain build today #launch
every post is a signed update call now?
yep — @Ada verified by msg_caller
verified — receipts are on-chain
Enforced on-chain, not in the UI.
Owners, admins and moderators get real powers — and the canister checks who you are before every privileged action. There is no API to go around.
- Four tiers. Owner, admin, moderator, member — granted per server.
- Pin, lock, time-out. Moderation actions are signed update calls, authorised by your principal.
- Tamper-proof. A locked channel rejects posts at the canister, not just the button.
Markdown, code, spoilers, media.
Say it properly. Format with markdown, drop in fenced code, hide spoilers, react with emoji, and share images and video — all rendered inline, all stored on-chain.
- Markdown & code. Bold, italic, lists and syntax-tinted code blocks.
- Spoilers. Blur text until a reader chooses to look.
- Media. Image uploads and embedded video, no external host.
Release notes for v3 — everything ships today:
if (msg.author == caller) commit(msg);
Ending is: it was on-chain all along — hover to reveal.
A lock that isn't decorative.
Private servers and DMs are returned only to their members, over signed reads — never rendered to the public, cacheable web. Not privacy by obscurity.
founders channel — visible to members
returned only over a signed read
Trust math, not a company.
The same chat features you expect — but the place they run changes what you have to trust.
| Typical chat SaaS | WASP Bzzz on the IC | |
|---|---|---|
| Where it runs | A company's cloud servers | One canister on the Internet Computer |
| Who can read your data | The operator and their database | Only members, over signed reads |
| If the company disappears | Your community goes with it | It runs on-chain, not on us |
| How sign-in works | Email + password to leak | Internet Identity — no password exists |
| Can responses be tampered with | Trust the operator's word | Certified by the Internet Computer |
Don't trust us. Read the canister.
The honest proof isn't a logo wall — it's that you can inspect the live state we run on.
2
3
4
5
6
7
canister 4dcfc-hyaaa-aaaas-qdqbq-cai
state certified by the Internet Computer
reads certified · writes signed update calls
auth Internet Identity · caller = msg_caller
→ view certified stable state
▋
What a community expects.
Your community. Your identity.
On a chain you can verify.
free · no email · no password · no wallet