idemcore-verify 0.3.0__tar.gz
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- idemcore_verify-0.3.0/LICENSE +202 -0
- idemcore_verify-0.3.0/PKG-INFO +223 -0
- idemcore_verify-0.3.0/README.md +193 -0
- idemcore_verify-0.3.0/idemcore_verify/__init__.py +5 -0
- idemcore_verify-0.3.0/idemcore_verify/__main__.py +121 -0
- idemcore_verify-0.3.0/idemcore_verify/core.py +357 -0
- idemcore_verify-0.3.0/idemcore_verify/samples.py +92 -0
- idemcore_verify-0.3.0/idemcore_verify.egg-info/PKG-INFO +223 -0
- idemcore_verify-0.3.0/idemcore_verify.egg-info/SOURCES.txt +13 -0
- idemcore_verify-0.3.0/idemcore_verify.egg-info/dependency_links.txt +1 -0
- idemcore_verify-0.3.0/idemcore_verify.egg-info/entry_points.txt +2 -0
- idemcore_verify-0.3.0/idemcore_verify.egg-info/top_level.txt +1 -0
- idemcore_verify-0.3.0/pyproject.toml +46 -0
- idemcore_verify-0.3.0/setup.cfg +4 -0
- idemcore_verify-0.3.0/tests/test_verify.py +105 -0
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright 2026 Don Wick
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
|
@@ -0,0 +1,223 @@
|
|
|
1
|
+
Metadata-Version: 2.4
|
|
2
|
+
Name: idemcore-verify
|
|
3
|
+
Version: 0.3.0
|
|
4
|
+
Summary: Check Idemcore per-token hash logs: verify, without trusting us, that two machines produced bit-identical LLM inference.
|
|
5
|
+
Author-email: Don Wick <don.wick@idemcore.net>
|
|
6
|
+
License-Expression: Apache-2.0
|
|
7
|
+
Project-URL: Homepage, https://idemcore.net
|
|
8
|
+
Project-URL: Paper, https://doi.org/10.5281/zenodo.23851129
|
|
9
|
+
Project-URL: Source, https://github.com/idemcore/idemcore-verifier
|
|
10
|
+
Project-URL: Issues, https://github.com/idemcore/idemcore-verifier/issues
|
|
11
|
+
Keywords: reproducibility,deterministic inference,llm,verification,integer inference
|
|
12
|
+
Classifier: Development Status :: 4 - Beta
|
|
13
|
+
Classifier: Environment :: Console
|
|
14
|
+
Classifier: Intended Audience :: Developers
|
|
15
|
+
Classifier: Intended Audience :: Science/Research
|
|
16
|
+
Classifier: Operating System :: OS Independent
|
|
17
|
+
Classifier: Programming Language :: Python :: 3
|
|
18
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
19
|
+
Classifier: Programming Language :: Python :: 3.9
|
|
20
|
+
Classifier: Programming Language :: Python :: 3.10
|
|
21
|
+
Classifier: Programming Language :: Python :: 3.11
|
|
22
|
+
Classifier: Programming Language :: Python :: 3.12
|
|
23
|
+
Classifier: Programming Language :: Python :: 3.13
|
|
24
|
+
Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
|
|
25
|
+
Classifier: Topic :: Software Development :: Testing
|
|
26
|
+
Requires-Python: >=3.9
|
|
27
|
+
Description-Content-Type: text/markdown
|
|
28
|
+
License-File: LICENSE
|
|
29
|
+
Dynamic: license-file
|
|
30
|
+
|
|
31
|
+
# idemcore-verifier
|
|
32
|
+
|
|
33
|
+
[](https://github.com/idemcore/idemcore-verifier/actions/workflows/verify.yml)
|
|
34
|
+
|
|
35
|
+
**Check, without trusting us, that two machines produced bit-identical LLM inference.**
|
|
36
|
+
|
|
37
|
+
Project site: <https://idemcore.net>
|
|
38
|
+
|
|
39
|
+
Idemcore is an integer-only inference engine: the same model, prompt, and
|
|
40
|
+
settings give the *same bits* on an x86 laptop, an ARM phone, and NVIDIA GPUs
|
|
41
|
+
from Turing to Hopper. Every token it scores or generates emits a 64-bit hash
|
|
42
|
+
of the full logit vector and a 64-bit hash of the integer sampling table
|
|
43
|
+
(CDF). A run log is a list of these hashes plus one chained digest (`ALL`).
|
|
44
|
+
|
|
45
|
+
This repository is the **open half** of Idemcore:
|
|
46
|
+
|
|
47
|
+
* the log format and hash protocol ([SPEC.md](SPEC.md)),
|
|
48
|
+
* a small, dependency-free Python verifier (`idemcore_verify/`),
|
|
49
|
+
* the measurement methodology ([METHODOLOGY.md](METHODOLOGY.md)),
|
|
50
|
+
* raw per-token logs from real cross-device runs (`samples/`) and the results
|
|
51
|
+
table they back ([RESULTS.md](RESULTS.md)).
|
|
52
|
+
|
|
53
|
+
The inference kernel itself is not in this repository and is not open source.
|
|
54
|
+
You do not need it to check a claim: the verifier only needs two logs.
|
|
55
|
+
|
|
56
|
+
## Reproduce in 5 minutes
|
|
57
|
+
|
|
58
|
+
You need `git` and Python ≥ 3.9. No GPU, no model and no third-party package.
|
|
59
|
+
|
|
60
|
+
```sh
|
|
61
|
+
# 1. get the verifier and the sample logs (about 6 MB)
|
|
62
|
+
git clone https://github.com/idemcore/idemcore-verifier.git
|
|
63
|
+
cd idemcore-verifier
|
|
64
|
+
|
|
65
|
+
# 2. optional: a clean virtual environment and the `idemcore-verify` command
|
|
66
|
+
python3 -m venv .venv && . .venv/bin/activate
|
|
67
|
+
pip install .
|
|
68
|
+
|
|
69
|
+
# 3. recompute every published hash and re-check every published pair (~5 s)
|
|
70
|
+
python3 -m idemcore_verify samples # same as: make verify or sh verify_samples.sh
|
|
71
|
+
|
|
72
|
+
# 4. check one pair yourself: x86-64 CPU vs NVIDIA L40S, gpt-oss-20b
|
|
73
|
+
python3 -m idemcore_verify compare samples/gpt-oss-20b/x86_64.log \
|
|
74
|
+
samples/gpt-oss-20b/nvidia_l40s.log
|
|
75
|
+
|
|
76
|
+
# 5. the unit tests, including a tamper test
|
|
77
|
+
python3 -m unittest discover -s tests
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Expected output of step 3:
|
|
81
|
+
|
|
82
|
+
```
|
|
83
|
+
checked 65 logs (448904 token rows) and 58 pairs
|
|
84
|
+
PASS: every published hash recomputes and every pair is bit-identical
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
and of step 4:
|
|
88
|
+
|
|
89
|
+
```
|
|
90
|
+
OK samples/gpt-oss-20b/x86_64.log: 512 tokens, ALL 8ec348aaf3b4109c (recomputed 8ec348aaf3b4109c)
|
|
91
|
+
OK samples/gpt-oss-20b/nvidia_l40s.log: 512 tokens, ALL 8ec348aaf3b4109c (recomputed 8ec348aaf3b4109c)
|
|
92
|
+
MATCH: 512/512 positions identical (mode exact; only-in-ref 0, only-in-cand 0)
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
Step 3 recomputes all 65 published digests in
|
|
96
|
+
[samples/HASHES.tsv](samples/HASHES.tsv) from the shipped logs (about 450 000
|
|
97
|
+
token rows, including batched GPU logs) and re-checks all 58 pairs in
|
|
98
|
+
[samples/PAIRS.tsv](samples/PAIRS.tsv). To prove the check is not a rubber
|
|
99
|
+
stamp, edit any hex digit in a log and run it again: the chain breaks.
|
|
100
|
+
|
|
101
|
+
`idemcore-verify samples` looks for `./samples` in the current directory; run
|
|
102
|
+
it from the repository root, or pass `--dir path/to/samples`. `make` is not
|
|
103
|
+
required; every `make` target is a one-line Python command.
|
|
104
|
+
|
|
105
|
+
### Check a live answer from api.idemcore.net
|
|
106
|
+
|
|
107
|
+
The hosted API (`https://api.idemcore.net/v1`, OpenAI-compatible) attaches a
|
|
108
|
+
receipt to every answer, and `GET /v1/receipts/{id}/log` returns that answer's
|
|
109
|
+
per-token log. The API serves the public form of the log (`log_format`
|
|
110
|
+
`idemcore-log/r1-public`): the `pi j h hc` fields of [SPEC.md](SPEC.md) plus the
|
|
111
|
+
`ALL` line, without `freq` and `total`. The verifier accepts both forms (version
|
|
112
|
+
0.3.0 and later). Access needs an API key: sign in to the console at
|
|
113
|
+
<https://console.idemcore.net/#/login> and create one. With a key, save the log and run:
|
|
114
|
+
|
|
115
|
+
```sh
|
|
116
|
+
curl -s https://api.idemcore.net/v1/receipts/RECEIPT_ID/log \
|
|
117
|
+
-H "Authorization: Bearer $IDEMCORE_API_KEY" | jq -r .log_text > answer.log
|
|
118
|
+
python3 -m idemcore_verify check answer.log
|
|
119
|
+
python3 -m idemcore_verify compare answer.log your_rerun.log
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
### Install as a package
|
|
123
|
+
|
|
124
|
+
The verifier is published on PyPI as
|
|
125
|
+
[`idemcore-verify`](https://pypi.org/project/idemcore-verify/) (console script of
|
|
126
|
+
the same name):
|
|
127
|
+
|
|
128
|
+
```sh
|
|
129
|
+
pip install idemcore-verify
|
|
130
|
+
idemcore-verify --version
|
|
131
|
+
idemcore-verify check run.log
|
|
132
|
+
idemcore-verify compare reference.log candidate.log
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
The package contains only the verifier; the sample logs ship with this
|
|
136
|
+
repository.
|
|
137
|
+
|
|
138
|
+
All hash tables, per device, workload and batch size: [EVIDENCE.md](EVIDENCE.md).
|
|
139
|
+
|
|
140
|
+
Requires Python ≥ 3.9, standard library only.
|
|
141
|
+
|
|
142
|
+
## What the verifier checks
|
|
143
|
+
|
|
144
|
+
1. **Well-formedness** – every line has six fields, hashes are 64-bit hex,
|
|
145
|
+
`0 < freq ≤ total < 2^31`, no duplicate positions.
|
|
146
|
+
2. **Chain integrity** – it recomputes the `ALL` digest from the per-token
|
|
147
|
+
lines; editing a single line breaks it.
|
|
148
|
+
3. **Agreement** – it compares a candidate log against a reference log
|
|
149
|
+
position by position, keyed by `(payload, position)`, and prints the first
|
|
150
|
+
divergence (which token, which field). `--subset` allows a short spot check
|
|
151
|
+
(e.g. 128 CPU tokens against a 512-token GPU run).
|
|
152
|
+
|
|
153
|
+
A match on `h` means the two machines computed the **same integer logits for
|
|
154
|
+
the whole vocabulary** at that position, not just the same argmax token. A
|
|
155
|
+
match on `hc` means they built the same integer sampling distribution, so any
|
|
156
|
+
seeded sampler driven by it makes the same choices.
|
|
157
|
+
|
|
158
|
+
## Published pairs
|
|
159
|
+
|
|
160
|
+
| Model | Reference | Candidate | Positions | Result |
|
|
161
|
+
|---|---|---|---|---|
|
|
162
|
+
| Qwen2.5-0.5B, 8-bit | x86-64 CPU | NVIDIA T4 | 3260 | identical |
|
|
163
|
+
| Qwen2.5-0.5B, 8-bit | x86-64 CPU | Galaxy Z Fold5 (Android) | 240 | identical |
|
|
164
|
+
| Qwen2.5-0.5B, 8-bit | x86-64 CPU | Windows 11 ARM64 laptop (Snapdragon X Plus) | 240 | identical |
|
|
165
|
+
| Qwen2.5-7B, 8-bit | x86-64 CPU | NVIDIA A10 | 512 | identical |
|
|
166
|
+
| Qwen2.5-7B, 8-bit | x86-64 CPU | Galaxy Z Fold5 (Android) | 64 (prefix) | identical |
|
|
167
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | NVIDIA A10 | 512 | identical |
|
|
168
|
+
| Qwen2.5-7B, 4-bit (g4) | x86-64 CPU | NVIDIA A10G | 512 | identical |
|
|
169
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | Galaxy Z Fold5 (Android), both CPU code paths | 128 (prefix) | identical |
|
|
170
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | x86-64 CPU, 6 repeat runs (6 and 8 pinned threads) | 512 | identical |
|
|
171
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | NVIDIA A10G and A10, batched B = 1–64, shuffled and staggered (40 logs) | every row of every stream | identical |
|
|
172
|
+
| gpt-oss-20b (MoE) | x86-64 CPU | NVIDIA L40S | 512 | identical |
|
|
173
|
+
| gpt-oss-120b (MoE) | x86-64 CPU (spot check) | NVIDIA H100 | 128 of 512 | identical |
|
|
174
|
+
|
|
175
|
+
Details per file: [samples/MANIFEST.md](samples/MANIFEST.md).
|
|
176
|
+
Qwen2.5-7B 4-bit on Android runs at 3.39 tok/s on the Fold5 (see [RESULTS.md](RESULTS.md)).
|
|
177
|
+
|
|
178
|
+
**Batched GPU serving.** With an improved batched GPU kernel, Qwen2.5-7B 4-bit
|
|
179
|
+
on an NVIDIA A10G serves up to 64 concurrent streams, and every stream's
|
|
180
|
+
per-token hashes match a single-stream x86-64 run at batch sizes 1, 8, 16, 32
|
|
181
|
+
and 64, including shuffled slot order and staggered joins (0 mismatches).
|
|
182
|
+
The same holds on an NVIDIA A10. Aggregate throughput (A10G): 641 tok/s at 8
|
|
183
|
+
streams and 1372 tok/s at 32. Numbers and caveats:
|
|
184
|
+
[RESULTS.md](RESULTS.md#2b-batched-serving-qwen25-7b-4-bit-g-nvidia-a10g).
|
|
185
|
+
The raw batched logs are in `samples/batched/` and are re-checked by step 3 above.
|
|
186
|
+
|
|
187
|
+
## Methodology and benchmarks
|
|
188
|
+
|
|
189
|
+
* How every number was measured (workloads, clocks, baselines, energy,
|
|
190
|
+
quality): [METHODOLOGY.md](METHODOLOGY.md).
|
|
191
|
+
* Results and their caveats: [RESULTS.md](RESULTS.md); every hash, per device,
|
|
192
|
+
workload and batch size: [EVIDENCE.md](EVIDENCE.md).
|
|
193
|
+
* The serving-benchmark kit used in the paper will be published separately and
|
|
194
|
+
linked here.
|
|
195
|
+
|
|
196
|
+
## Paper
|
|
197
|
+
|
|
198
|
+
Don Wick, *Idemcore: Bit-Identical LLM Inference from Phones to Datacenter
|
|
199
|
+
GPUs, with an Open Per-Token Verification Protocol*, preprint, Zenodo,
|
|
200
|
+
2026. DOI: [10.5281/zenodo.23851129](https://doi.org/10.5281/zenodo.23851129).
|
|
201
|
+
Citation metadata: [CITATION.cff](CITATION.cff).
|
|
202
|
+
|
|
203
|
+
## What this does **not** prove
|
|
204
|
+
|
|
205
|
+
* The logs are produced by our engine. A matching pair shows two runs agree;
|
|
206
|
+
it does not prove *which* program produced them. To check a provider, re-run
|
|
207
|
+
the same request on hardware you control (or ask a second party to) and
|
|
208
|
+
compare logs.
|
|
209
|
+
* The hash is FNV-1a-64: fast and good for detecting accidental divergence,
|
|
210
|
+
**not** collision-resistant against an adversary who can choose logits. A
|
|
211
|
+
SHA-256 / BLAKE3 variant of the log is planned; the format has a version.
|
|
212
|
+
|
|
213
|
+
## License
|
|
214
|
+
|
|
215
|
+
Apache-2.0 for everything in this repository (verifier, spec, methodology,
|
|
216
|
+
sample logs). See [LICENSE](LICENSE). Idemcore's inference kernel, weight
|
|
217
|
+
format, and tables are proprietary and are not covered by this license.
|
|
218
|
+
|
|
219
|
+
Contact: Don Wick — don.wick@idemcore.net · Website: <https://idemcore.net>
|
|
220
|
+
· Security reports: [SECURITY.md](SECURITY.md) · Mismatch reports: open an
|
|
221
|
+
issue with the "Hash mismatch" template.
|
|
222
|
+
|
|
223
|
+
Copyright 2026 Don Wick.
|
|
@@ -0,0 +1,193 @@
|
|
|
1
|
+
# idemcore-verifier
|
|
2
|
+
|
|
3
|
+
[](https://github.com/idemcore/idemcore-verifier/actions/workflows/verify.yml)
|
|
4
|
+
|
|
5
|
+
**Check, without trusting us, that two machines produced bit-identical LLM inference.**
|
|
6
|
+
|
|
7
|
+
Project site: <https://idemcore.net>
|
|
8
|
+
|
|
9
|
+
Idemcore is an integer-only inference engine: the same model, prompt, and
|
|
10
|
+
settings give the *same bits* on an x86 laptop, an ARM phone, and NVIDIA GPUs
|
|
11
|
+
from Turing to Hopper. Every token it scores or generates emits a 64-bit hash
|
|
12
|
+
of the full logit vector and a 64-bit hash of the integer sampling table
|
|
13
|
+
(CDF). A run log is a list of these hashes plus one chained digest (`ALL`).
|
|
14
|
+
|
|
15
|
+
This repository is the **open half** of Idemcore:
|
|
16
|
+
|
|
17
|
+
* the log format and hash protocol ([SPEC.md](SPEC.md)),
|
|
18
|
+
* a small, dependency-free Python verifier (`idemcore_verify/`),
|
|
19
|
+
* the measurement methodology ([METHODOLOGY.md](METHODOLOGY.md)),
|
|
20
|
+
* raw per-token logs from real cross-device runs (`samples/`) and the results
|
|
21
|
+
table they back ([RESULTS.md](RESULTS.md)).
|
|
22
|
+
|
|
23
|
+
The inference kernel itself is not in this repository and is not open source.
|
|
24
|
+
You do not need it to check a claim: the verifier only needs two logs.
|
|
25
|
+
|
|
26
|
+
## Reproduce in 5 minutes
|
|
27
|
+
|
|
28
|
+
You need `git` and Python ≥ 3.9. No GPU, no model and no third-party package.
|
|
29
|
+
|
|
30
|
+
```sh
|
|
31
|
+
# 1. get the verifier and the sample logs (about 6 MB)
|
|
32
|
+
git clone https://github.com/idemcore/idemcore-verifier.git
|
|
33
|
+
cd idemcore-verifier
|
|
34
|
+
|
|
35
|
+
# 2. optional: a clean virtual environment and the `idemcore-verify` command
|
|
36
|
+
python3 -m venv .venv && . .venv/bin/activate
|
|
37
|
+
pip install .
|
|
38
|
+
|
|
39
|
+
# 3. recompute every published hash and re-check every published pair (~5 s)
|
|
40
|
+
python3 -m idemcore_verify samples # same as: make verify or sh verify_samples.sh
|
|
41
|
+
|
|
42
|
+
# 4. check one pair yourself: x86-64 CPU vs NVIDIA L40S, gpt-oss-20b
|
|
43
|
+
python3 -m idemcore_verify compare samples/gpt-oss-20b/x86_64.log \
|
|
44
|
+
samples/gpt-oss-20b/nvidia_l40s.log
|
|
45
|
+
|
|
46
|
+
# 5. the unit tests, including a tamper test
|
|
47
|
+
python3 -m unittest discover -s tests
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
Expected output of step 3:
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
checked 65 logs (448904 token rows) and 58 pairs
|
|
54
|
+
PASS: every published hash recomputes and every pair is bit-identical
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
and of step 4:
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
OK samples/gpt-oss-20b/x86_64.log: 512 tokens, ALL 8ec348aaf3b4109c (recomputed 8ec348aaf3b4109c)
|
|
61
|
+
OK samples/gpt-oss-20b/nvidia_l40s.log: 512 tokens, ALL 8ec348aaf3b4109c (recomputed 8ec348aaf3b4109c)
|
|
62
|
+
MATCH: 512/512 positions identical (mode exact; only-in-ref 0, only-in-cand 0)
|
|
63
|
+
```
|
|
64
|
+
|
|
65
|
+
Step 3 recomputes all 65 published digests in
|
|
66
|
+
[samples/HASHES.tsv](samples/HASHES.tsv) from the shipped logs (about 450 000
|
|
67
|
+
token rows, including batched GPU logs) and re-checks all 58 pairs in
|
|
68
|
+
[samples/PAIRS.tsv](samples/PAIRS.tsv). To prove the check is not a rubber
|
|
69
|
+
stamp, edit any hex digit in a log and run it again: the chain breaks.
|
|
70
|
+
|
|
71
|
+
`idemcore-verify samples` looks for `./samples` in the current directory; run
|
|
72
|
+
it from the repository root, or pass `--dir path/to/samples`. `make` is not
|
|
73
|
+
required; every `make` target is a one-line Python command.
|
|
74
|
+
|
|
75
|
+
### Check a live answer from api.idemcore.net
|
|
76
|
+
|
|
77
|
+
The hosted API (`https://api.idemcore.net/v1`, OpenAI-compatible) attaches a
|
|
78
|
+
receipt to every answer, and `GET /v1/receipts/{id}/log` returns that answer's
|
|
79
|
+
per-token log. The API serves the public form of the log (`log_format`
|
|
80
|
+
`idemcore-log/r1-public`): the `pi j h hc` fields of [SPEC.md](SPEC.md) plus the
|
|
81
|
+
`ALL` line, without `freq` and `total`. The verifier accepts both forms (version
|
|
82
|
+
0.3.0 and later). Access needs an API key: sign in to the console at
|
|
83
|
+
<https://console.idemcore.net/#/login> and create one. With a key, save the log and run:
|
|
84
|
+
|
|
85
|
+
```sh
|
|
86
|
+
curl -s https://api.idemcore.net/v1/receipts/RECEIPT_ID/log \
|
|
87
|
+
-H "Authorization: Bearer $IDEMCORE_API_KEY" | jq -r .log_text > answer.log
|
|
88
|
+
python3 -m idemcore_verify check answer.log
|
|
89
|
+
python3 -m idemcore_verify compare answer.log your_rerun.log
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
### Install as a package
|
|
93
|
+
|
|
94
|
+
The verifier is published on PyPI as
|
|
95
|
+
[`idemcore-verify`](https://pypi.org/project/idemcore-verify/) (console script of
|
|
96
|
+
the same name):
|
|
97
|
+
|
|
98
|
+
```sh
|
|
99
|
+
pip install idemcore-verify
|
|
100
|
+
idemcore-verify --version
|
|
101
|
+
idemcore-verify check run.log
|
|
102
|
+
idemcore-verify compare reference.log candidate.log
|
|
103
|
+
```
|
|
104
|
+
|
|
105
|
+
The package contains only the verifier; the sample logs ship with this
|
|
106
|
+
repository.
|
|
107
|
+
|
|
108
|
+
All hash tables, per device, workload and batch size: [EVIDENCE.md](EVIDENCE.md).
|
|
109
|
+
|
|
110
|
+
Requires Python ≥ 3.9, standard library only.
|
|
111
|
+
|
|
112
|
+
## What the verifier checks
|
|
113
|
+
|
|
114
|
+
1. **Well-formedness** – every line has six fields, hashes are 64-bit hex,
|
|
115
|
+
`0 < freq ≤ total < 2^31`, no duplicate positions.
|
|
116
|
+
2. **Chain integrity** – it recomputes the `ALL` digest from the per-token
|
|
117
|
+
lines; editing a single line breaks it.
|
|
118
|
+
3. **Agreement** – it compares a candidate log against a reference log
|
|
119
|
+
position by position, keyed by `(payload, position)`, and prints the first
|
|
120
|
+
divergence (which token, which field). `--subset` allows a short spot check
|
|
121
|
+
(e.g. 128 CPU tokens against a 512-token GPU run).
|
|
122
|
+
|
|
123
|
+
A match on `h` means the two machines computed the **same integer logits for
|
|
124
|
+
the whole vocabulary** at that position, not just the same argmax token. A
|
|
125
|
+
match on `hc` means they built the same integer sampling distribution, so any
|
|
126
|
+
seeded sampler driven by it makes the same choices.
|
|
127
|
+
|
|
128
|
+
## Published pairs
|
|
129
|
+
|
|
130
|
+
| Model | Reference | Candidate | Positions | Result |
|
|
131
|
+
|---|---|---|---|---|
|
|
132
|
+
| Qwen2.5-0.5B, 8-bit | x86-64 CPU | NVIDIA T4 | 3260 | identical |
|
|
133
|
+
| Qwen2.5-0.5B, 8-bit | x86-64 CPU | Galaxy Z Fold5 (Android) | 240 | identical |
|
|
134
|
+
| Qwen2.5-0.5B, 8-bit | x86-64 CPU | Windows 11 ARM64 laptop (Snapdragon X Plus) | 240 | identical |
|
|
135
|
+
| Qwen2.5-7B, 8-bit | x86-64 CPU | NVIDIA A10 | 512 | identical |
|
|
136
|
+
| Qwen2.5-7B, 8-bit | x86-64 CPU | Galaxy Z Fold5 (Android) | 64 (prefix) | identical |
|
|
137
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | NVIDIA A10 | 512 | identical |
|
|
138
|
+
| Qwen2.5-7B, 4-bit (g4) | x86-64 CPU | NVIDIA A10G | 512 | identical |
|
|
139
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | Galaxy Z Fold5 (Android), both CPU code paths | 128 (prefix) | identical |
|
|
140
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | x86-64 CPU, 6 repeat runs (6 and 8 pinned threads) | 512 | identical |
|
|
141
|
+
| Qwen2.5-7B, 4-bit (g) | x86-64 CPU | NVIDIA A10G and A10, batched B = 1–64, shuffled and staggered (40 logs) | every row of every stream | identical |
|
|
142
|
+
| gpt-oss-20b (MoE) | x86-64 CPU | NVIDIA L40S | 512 | identical |
|
|
143
|
+
| gpt-oss-120b (MoE) | x86-64 CPU (spot check) | NVIDIA H100 | 128 of 512 | identical |
|
|
144
|
+
|
|
145
|
+
Details per file: [samples/MANIFEST.md](samples/MANIFEST.md).
|
|
146
|
+
Qwen2.5-7B 4-bit on Android runs at 3.39 tok/s on the Fold5 (see [RESULTS.md](RESULTS.md)).
|
|
147
|
+
|
|
148
|
+
**Batched GPU serving.** With an improved batched GPU kernel, Qwen2.5-7B 4-bit
|
|
149
|
+
on an NVIDIA A10G serves up to 64 concurrent streams, and every stream's
|
|
150
|
+
per-token hashes match a single-stream x86-64 run at batch sizes 1, 8, 16, 32
|
|
151
|
+
and 64, including shuffled slot order and staggered joins (0 mismatches).
|
|
152
|
+
The same holds on an NVIDIA A10. Aggregate throughput (A10G): 641 tok/s at 8
|
|
153
|
+
streams and 1372 tok/s at 32. Numbers and caveats:
|
|
154
|
+
[RESULTS.md](RESULTS.md#2b-batched-serving-qwen25-7b-4-bit-g-nvidia-a10g).
|
|
155
|
+
The raw batched logs are in `samples/batched/` and are re-checked by step 3 above.
|
|
156
|
+
|
|
157
|
+
## Methodology and benchmarks
|
|
158
|
+
|
|
159
|
+
* How every number was measured (workloads, clocks, baselines, energy,
|
|
160
|
+
quality): [METHODOLOGY.md](METHODOLOGY.md).
|
|
161
|
+
* Results and their caveats: [RESULTS.md](RESULTS.md); every hash, per device,
|
|
162
|
+
workload and batch size: [EVIDENCE.md](EVIDENCE.md).
|
|
163
|
+
* The serving-benchmark kit used in the paper will be published separately and
|
|
164
|
+
linked here.
|
|
165
|
+
|
|
166
|
+
## Paper
|
|
167
|
+
|
|
168
|
+
Don Wick, *Idemcore: Bit-Identical LLM Inference from Phones to Datacenter
|
|
169
|
+
GPUs, with an Open Per-Token Verification Protocol*, preprint, Zenodo,
|
|
170
|
+
2026. DOI: [10.5281/zenodo.23851129](https://doi.org/10.5281/zenodo.23851129).
|
|
171
|
+
Citation metadata: [CITATION.cff](CITATION.cff).
|
|
172
|
+
|
|
173
|
+
## What this does **not** prove
|
|
174
|
+
|
|
175
|
+
* The logs are produced by our engine. A matching pair shows two runs agree;
|
|
176
|
+
it does not prove *which* program produced them. To check a provider, re-run
|
|
177
|
+
the same request on hardware you control (or ask a second party to) and
|
|
178
|
+
compare logs.
|
|
179
|
+
* The hash is FNV-1a-64: fast and good for detecting accidental divergence,
|
|
180
|
+
**not** collision-resistant against an adversary who can choose logits. A
|
|
181
|
+
SHA-256 / BLAKE3 variant of the log is planned; the format has a version.
|
|
182
|
+
|
|
183
|
+
## License
|
|
184
|
+
|
|
185
|
+
Apache-2.0 for everything in this repository (verifier, spec, methodology,
|
|
186
|
+
sample logs). See [LICENSE](LICENSE). Idemcore's inference kernel, weight
|
|
187
|
+
format, and tables are proprietary and are not covered by this license.
|
|
188
|
+
|
|
189
|
+
Contact: Don Wick — don.wick@idemcore.net · Website: <https://idemcore.net>
|
|
190
|
+
· Security reports: [SECURITY.md](SECURITY.md) · Mismatch reports: open an
|
|
191
|
+
issue with the "Hash mismatch" template.
|
|
192
|
+
|
|
193
|
+
Copyright 2026 Don Wick.
|