Maktub Community
Build it, run it, teach it. In the open.
It is written. And only for whom it is written.
Maktub is an open protocol for sealed letters. You seal a message to the people you choose and set a timer. If you stop checking in, it's delivered. Nobody can stop it, and only those people can read it.
The community builds apps on it, runs its networks, teaches people about cryptography and blockchains, and takes it to conferences. Everything happens in public, including our plans, outreach, grant applications, funding strategy and the reasons behind our decisions.
Everything runs on testnet today. Mainnet waits on audits.
Ways to take part
- Warden node operator. Run one of the independent nodes that release a decryption key only when an on-chain condition is met. We especially want universities and research groups. Operators are credited, not paid. Read the invitation.
- Executor operator. Run the node that triggers delivery when a timer runs out. Start on testnet.
- Builder. Make an app or tool with the SDK. Builder guide and ideas to pick up.
- Reviewer. Read the contracts and cryptography before the audit. Where to look.
- Educator. Make conversational videos, explainers, talks and translations. Video series & scripts, YouTube (@maktub-it) and topics.
- Outreach. Find grants and conferences, and help write applications. Grants and events.
Ideas to build on Maktub
The protocol does one thing: deliver an encrypted message when a condition is met. Everything else—user interfaces, reminders, team workflows and domain-specific tools—belongs in apps built by contributors on Base Sepolia testnet. Read the builder guide or claim an idea in Issue #3:
- Trailhead & national park "miner's tally board". Before descending into a shaft, coal miners hang their brass token ("tally") on a surface board and reclaim it when they walk back out—so the surface team immediately knows if anyone is still underground at shift change. Build the same safety net for national parks and trekking spots on
MaktubCore+ Warden: the park's rescue station publishes itsRecipientRegistryaddress via a trailhead QR code, and trekkers seal a Beat with their planned route, vehicle plate and return window (watch Episode #4). When they return safely and deactivate it, nobody can read the sealed route card; if they don't return before the timer expires, the park's rescue dashboard unlocks where and when to look. - CLI & cron check-in tool for servers and field teams. A lightweight terminal client wrapping
@bytesbrains/maktub-sdk(status,checkin,seal) with hardware-key support. - Notes & document plugin for digital estate or journalism continuity. Seal local markdown notes to a designated editor or family member using
@bytesbrains/maktub-sdkand Warden double-wrap so your work survives you if illness or an accident prevents you from delivering it yourself. - Business & infrastructure continuity kit ("key-person switch"). Multi-recipient Beat addressed to co-maintainers with a 14- or 30-day check-in window and handover runbook.
- Browser extension for one-click check-ins. Client-local toolbar indicator showing time remaining before your next check-in, with one-click timer reset and no central push server.
- Agent-to-agent coordination & alerting on
MaktubFlash. Verifiable, end-to-end encrypted payloads between scripts, bots and human operators viaMaktubFlashandRecipientRegistryV2.
What Maktub claims, and what it doesn't
Maktub claims two things only: delivery is guaranteed, and only the people you chose can read the message.
It is not an anonymity tool. Who sent a letter, who it goes to and when are all visible on-chain. Only the contents are secret.
How we work
- How to contribute in each role
- What we publish and the few things we don't
- Every decision so far, with the reasons
- The checklist everything we publish must pass
- Report security problems privately, following SECURITY.md, not in public issues.