We build sovereign infrastructure: chains, wallets, settlement and financial systems that hold up when the institutions around them cannot. Cairo-based venture studio; applied R&D in Web3, AI and robotics.
Everything in this organisation is part of the Forum, an initiative by Mercatura Forum: one of MENA's largest institutionally developed open-source deep-tech initiatives, and one of the region's most extensive integrated sovereign software stacks. The Thebes substrate, its developer tools, the example applications and the financial products below are one body of work, under one licence (Apache 2.0) and one team attribution, and every repository is meant to be read, run and built on by anyone.
🌐 thebesprotocol.com: the official site
Distributed cloud hosting for Egypt and the GCC. Everything below runs on it.
Frontend, backend, and data: replicated across every validator, finalized by a Byzantine quorum, signed under post-quantum certificates on the consensus critical path. No servers, no cloud bill, nothing to take down.
Start here, in order:
| Step | Where | What you get |
|---|---|---|
| 0. Start | thebesprotocol.com | The product site: what Thebes is, what it costs, and how to put a site on it |
| 1. Understand | Thebes-Protocol- | The hub: homepage, technical spec, docs, and small starters (Motoko and Rust) |
| 2. See it | The example library | Twelve full-stack applications, each one live on-chain: store, chat, CRM, finance, medical imaging, ISO 20022 banking, and more |
| 3. Build | thebes-sdk + thebes-lib | The frontend SDK (@thebes/sdk: boundary client, React hooks, passkey gate) and the Motoko backend library (Admin, Users, Pagination, Invoices) |
| 4. Deploy | thebes-deploy releases · CLI guide | One binary. thebes-deploy deploy compiles, installs, uploads the frontend, prints the live URL |
| 5. Go further | digital-asset-exchange | A sovereign DvP exchange: cash, shares, and land titles settling in one indivisible step |
Your users sign in with a passkey: no wallets, no seed phrases, no extensions.
A first public release of a Forum repository arrives as a single commit, and that is by design. Each product is built in a private tree through iteration, test batteries, oracle comparison and review, and the public repository is cut from it clean: the source, the tests, the design and verification records, and nothing of the lab work behind them. What is published is the result that reproduces, so that contributors build on a verified base rather than on a history of experiments. From the first release onward, the public repository is the place where work continues in the open: issues, pull requests and releases happen there.
Financial systems that run as smart contracts, each with a provable record, a test battery and an architecture document. Apache 2.0.
| Repository | What it is |
|---|---|
| Manticore | Core banking and payments: a provable double-entry journal, maker-checker on every money-moving act, ISO 20022 and Mojaloop payments, certified reports |
| Solari | An audit system for audit firms: a hash-chained engagement trail, journal-entry testing, passkey sign-offs, figures a third party can verify |
| Tachyon | Delivery-versus-payment settlement: two-phase escrow, both-or-neither settlement, a batch matching engine, certified receipts |
- ICRC-ME: a self-indexing ledger standard.
- LiteCoin-node: a Litecoin full node as a smart contract.
- ICP-GPU: GPU-accelerated cryptography for chain workloads.
Maintained by the Thebes Core Team. Open to contributors: open an issue on the repository concerned.
