Landauer — Thermodynamic Compute-Cost Oracle 🔥
Landauer sells the physical price of computation. Given an operation DAG it counts
the logically-irreversible bit-erasures, derives the energy floor in joules
(erasures · k_B·T·ln2, ≈ 2.87 zJ per bit at 300 K), the Bennett reversible lower
bound (necessary vs wasteful erasures) and a 0..1 thermodynamic efficiency. The
same principle that says erasing one bit must dissipate at least kT·ln2 of heat —
the bridge between information and the second law.
Built on oracle-core (AIMarket Protocol v2). Where Chronos proves
elapsed time (a VDF), Landauer computes an entropic / thermal floor — an orthogonal
quantity. It neither optimizes nor checks correctness; it audits irreversible
energetics.
# Audit: a 3-input AND tree (two AND gates) erases 2 bits → ~5.7 zJ at 300 K
curl -s -X POST http://localhost:9309/ai-market/v2/invoke -H "Content-Type: application/json" \
-d '{"capability_id":"landauer.audit@v1","input":{"ops":[
{"id":"a","gate":"input"},{"id":"b","gate":"input"},{"id":"c","gate":"input"},
{"id":"g1","gate":"and","inputs":["a","b"]},
{"id":"g2","gate":"and","inputs":["g1","c"]},
{"id":"out","gate":"output","inputs":["g2"]}]}}'
| Capability | What | Price |
|---|---|---|
landauer.audit@v1 |
irreversible_bits, energy_floor_j, reversible/wasteful bits, efficiency, circuit_commitment | $0.01 |
landauer.verify@v1 |
trustless replay — recompute the erasure count + floor and check a claim | $0.001 |
Verifiable, not asserted. The audit is a pure function of a SHA-256
circuit_commitment; the irreversibility of each gate is log2 of the collapse in
distinguishable states (fan-in bit loss), summed over a deterministic topological
traversal to an integer. Any verifier replays the count and reproduces
energy_floor_j bit-for-bit. It is a proof about the geometry of information, not a
hardware measurement.
Full physics, math, diagrams and use cases: docs/en.md · docs/ru.md · docs/es.md.
Part of the AICOM oracle family. MIT.
Metadata
Release files for aimarket-oracle-landauer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| aimarket_oracle_landauer-0.1.0.tar.gz | 14.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aimarket_oracle_landauer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.9 kB
Release files / aimarket_oracle_landauer-0.1.0.tar.gz
| Download URL | aimarket_oracle_landauer-0.1.0.tar.gz |
|---|---|
| Size | 14.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
44edb3958ada7e5c8427470c38c57ee267e2d6ba927b8179248ebc4254d5ac5a
|
|
BLAKE2b-256 checksum How to use checksums |
3b90a1f42098191e845ba98e2060cfab551e14759c025a037d209e318727f12e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / aimarket_oracle_landauer-0.1.0-py3-none-any.whl
| Download URL | aimarket_oracle_landauer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
216ab321a6831b5feb542ff3bf29d8578894e8054f55bf6c2319ac65db968aa5
|
|
BLAKE2b-256 checksum How to use checksums |
462f3d78615b0f986b6f908da294b3d5a8de3e3b54da927d7e63fd91eda1bbcc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for aimarket-oracle-landauer 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.