Skip to content

ChipletOS · Chip printing · for a technical reader

A near-constant-size sign-off record for a photomask: the lab’s exact wording

The lab’s own sentences and figures for this result, word for word, in its working terms, with its limits in full. The plain account is on the result’s page; it says the same things in plain words.

The lab’s plain-English sentence

A way to fold the pass/fail records for every small piece of a chip-printing stencil (photomask) into one summary record of about 1.35 kilobytes that stays that size whether the stencil is split into 64 pieces or about a million, plus a short checking program that uses only standard built-in libraries

  • though the summary record on its own proves nothing, and assurance comes only from opening a number of spot-checked pieces that grows with how small a chance of missing a bad piece the checker wants

Measured across the lab’s tile sweep

stay 1,347-1,379 bytes across 64 to 1,048,576 tiles

The limit to read first, in the lab’s words

Certificate SIZE is O(1) in tile count; certificate ASSURANCE is not.

What the size does not buy

Compact commitment is not compact assurance.

Claim

Fold-annotated certificates compose tile to reticle and stay 1,347-1,379 bytes across 64 to 1,048,576 tiles, checkable by a verifier importing only hashlib, hmac, json and math.

Limits

Compact commitment is not compact assurance. A disclosed section-102 novelty risk exists against Miller, Hicks, Katz and Shi, 'Authenticated Data Structures, Generically' (POPL 2014); the self-caught odd-arity duplication defect is Bitcoin CVE-2012-2459, public since 2012. Residual novelty is the domain observation that the four admission legs form a monoid under (AND, max, union-sum) -- frame the family around that, not the tree. Three fixed defects travel with it, including a false ADMIT this verifier once accepted. The measured compression is 7.934x (839 B against 6,657 B); the chiplet CLI separately PRINTS a compression_ratio of 7.9 that is a hardcoded literal and not a measurement.

All resultsFormal statements

How we show numbers

Every number on this site links to the file it comes from. How each result is checked

  • We never show a number before its file has loaded.
  • A question we have not checked yet is marked as unchecked.
  • A check that found nothing says so.
  • A file with no value for a question says so.
  • A number whose file is missing or has changed is not shown.
  • Two files that disagree about what a number describes are both flagged.
  • A number from too few samples shows its sample size.
  • Two files that give different values are both shown.
  • A file we cannot publish is listed by its fingerprint only.
  • A measurement more than a week old shows its age.
  • A question that does not apply to a page is left off it.
  • A measurement whose program failed is shown as failed.