eif-sdk 0.1.0__tar.gz

eif_sdk-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

eif_sdk-0.1.0/NOTICE

@@ -0,0 +1,12 @@
+Evidence Integrity Framework (EIF)
+Copyright 2026 NeuralWeaves Technology Private Limited and the EIF contributors
+
+This product includes software developed by NeuralWeaves Technology Private
+Limited and contributors to the eif-format project.
+
+The EIF Format Specification and this reference implementation are published
+under the Apache License, Version 2.0, which includes an express grant of
+patent rights from contributors to users. See LICENSE for the full terms.
+
+Portions of the Merkle tree construction follow the approach described in
+RFC 6962 (Certificate Transparency), IETF, 2013.

eif_sdk-0.1.0/PKG-INFO

@@ -0,0 +1,199 @@
+Metadata-Version: 2.4
+Name: eif-sdk
+Version: 0.1.0
+Summary: Reference implementation of the Evidence Integrity Framework (EIF) image provenance format
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://eif-format.org
+Project-URL: Specification, https://github.com/eif-format/specification
+Project-URL: Source, https://github.com/eif-format/eif-sdk
+Project-URL: Issues, https://github.com/eif-format/eif-sdk/issues
+Keywords: provenance,authenticity,forensics,image,cryptography,c2pa
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Legal Industry
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Multimedia :: Graphics
+Classifier: Topic :: Security :: Cryptography
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Requires-Dist: cryptography>=41.0
+Requires-Dist: Pillow>=10.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.4; extra == "dev"
+Requires-Dist: pytest-cov>=4.1; extra == "dev"
+Requires-Dist: ruff==0.14.4; extra == "dev"
+Dynamic: license-file
+
+# EIF SDK
+
+**Reference implementation of the Evidence Integrity Framework — an open file format that binds a photograph to cryptographic proof of how it was captured.**
+
+[![CI](https://github.com/eif-format/eif-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/eif-format/eif-sdk/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/eif-format/eif-sdk/blob/main/LICENSE)
+[![Spec](https://img.shields.io/badge/spec-v1.0-informational)](https://github.com/eif-format/specification)
+
+---
+
+## The problem
+
+A claims adjuster receives a photograph of a damaged bumper. A lender receives a photograph of equipment they are financing. A court receives a photograph of a scene. In each case a decision worth money follows from pixels, and in 2026 pixels can be fabricated by anyone with a phone in under two minutes.
+
+The instinctive response is detection: build a classifier that spots fakes. We tried that first and published the result. Across 150+ images and four physics-based forensic probes, the best classifier we could build reached 74% accuracy under leave-one-out cross-validation. That is not a number you can deny a claim with, and it gets worse every time a generative model improves. Detection is a race against an adversary who is improving faster than the defence.
+
+EIF takes the other route. Rather than asking "is this image fake?", it makes it possible to ask "can this image prove where it came from?" — a question with a cryptographic answer instead of a statistical one.
+
+## What EIF does
+
+An `.eif` file contains five blocks:
+
+| Block | Purpose |
+|---|---|
+| **Capture Attestation Block** | When, what device, what software, what location, and against what server-issued challenge |
+| **Structural Integrity Layer** | A Merkle tree over a grid of image tiles |
+| **Cryptographic Seal** | One ECDSA P-256 signature binding the CAB, the tree root, and the image data together |
+| **Provenance Chain** | Append-only, hash-linked record of every hand the file passed through |
+| **Image Data** | The pixels |
+
+Three properties follow from that structure.
+
+**The proof cannot be stripped.** It is not metadata sitting beside the image; it is the container. Remove it and you no longer have an EIF file — you have an ordinary image with no claim to make.
+
+**Tampering is localised, not just detected.** Because the signature covers a per-tile Merkle tree rather than a single whole-image hash, a verifier can recompute the tree and report exactly which tiles changed. "This file is invalid" is not useful to a claims handler. "Tiles 34, 35, 44 and 45 changed — the region around the left headlight" is.
+
+**Verification works offline.** Four of the five verification levels complete with no network access, no trust service, and no vendor. Evidence has to be checkable in a courtroom, in an adjuster's car, and in ten years' time, none of which guarantee a working connection to somebody's server.
+
+## Install
+
+```bash
+pip install eif-sdk
+```
+
+From source:
+
+```bash
+git clone https://github.com/eif-format/eif-sdk.git
+cd eif-sdk
+pip install -e ".[dev]"
+pytest
+```
+
+## Use it in sixty seconds
+
+```bash
+eif keygen --out signing-key.pem
+eif capture damage.png --key signing-key.pem --challenge "srv-nonce-7f3a"
+eif verify damage.eif --key signing-key.pub.pem
+```
+
+Then prove the localisation claim to yourself:
+
+```bash
+eif tamper-test damage.eif --x 300 --y 200 --width 80 --height 60
+```
+
+```
+Verification result: NOT VALID
+  L1  Format           pass
+  L2  Cryptographic    FAIL
+      - seal signature does not verify over this CAB, structural integrity layer and image data
+      - recomputed tile tree does not match the sealed root
+  L3  Temporal         pass
+  L4  Provenance       pass
+  L5  Device           not evaluated
+
+  Tamper localisation: 4 of 80 tiles altered
+      tile    34  (col 4, row 3)  pixels [256,192]-[320,256]
+      tile    35  (col 5, row 3)  pixels [320,192]-[384,256]
+      tile    44  (col 4, row 4)  pixels [256,256]-[320,320]
+      tile    45  (col 5, row 4)  pixels [320,256]-[384,320]
+```
+
+## Use it from Python
+
+```python
+from eif import CaptureAttestation, Device, EIFFile, KeyPair, Location, imaging
+
+keypair = KeyPair.generate()
+
+attestation = CaptureAttestation(
+    device=Device(
+        make="Acme", model="Field-1", os="Android 15",
+        app_id="com.example.claims", app_version="2.3.0",
+    ),
+    location=Location(latitude="12.9716", longitude="77.5946", accuracy_m=8),
+    challenge="srv-nonce-7f3a",        # issued by your server, seconds before capture
+    session_id="claim-2026-0041",
+)
+
+sealed = EIFFile.capture(imaging.encode_png("damage.jpg"), attestation, keypair)
+sealed.save("damage.eif")
+```
+
+Verifying, with the signing key pinned:
+
+```python
+report = EIFFile.load("damage.eif").verify(expected_public_key=keypair.public_key)
+
+if not report["valid"]:
+    for tile in report["L2_cryptographic"]["altered_tiles"]:
+        print(f"altered region: {tile['bounds']}")
+```
+
+## The verification protocol
+
+| Level | Question | Network |
+|---|---|---|
+| **L1 Format** | Is this a well-formed EIF file? | offline |
+| **L2 Cryptographic** | Does the seal verify over this CAB, tree and image? If not, which tiles changed? | offline |
+| **L3 Temporal** | Are the timestamps internally coherent and plausible? | offline |
+| **L4 Provenance** | Is the chain of custody unbroken? | offline |
+| **L5 Device** | Is the signing key attested to real hardware? | online |
+
+Verification never raises on an invalid file; it returns a structured report. Each level is reported independently because the levels fail for different reasons and a relying party needs to make different decisions about each.
+
+## The challenge, and the attack it addresses
+
+Provenance systems that only record "a real camera took this photograph" are defeated by an attack that costs nothing: generate a fake image, display it on a screen, photograph the screen with a genuine camera. The capture is real, the signature is honest, and the content is fabricated.
+
+EIF's answer is the `challenge` field. Your server issues a nonce immediately before capture; the capture pipeline binds it into the Capture Attestation Block before signing. An image produced any other way cannot carry a fresh, unused, server-recognised nonce for a session you opened. This does not make recapture impossible — nothing in software does — but it moves the attack from "free and instant" to "requires real-time control of a device inside your session," which is a different economic proposition for a fraudster.
+
+Captures with no challenge are permitted and are honestly weaker. Treat them as a lower assurance tier.
+
+## Where this fits alongside C2PA and JPEG Trust
+
+EIF is not a competitor to [C2PA Content Credentials](https://c2pa.org) or [JPEG Trust (ISO/IEC 21617)](https://jpeg.org/jpegtrust/), and positioning it as one would be dishonest. Those efforts have the ecosystem — camera manufacturers, platforms, an ISO process — and they solve the problem they set out to solve: recording and travelling with a content history across a general-purpose media supply chain.
+
+EIF addresses a narrower case those systems do not target: **high-assurance evidence capture**, where the relying party controls the capture pipeline, the stakes justify a stricter model, and two specific requirements apply that general provenance does not meet — knowing *where* in the frame an image changed, and binding a capture to a session the relying party opened.
+
+An EIF file can carry a C2PA manifest as an annotation, and an EIF verifier can treat a valid Content Credential as one input among several. Interoperability notes are in the [specification repository](https://github.com/eif-format/specification/blob/main/spec/Interop.md).
+
+## Honest limitations
+
+Read these before you build anything on this.
+
+- **v1.0 handles losslessly-decodable images only (PNG).** JPEG decoding is not bit-exact across libraries, so tile hashes computed at capture would not reliably recompute on a verifier's machine. Rather than ship a structural integrity layer that produces false tamper reports, lossy profiles are deferred. This is the largest practical limitation and the first thing v1.1 must address.
+- **A signature proves who signed, not that the content is true.** EIF can tell you an image was sealed by a specific key at a specific time and has not changed since. It cannot tell you the adjuster photographed the right car.
+- **Software keys are only as good as the device.** The security of the whole scheme rests on the private key. This SDK generates software keys, which are appropriate for development. Production capture should sign inside a TEE, Secure Enclave, or StrongBox-backed keystore, and L5 exists to let a verifier check that.
+- **The provenance chain records what was recorded.** It detects alteration of the sequence. It cannot detect a handler who simply never appended an entry.
+- **No mobile SDK yet.** Android and iOS are the platforms this format actually needs. They are not built.
+- **The specification is v1.0 and has not been through independent security review.** If you find a flaw, please tell us — see [SECURITY.md](https://github.com/eif-format/eif-sdk/blob/main/SECURITY.md).
+
+## Repositories
+
+| Repository | Contents |
+|---|---|
+| [`specification`](https://github.com/eif-format/specification) | The format specification, JSON schemas, and shared test vectors |
+| [`eif-sdk`](https://github.com/eif-format/eif-sdk) | This reference implementation |
+| [`research`](https://github.com/eif-format/research) | Papers, datasets and methodology |
+
+## Contributing
+
+Independent implementations in other languages are the single most valuable contribution. A format with one implementation is a product; a format with several is a standard. See [CONTRIBUTING.md](https://github.com/eif-format/eif-sdk/blob/main/CONTRIBUTING.md).
+
+## Licence
+
+Apache License 2.0. See [LICENSE](https://github.com/eif-format/eif-sdk/blob/main/LICENSE) and [NOTICE](https://github.com/eif-format/eif-sdk/blob/main/NOTICE).
+
+The Apache 2.0 licence includes an express patent grant covering this implementation. Patent applications relating to the format have been filed in India; the licence grant applies to the contributed code as described in Section 3 of the licence.

eif_sdk-0.1.0/README.md

@@ -0,0 +1,171 @@
+# EIF SDK
+
+**Reference implementation of the Evidence Integrity Framework — an open file format that binds a photograph to cryptographic proof of how it was captured.**
+
+[![CI](https://github.com/eif-format/eif-sdk/actions/workflows/ci.yml/badge.svg)](https://github.com/eif-format/eif-sdk/actions/workflows/ci.yml)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](https://github.com/eif-format/eif-sdk/blob/main/LICENSE)
+[![Spec](https://img.shields.io/badge/spec-v1.0-informational)](https://github.com/eif-format/specification)
+
+---
+
+## The problem
+
+A claims adjuster receives a photograph of a damaged bumper. A lender receives a photograph of equipment they are financing. A court receives a photograph of a scene. In each case a decision worth money follows from pixels, and in 2026 pixels can be fabricated by anyone with a phone in under two minutes.
+
+The instinctive response is detection: build a classifier that spots fakes. We tried that first and published the result. Across 150+ images and four physics-based forensic probes, the best classifier we could build reached 74% accuracy under leave-one-out cross-validation. That is not a number you can deny a claim with, and it gets worse every time a generative model improves. Detection is a race against an adversary who is improving faster than the defence.
+
+EIF takes the other route. Rather than asking "is this image fake?", it makes it possible to ask "can this image prove where it came from?" — a question with a cryptographic answer instead of a statistical one.
+
+## What EIF does
+
+An `.eif` file contains five blocks:
+
+| Block | Purpose |
+|---|---|
+| **Capture Attestation Block** | When, what device, what software, what location, and against what server-issued challenge |
+| **Structural Integrity Layer** | A Merkle tree over a grid of image tiles |
+| **Cryptographic Seal** | One ECDSA P-256 signature binding the CAB, the tree root, and the image data together |
+| **Provenance Chain** | Append-only, hash-linked record of every hand the file passed through |
+| **Image Data** | The pixels |
+
+Three properties follow from that structure.
+
+**The proof cannot be stripped.** It is not metadata sitting beside the image; it is the container. Remove it and you no longer have an EIF file — you have an ordinary image with no claim to make.
+
+**Tampering is localised, not just detected.** Because the signature covers a per-tile Merkle tree rather than a single whole-image hash, a verifier can recompute the tree and report exactly which tiles changed. "This file is invalid" is not useful to a claims handler. "Tiles 34, 35, 44 and 45 changed — the region around the left headlight" is.
+
+**Verification works offline.** Four of the five verification levels complete with no network access, no trust service, and no vendor. Evidence has to be checkable in a courtroom, in an adjuster's car, and in ten years' time, none of which guarantee a working connection to somebody's server.
+
+## Install
+
+```bash
+pip install eif-sdk
+```
+
+From source:
+
+```bash
+git clone https://github.com/eif-format/eif-sdk.git
+cd eif-sdk
+pip install -e ".[dev]"
+pytest
+```
+
+## Use it in sixty seconds
+
+```bash
+eif keygen --out signing-key.pem
+eif capture damage.png --key signing-key.pem --challenge "srv-nonce-7f3a"
+eif verify damage.eif --key signing-key.pub.pem
+```
+
+Then prove the localisation claim to yourself:
+
+```bash
+eif tamper-test damage.eif --x 300 --y 200 --width 80 --height 60
+```
+
+```
+Verification result: NOT VALID
+  L1  Format           pass
+  L2  Cryptographic    FAIL
+      - seal signature does not verify over this CAB, structural integrity layer and image data
+      - recomputed tile tree does not match the sealed root
+  L3  Temporal         pass
+  L4  Provenance       pass
+  L5  Device           not evaluated
+
+  Tamper localisation: 4 of 80 tiles altered
+      tile    34  (col 4, row 3)  pixels [256,192]-[320,256]
+      tile    35  (col 5, row 3)  pixels [320,192]-[384,256]
+      tile    44  (col 4, row 4)  pixels [256,256]-[320,320]
+      tile    45  (col 5, row 4)  pixels [320,256]-[384,320]
+```
+
+## Use it from Python
+
+```python
+from eif import CaptureAttestation, Device, EIFFile, KeyPair, Location, imaging
+
+keypair = KeyPair.generate()
+
+attestation = CaptureAttestation(
+    device=Device(
+        make="Acme", model="Field-1", os="Android 15",
+        app_id="com.example.claims", app_version="2.3.0",
+    ),
+    location=Location(latitude="12.9716", longitude="77.5946", accuracy_m=8),
+    challenge="srv-nonce-7f3a",        # issued by your server, seconds before capture
+    session_id="claim-2026-0041",
+)
+
+sealed = EIFFile.capture(imaging.encode_png("damage.jpg"), attestation, keypair)
+sealed.save("damage.eif")
+```
+
+Verifying, with the signing key pinned:
+
+```python
+report = EIFFile.load("damage.eif").verify(expected_public_key=keypair.public_key)
+
+if not report["valid"]:
+    for tile in report["L2_cryptographic"]["altered_tiles"]:
+        print(f"altered region: {tile['bounds']}")
+```
+
+## The verification protocol
+
+| Level | Question | Network |
+|---|---|---|
+| **L1 Format** | Is this a well-formed EIF file? | offline |
+| **L2 Cryptographic** | Does the seal verify over this CAB, tree and image? If not, which tiles changed? | offline |
+| **L3 Temporal** | Are the timestamps internally coherent and plausible? | offline |
+| **L4 Provenance** | Is the chain of custody unbroken? | offline |
+| **L5 Device** | Is the signing key attested to real hardware? | online |
+
+Verification never raises on an invalid file; it returns a structured report. Each level is reported independently because the levels fail for different reasons and a relying party needs to make different decisions about each.
+
+## The challenge, and the attack it addresses
+
+Provenance systems that only record "a real camera took this photograph" are defeated by an attack that costs nothing: generate a fake image, display it on a screen, photograph the screen with a genuine camera. The capture is real, the signature is honest, and the content is fabricated.
+
+EIF's answer is the `challenge` field. Your server issues a nonce immediately before capture; the capture pipeline binds it into the Capture Attestation Block before signing. An image produced any other way cannot carry a fresh, unused, server-recognised nonce for a session you opened. This does not make recapture impossible — nothing in software does — but it moves the attack from "free and instant" to "requires real-time control of a device inside your session," which is a different economic proposition for a fraudster.
+
+Captures with no challenge are permitted and are honestly weaker. Treat them as a lower assurance tier.
+
+## Where this fits alongside C2PA and JPEG Trust
+
+EIF is not a competitor to [C2PA Content Credentials](https://c2pa.org) or [JPEG Trust (ISO/IEC 21617)](https://jpeg.org/jpegtrust/), and positioning it as one would be dishonest. Those efforts have the ecosystem — camera manufacturers, platforms, an ISO process — and they solve the problem they set out to solve: recording and travelling with a content history across a general-purpose media supply chain.
+
+EIF addresses a narrower case those systems do not target: **high-assurance evidence capture**, where the relying party controls the capture pipeline, the stakes justify a stricter model, and two specific requirements apply that general provenance does not meet — knowing *where* in the frame an image changed, and binding a capture to a session the relying party opened.
+
+An EIF file can carry a C2PA manifest as an annotation, and an EIF verifier can treat a valid Content Credential as one input among several. Interoperability notes are in the [specification repository](https://github.com/eif-format/specification/blob/main/spec/Interop.md).
+
+## Honest limitations
+
+Read these before you build anything on this.
+
+- **v1.0 handles losslessly-decodable images only (PNG).** JPEG decoding is not bit-exact across libraries, so tile hashes computed at capture would not reliably recompute on a verifier's machine. Rather than ship a structural integrity layer that produces false tamper reports, lossy profiles are deferred. This is the largest practical limitation and the first thing v1.1 must address.
+- **A signature proves who signed, not that the content is true.** EIF can tell you an image was sealed by a specific key at a specific time and has not changed since. It cannot tell you the adjuster photographed the right car.
+- **Software keys are only as good as the device.** The security of the whole scheme rests on the private key. This SDK generates software keys, which are appropriate for development. Production capture should sign inside a TEE, Secure Enclave, or StrongBox-backed keystore, and L5 exists to let a verifier check that.
+- **The provenance chain records what was recorded.** It detects alteration of the sequence. It cannot detect a handler who simply never appended an entry.
+- **No mobile SDK yet.** Android and iOS are the platforms this format actually needs. They are not built.
+- **The specification is v1.0 and has not been through independent security review.** If you find a flaw, please tell us — see [SECURITY.md](https://github.com/eif-format/eif-sdk/blob/main/SECURITY.md).
+
+## Repositories
+
+| Repository | Contents |
+|---|---|
+| [`specification`](https://github.com/eif-format/specification) | The format specification, JSON schemas, and shared test vectors |
+| [`eif-sdk`](https://github.com/eif-format/eif-sdk) | This reference implementation |
+| [`research`](https://github.com/eif-format/research) | Papers, datasets and methodology |
+
+## Contributing
+
+Independent implementations in other languages are the single most valuable contribution. A format with one implementation is a product; a format with several is a standard. See [CONTRIBUTING.md](https://github.com/eif-format/eif-sdk/blob/main/CONTRIBUTING.md).
+
+## Licence
+
+Apache License 2.0. See [LICENSE](https://github.com/eif-format/eif-sdk/blob/main/LICENSE) and [NOTICE](https://github.com/eif-format/eif-sdk/blob/main/NOTICE).
+
+The Apache 2.0 licence includes an express patent grant covering this implementation. Patent applications relating to the format have been filed in India; the licence grant applies to the contributed code as described in Section 3 of the licence.

eif_sdk-0.1.0/pyproject.toml

@@ -0,0 +1,68 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "eif-sdk"
+version = "0.1.0"
+description = "Reference implementation of the Evidence Integrity Framework (EIF) image provenance format"
+readme = "README.md"
+requires-python = ">=3.9"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE"]
+keywords = ["provenance", "authenticity", "forensics", "image", "cryptography", "c2pa"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Intended Audience :: Legal Industry",
+    "Programming Language :: Python :: 3",
+    "Topic :: Multimedia :: Graphics",
+    "Topic :: Security :: Cryptography",
+]
+dependencies = [
+    "cryptography>=41.0",
+    "Pillow>=10.0",
+]
+
+[project.optional-dependencies]
+dev = ["pytest>=7.4", "pytest-cov>=4.1", "ruff==0.14.4"]
+
+[project.urls]
+Homepage = "https://eif-format.org"
+Specification = "https://github.com/eif-format/specification"
+Source = "https://github.com/eif-format/eif-sdk"
+Issues = "https://github.com/eif-format/eif-sdk/issues"
+
+[project.scripts]
+eif = "eif.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+addopts = "-q"
+
+[tool.ruff]
+line-length = 100
+target-version = "py39"
+
+# Rules are selected explicitly rather than left to ruff's defaults. Defaults
+# change between ruff releases, which would mean an upstream release could fail
+# CI with no change to this repository. The version is pinned in the dev extra
+# for the same reason.
+[tool.ruff.lint]
+select = [
+    "E",    # pycodestyle errors
+    "F",    # pyflakes
+    "I",    # import sorting
+    "UP",   # pyupgrade
+    "B",    # bugbear
+    "BLE",  # blind except
+    "C4",   # comprehensions
+    "RUF",  # ruff-specific
+]
+
+[tool.ruff.lint.per-file-ignores]
+# Tests deliberately construct malformed input and assert on failure paths.
+"tests/*" = ["B011"]

eif_sdk-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+