Your binary.
Bound to one machine.
Verified before it runs.
DRM3 wraps both CAGM and SPCMP: AES-256-GCM license state, hardware fingerprint binding, server-authoritative use counting, VM and debugger detection. This is not a EULA promise — run the verifier yourself.
Get bound. Get shipped.
cat /etc/machine-id
Persistent OS-level machine identifier.
ip link show | grep "link/ether" | awk '{print $2}' | head -1
Primary NIC hardware address.
grep "model name" /proc/cpuinfo | head -1 | cut -d: -f2 | xargs
CPU model name from /proc/cpuinfo.
grep "physical id" /proc/cpuinfo | head -1 | cut -d: -f2 | xargs
Physical socket ID from /proc/cpuinfo.
samayuktam.licensing@gmail.com
swapnopammitra1308@gmail.com
Send all four values. That's everything needed to issue your binary.
How your license is enforced
/proc/cpuinfo. Network: the binary calls our licensing server directly — once to activate on first launch, then again on every subsequent run to check remaining uses. Both calls are automatic; there is nothing for you to run or configure. Nothing else is read, written, or modified. No local state files. No background service.WSL2: confirm your virtual NIC MAC doesn't regenerate on restart before requesting a license. Run the MAC command, do a full
wsl --shutdown, reopen, and compare. If it changes, flag it when you write in.
Colab: container recycling (idle timeout, disconnect, restart) can produce a different MAC or machine ID and fail the fingerprint check. Fine for a single-session pilot run — not for multi-session use.
activation failed: could not reach licensing server
The binary makes this call itself on every run — there's no separate command for you to run. If you see this, it's your network path: firewall, proxy, or no outbound HTTPS. Remaining uses stay frozen until a run completes end to end.
samayuktam.licensing@gmail.com
swapnopammitra1308@gmail.com
NIC swap, OS reinstall, or new machine will cause the server-side fingerprint check to reject the run. Email your new values and remaining use count — we'll reissue to the new hardware.
rm -f ./cagm ./app
Nothing persistent is written to your machine beyond the binary. Delete it and it's gone.
What CAGM actually does
accuracy, proof, and ie_verify — in that order, on stdout. Everything else stays on stderr.What SPCMP actually does
Pilot pricing
Specifications
The public specification PDF for is no longer available — the PCT filing window has closed and the document has been taken offline. To request access, reach out directly:
Test reports
Your machine. Your binary. No exceptions.
Run the four commands. Mail in the values. Get a binary that only runs on that exact machine, verified online on every use.
START THE HANDSHAKE