Kawach
The blockchain technology behind Pramaan: tamper-evident software releases and licences verified entirely offline, unlocked inside the customer's TPM chip, and fingerprinted so a leaked copy names its source.
About Kawach
Kawach (कवच, "armour") is a protocol and toolchain for shipping software. Release attestations, licences and revocations live on any EVM chain, but the protected app never queries it: it carries a trust anchor compiled into its binary and checks a Merkle proof it was handed at purchase, so a licensee can run it with no network, forever. Protected code ships as ciphertext whose key is released inside the TPM, bound to one device and timed by the chip's own clock; every licensee's build differs, so a recovered copy is traced back to its owner. Licences can be resold with escrow and publisher royalties, and Pramaan's proof-of-invention notebooks anchor only a Merkle root on chain. 147 Rust tests, 40 contract tests and 59 end-to-end checks pass, with device binding on a real TPM 2.0. Its limits are stated plainly: it does not stop a licensee dumping what they may decrypt (it makes the leak attributable), it does not defeat a kernel debugger without a TEE, and its text watermark does not survive whitespace normalisation.
Highlights
- ▸Licences verified fully offline — a Merkle proof checked against an anchor compiled into the binary; nothing phones home
- ▸Content keys released inside the TPM and bound to one device — a copied install refuses to run
- ▸Traitor tracing: each licensee's build differs, so a leaked copy names its source, with no false accusations across the attack suite
- ▸Compiled-binary watermarks for x86-64 and AArch64 (PE, ELF, Mach-O): 98.9% survival on a real 1.69 MB binary, and the marked binary still runs
Publications from this lab
- Technical report · in preparation · NOV 07, 2026Kawach: Offline-Verifiable Software Shipment, Device-Bound Licensing and Traitor Tracing Anchored on a Public Ledger
A blockchain can make software provenance and licensing tamper-evident, but a protected program running on a machine its publisher does not control, with no network, cannot consult a chain. We describe Kawach, the protocol and toolchain beneath Pramaan, which bridges the two: release attestations, entitlements and revocations are committed on an EVM ledger, and the program carries a trust anchor compiled into its binary and checks a Merkle inclusion proof handed over at purchase, so verification is entirely offline. Protected code ships as ciphertext whose content key is unwrapped only inside the device's TPM 2.0, with P-256 keys that never leave the chip, and only against a valid proof — there is no licence branch to patch out — while expiry is measured against the TPM's own clock rather than the system clock. Because a licensee can always dump what they are entitled to decrypt, every licensee receives a differently marked build — Tardos-coded variants in text, and semantics-preserving instruction re-encodings in x86-64 and AArch64 PE, ELF and Mach-O binaries — from which a recovered copy is traced to its source. On a 1.69 MB binary the binary carrier held 10,036 marks with three-colluder resistance and 98.9% survival under the whitespace attack that defeats the text carrier, the marked binary still ran, and no attack in the suite produced a false accusation. Licences resell through escrow with publisher royalties, and an extension — Pramaan's proof of invention — anchors salted, hash-chained research notebooks that record which steps were human and which the model's, revealing only a Merkle root. The implementation passes 147 Rust tests, 40 contract tests and 59 end-to-end checks, with device binding on a real TPM. It does not prevent a licensee extracting decrypted content, does not resist a kernel debugger without a trusted execution environment, and cannot enforce sealed-state rollback on stock Windows; and timestamps on a private development chain prove nothing to a third party.
Choose the one that fits.
Get your app, venture or R&D done
An app, a venture or R&D — brief us on WhatsApp and get everything built, lightning fast.
Work with the commons For builders & researchersApply as a Fellow
Bring your app, your business — and apply for investment — or your own research. Not built yet? We'll build it with you first.
Apply For investorsInvest in the commons
Back Aitele itself, a lab's research programme, a venture, or a technology release on its way to market — one conversation covers all four.
Invest