Skip to main content

What is Zeq

Zeq is one computational surface for physics on a single time base, and ZeqVM is the virtual machine that runs it. That's the whole idea, and it's worth unpacking one clause at a time — because each clause is doing real work.

"For physics"​

Most computers treat physical law as data — a formula you look up and plug numbers into. Zeq treats physical law as the instruction set. The catalogue of operators — a named, standard equation for each — is the machine's vocabulary, and computing means naming the operators you want and letting the engine evaluate them for real, over CODATA constants, to ≤0.1%. You don't implement F = ma; you call NM19.

"One computational surface"​

Ordinary scientific software fragments by regime: one library for quantum, another for classical, another for relativity, each with its own conventions and its own translation layer where they meet. Zeq is one surface for all of it — quantum, classical, relativistic — with no translation layer between regimes. The same call shape, the same constants, the same proof format, whether you're computing a de Broglie wavelength or a Schwarzschild radius.

"On a single time base"​

Everything runs on one clock: the 1.287 Hz HulyaPulse, ticking in Zeqonds (0.777 s). Every computation is stamped to it, every machine ticks on it, every proof carries it. A shared, exact time base is what lets a result made on one node be checked on another — the clock is the common reference the whole framework agrees on.

What it's made of​

Operators

The vocabulary — 1,600+ named physical laws across 65 domains. See them all in the Kinematic Spectrum.

Machines

Your state machine — a private backend with keys, a hash-linked audit chain, and its own clock.

Proofs

Every result carries a ZeqProof any node re-verifies — never "trust me," always demonstrable.

On top of these three sit contracts (standing logic), channels (hosted apps), the economy, security, and the lattice of nodes — all the same primitives, arranged.

How you build on it​

You spin up a machine (free), and compute against it from the CLI, an SDK, MCP, or the extensions. From there you can turn a compute into a contract, put it behind an app, and everything you do lands on your audit chain with a proof. The Guides section is the practical path; this page is the mental model.

Why it's different​

It comes down to one word: verifiable. Ordinary computing hands you a floating-point number and asks you to trust it — run it twice and the bits can disagree, and no one can independently check it's right. Zeq is deterministic and proof-carrying: the same inputs give the same bits on every node, and every result travels with a proof anyone can re-check. It's not a faster calculator; it's reproducible, provable physics.