actproof 0.2.0__tar.gz → 0.3.2__tar.gz

{actproof-0.2.0 → actproof-0.3.2}/.gitignore

@@ -108,3 +108,5 @@ local_config.py
 scratch/
 # Local test receipts (these should be in tests/fixtures/ if intended to persist)
 *.receipt.local.json
+actproof-v*.zip
+APPLY_v*.md

{actproof-0.2.0 → actproof-0.3.2}/CHANGELOG.md

@@ -12,18 +12,122 @@ release. Once 1.0.0 ships, semantic versioning will be strictly followed.
 
 ### Planned
 
-- **v0.2.0** — `docs/` complete with three worked examples (NIS2 / EUDR / software release), GitHub Action wrapper `release-anchor.yml`, EU Trusted List chain validation for RFC 3161 tokens, stricter verifier semantics (PARTIAL state distinct from PASS), disclosure CLI subcommands (`actproof verify-disclosure`, `actproof issue-disclosure`).
-- **v0.3.0** — Cross-implementation conformance test suite landing.
+- **v0.4.0** — Pluggable anchor backend architecture. Generalize the chain-agnostic substrate (canonicalization, RFC 3161 timestamps, receipt format, verifier) into an `AnchorBackend` protocol with chain-specific implementations (Hedera Consensus Service, Stellar memo-hash, Bitcoin OP_RETURN, Ethereum). See `docs/ANCHOR_BACKENDS.md` for the design intent.
 - **v1.0.0** — API frozen.
 - **v2.0.0** — COSE_Sign1 + SCITT Transparent Statement bridge, once RFC 9943 publishes.
 
+## [0.3.2] — 2026-05-19
+
+**License switch from MIT to Apache-2.0.** Forward-looking positioning of
+actproof-py as verification infrastructure rather than a small utility
+library: Apache-2.0 provides an explicit patent grant suitable for
+standards-facing work and institutional adoption, while remaining as
+permissive as MIT for commercial and proprietary embedding.
+
+### Changed
+
+- **LICENSE file replaced** with the canonical Apache License 2.0 text.
+- **`pyproject.toml`** updated: license expression now `"Apache-2.0"`
+  with `license-files = ["LICENSE"]` per the modern Python packaging
+  guidance. Classifier updated to `License :: OSI Approved :: Apache
+  Software License`.
+- **SPDX headers** in all 27 source files (`actproof/*.py`,
+  `actproof/signers/*.py`, `tests/*.py`) changed from
+  `SPDX-License-Identifier: MIT` to `SPDX-License-Identifier: Apache-2.0`.
+- **README, DEPLOY, and STS standards documentation** updated to state
+  Apache-2.0 throughout.
+
+### Notes
+
+- Existing users on v0.3.1 (MIT) retain MIT rights for that release.
+  All v0.3.2 and later releases are governed by Apache-2.0.
+- Copyright remains "2026 Deyan Paroushev." No change to authorship or
+  contributor structure.
+- No API changes, no behavioural changes, no dependency changes. This is
+  a pure licensing release.
+
+## [0.3.1] — 2026-05-19
+
+**Packaging hotfix.** Resolves an internal contradiction in v0.3.0's
+dependency declaration that prevented installation in modern pip
+environments.
+
+### Fixed
+
+- **`cryptography` lower bound relaxed from `>=42.0` to `>=41.0`.** v0.3.0
+  declared both `tsp-client>=0.2.1,<0.3` and `cryptography>=42.0`, but
+  `tsp-client==0.2.1` (the only version in that range) transitively
+  requires `pyOpenSSL<24`, which in turn requires `cryptography<42`. The
+  two constraints could not be satisfied simultaneously by a strict pip
+  resolver, making v0.3.0 uninstallable in fresh environments. The
+  actual cryptography API surface used by
+  `actproof.signers.google_kms._extract_raw_ed25519_from_pem`
+  (`Ed25519PublicKey`, `load_pem_public_key`, `Encoding.Raw`,
+  `PublicFormat.Raw`) has been available since cryptography 2.6, so the
+  `>=42` floor was conservative rather than technical.
+
+### Notes
+
+- The upper bound `<46.0` is unchanged.
+- v0.4.0 will replace `tsp-client` with `rfc3161-client`, removing the
+  legacy `pyOpenSSL` cap entirely. The cryptography floor can then move
+  forward in step with modern releases.
+
+## [0.3.0] — 2026-05-17
+
+**Security hardening release.** Closes a transaction-validation gap present in v0.2.0. See `SECURITY.md` for the advisory.
+
+### Security
+
+- **`AlgorandSigner.validate_transaction` now rejects attack-vector fields unconditionally.** `rekey_to`, `close_remainder_to`, `group`, and `lease` are rejected on every transaction. v0.2.0 accepted these fields if the sender, receiver, amount, and note prefix passed validation; a `rekey_to=attacker` payment was therefore accepted as a benign-looking 0-ALGO self-payment. This is the same attack class that drained roughly 3.3 million USD across 25 accounts in the February 2023 MyAlgo wallet incident.
+- **Transaction type restricted to `PaymentTxn`.** v0.2.0 accepted any `algosdk.transaction.Transaction` subclass. v0.3.0 rejects `AssetTransferTxn`, `ApplicationCallTxn`, `KeyregTxn`, and any other non-payment type.
+- **Fee bounded and forced flat.** `txn.fee` must lie in `[ALGORAND_MIN_FEE_MICROALGOS, max_fee_microalgos]` (default 1000 microALGOs). `build_transaction` now forces `flat_fee=True` and `fee=1000` on the copy of `SuggestedParams` it passes to `PaymentTxn`, so per-byte fee rates returned by algod under congestion do not produce a transaction the signer would reject.
+- **Note size bounded.** New constant `ALGORAND_MAX_NOTE_BYTES = 1024` enforced explicitly by the signer before any KMS call.
+- **`GoogleKMSSigner`: fail-closed end-to-end integrity verification.** Every KMS call now requires `response.name == request.name`, `response.verified_data_crc32c is True`, `crc32c(signature) == response.signature_crc32c`, and `len(signature) == 64`. Same pattern for `get_public_key` (`response.name`, `pem_crc32c`). v0.2.0 used `hasattr(...)` guards that silently bypassed missing fields; v0.3.0 raises `RuntimeError` if any required field is missing or invalid. Implementation follows Google's recommended pattern documented at `cloud.google.com/kms/docs/data-integrity-guidelines`.
+- **`_assemble_signed_transaction` validates signature length.** Refuses to wrap a non-64-byte signature into a `SignedTransaction` (Ed25519 signatures are always 64 octets per RFC 8032).
+- **Release workflow now runs the test suite before publishing.** `.github/workflows/release.yml` adds a pytest gate plus wheel smoke-test job that the publish job depends on. A failing test now blocks the PyPI upload.
+
+### Changed
+
+- **`AlgorandSigner.__init__` accepts `allowed_note_prefixes` and `max_fee_microalgos` only.** The earlier v0.3.0 draft had also exposed `require_self_payment` and `require_zero_amount` as configurable booleans; these were removed because disabling them turned the signer into a general-purpose Algorand signing adapter, broader than its stated scope. The strict 0-ALGO self-payment shape is now a non-configurable invariant.
+- **`allowed_note_prefixes` accepts a single `bytes` value.** Passing `allowed_note_prefixes=b"quoruna/v1:"` now works without wrapping in a list. The constructor also raises a clearer `TypeError` when a non-bytes element is found.
+- **`__init_subclass__` walks the full MRO.** Forbidden method names inherited via mixin (`class BadSigner(RawSigningMixin, AlgorandSigner)`) are now caught at class-definition time, not only methods defined directly on the subclass.
+- **`validate_transaction` fails closed on missing `super().__init__()`.** Earlier drafts silently set defaults if a subclass forgot to call the base init. v0.3.0 raises `RuntimeError` listing every missing policy attribute.
+- **GCP KMS protection level wording.** Module and class docstrings no longer claim "HSM-backed" unconditionally. The signer accepts keys with any protection level (`SOFTWARE`, `HSM`, `HSM_SINGLE_TENANT`, `EXTERNAL`); operators who need HSM-residency guarantees should create the key version accordingly.
+- **`GoogleKMSSigner` without `[gcp]` deps.** Previously `actproof.signers.GoogleKMSSigner` was set to `None` if the GCP optional dependencies were missing, producing a confusing `TypeError: 'NoneType' object is not callable` on instantiation. v0.3.0 substitutes a stub subclass that raises a clear `RuntimeError` with the install command.
+- **`tsp-client` dependency loosened to `>=0.2.1,<0.3`.** Downstream applications that pull a slightly newer compatible patch release are no longer blocked by the exact-pin requirement.
+
+### Added
+
+- `ALGORAND_MIN_FEE_MICROALGOS`, `ALGORAND_DEFAULT_MAX_FEE_MICROALGOS`, `ALGORAND_MAX_NOTE_BYTES` constants on `actproof.signers.interface`.
+- New test module `tests/test_signers_v030_policy.py` with 52 tests covering the rejection paths above plus KMS response-verification fail-closed semantics. Includes a cryptographic-equivalence regression test that confirms v0.3.0 produces byte-identical signatures to v0.2.0 for the original strict-policy use case.
+- Two new tests in `tests/test_anchor.py` for `build_transaction`: confirms the resulting transaction carries `fee=1000` regardless of caller-supplied fee rate, and confirms the caller's `SuggestedParams` object is not mutated.
+- `SECURITY.md` documenting the v0.2.0 gap, the v0.3.0 fix, and the threat model. Now included in the sdist.
+- `docs/ANCHOR_BACKENDS.md` design note for v0.4.0 multi-chain anchor abstraction.
+- `docs/INTEGRATION.md` integration guide for downstream applications consuming actproof.
+- `actproof/py.typed` PEP 561 marker so downstream type-checkers honor inline annotations.
+
+### Migration from v0.2.0
+
+Existing callers using the strict actproof policy (default constructors, anchoring with `actproof:j{...}` notes, 0-ALGO self-payments, fee 1000) see no behavioural change: the signed bytes are byte-identical. Previously-accepted transactions carrying `rekey_to`, `close_remainder_to`, `group`, `lease`, fees above 1000 microALGOs, or notes longer than 1024 bytes are now rejected with `SignerValidationError`. Audit your transaction-construction code to confirm none of these fields should have been set; for a higher `fee` ceiling during network congestion, pass `max_fee_microalgos=<n>` to the signer constructor.
+
+Callers of any earlier v0.3.0 draft that used `require_self_payment=False` or `require_zero_amount=False` need to refactor: those kwargs were removed. If you need to sign other transaction shapes, write your own `AlgorandSigner` subclass and override `validate_transaction`.
+
+### Acknowledgements
+
+Independent review by ChatGPT (May 2026, three review rounds) flagged the original `rekey_to`/`close_remainder_to` gap, the KMS integrity-check weakening, the MRO walk gap, the configurable-policy footgun, the test-gating mistake, the flat-fee deployment issue, the release-workflow missing test gate, and seven additional release-quality items. All findings are addressed in this release.
+
 ## [0.2.0] — 2026-05-17
 
+Version bump for the initial PyPI publication path. See [0.1.0] notes below for the substrate API description; v0.2.0 was the version that actually shipped to PyPI (the 0.1.0 slot was skipped per immutable-release policy).
+
+## [0.1.0] — 2026-05-17
+
 **First PyPI release of `actproof`.** This is the inaugural published version of the substrate library under its canonical name. The library is installable via `pip install actproof`.
 
 ### Project history
 
-The code in this release was developed under the working name `openproof` on GitHub. The repository at `github.com/deyan-paroushev/openproof-py` was renamed to `github.com/deyan-paroushev/actproof-py` on 2026-05-17; the old URL auto-redirects to the new one. GitHub tags `v0.1.0` (initial public-API surface) and `v0.1.1` (additive schema v3 support) under the previous repository name are the development history of this code; this `v0.2.0` on PyPI is the first published release under the canonical name and supersedes both working-name tags.
+The code in this release was developed under the working name `openproof` on GitHub. The repository at `github.com/deyan-paroushev/openproof-py` was renamed to `github.com/deyan-paroushev/actproof-py` on 2026-05-17; the old URL auto-redirects to the new one. GitHub tags `v0.1.0` (initial public-API surface) and `v0.1.1` (additive schema v3 support) under the previous repository name are the development history of this code; this `v0.1.0` on PyPI is the first published release under the canonical name and supersedes both working-name tags.
 
 The PyPI namespace under `openproof` is unrelated to this project.
 

actproof-0.3.2/DEPLOY.md

@@ -0,0 +1,120 @@
+# Deployment
+
+This is the actproof-py v0.1.0 source tree, ready to push to
+`github.com/deyan-paroushev/actproof-py`.
+
+## What's inside
+
+```
+actproof-py/
+├── README.md                       Project README
+├── CHANGELOG.md                    Full v0.0.1 → v0.1.0 history
+├── LICENSE                         Apache-2.0
+├── DEPLOY.md                       This file
+├── pyproject.toml                  Hatchling build, dependencies pinned
+├── .gitignore
+├── actproof/                      Library source (~3,500 lines, 10 modules)
+│   ├── __init__.py
+│   ├── canonical.py                RFC 8785 JCS, strict-mode discipline
+│   ├── manifest.py                 Manifest envelope (issuer/claim/evidence/recipients)
+│   ├── catalogue.py                actproof-events loader + validator
+│   ├── receipt.py                  Public Receipt + private IssuerEvidence
+│   ├── timestamp.py                RFC 3161 with QTSP failover chain
+│   ├── anchor.py                   ARC-2 disclosed-mode notes on Algorand
+│   ├── signers/                    AlgorandSigner ABC + Mnemonic + GoogleKMS
+│   ├── verify.py                   Six-check end-to-end verification
+│   └── cli.py                      Click-based CLI (anchor / verify / validate)
+├── tests/                          11 test files, 443 tests, all passing
+│   └── ...
+└── docs/
+    └── STS-STANDARDS-APPLICATION.md   Maintainer application narrative
+```
+
+## First push to GitHub
+
+```bash
+cd actproof-py
+
+git init
+git add -A
+git commit -m "Initial release: actproof-py v0.1.0
+
+Library and CLI for anchoring signed JSON manifests to Algorand mainnet
+with RFC 3161 qualified timestamps, plus an independent verifier for
+anyone's anchored receipts.
+
+10 modules, 443 passing tests, Apache-2.0 licensed.
+
+Implements RFC 8785 JCS, RFC 3161 TSP, Algorand ARC-2 disclosed-mode
+notes, and tracks draft-ietf-scitt-architecture for the v2 COSE_Sign1
+bridge once RFC 9943 publishes."
+
+git branch -M main
+git remote add origin git@github.com:deyan-paroushev/actproof-py.git
+git push -u origin main
+
+git tag -a v0.1.0 -m "v0.1.0: first usable release"
+git push origin v0.1.0
+```
+
+## Local verification
+
+```bash
+python -m venv .venv
+. .venv/bin/activate
+pip install -e ".[dev,gcp]"
+
+# Sanity checks
+actproof --version              # actproof, version 0.1.0
+python -c "import actproof; print(actproof.__version__)"
+
+# Full test suite — expect 443 passed (with ACTPROOF_EVENTS_ROOT set, see Notes below)
+ACTPROOF_EVENTS_ROOT=/path/to/actproof-events python -m pytest tests/ -q
+
+# CLI help
+actproof --help
+actproof anchor --help
+actproof verify --help
+actproof validate --help
+```
+
+## Notes for the catalogue
+
+Several tests and the `actproof validate` command need the
+actproof-events catalogue to be present somewhere resolvable.
+
+The library (CLI flag, env var, error):
+
+1. The `--catalogue` CLI flag (a path to the `acts/` directory)
+2. The `ACTPROOF_CATALOGUE_PATH` environment variable
+3. Otherwise raises `CatalogueLoadError`
+
+The test suite (env var, sibling repo, skip):
+
+1. The `ACTPROOF_EVENTS_ROOT` environment variable (a path to the
+   actproof-events repo root, not the `acts/` directory)
+2. Falls back to `../actproof-events` as a sibling of this repo
+3. Tests that need the real catalogue skip cleanly if neither is
+   available; tests using synthetic `tmp_path` catalogues run regardless
+
+For local development against `github.com/deyan-paroushev/actproof-events`:
+
+```bash
+# Clone as a sibling of this repo
+git clone https://github.com/deyan-paroushev/actproof-events.git ../actproof-events
+
+# Or set the env vars explicitly
+export ACTPROOF_EVENTS_ROOT=/path/to/actproof-events                  # tests
+export ACTPROOF_CATALOGUE_PATH=$ACTPROOF_EVENTS_ROOT/catalogue/acts   # library/CLI
+```
+
+## STS Standards Network application
+
+The maintainer's statement of practice is at
+`docs/STS-STANDARDS-APPLICATION.md`. It is written against the four
+sections of the Sovereign Tech Standards Network application form
+(maintainer profile, standards relation, twelve-month plan, track
+record) plus a conflicts-and-disclosures appendix.
+
+It is structured to be read by the application reviewer; nothing in it
+is load-bearing for the library itself.

actproof-0.3.2/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 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 Support. 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 support.
+
+   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 2026 Deyan Paroushev
+
+   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.

{actproof-0.2.0 → actproof-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: actproof
-Version: 0.2.0
+Version: 0.3.2
 Summary: Verifiable receipts of regulated acts. Canonical JSON (RFC 8785), RFC 3161 trusted timestamps, Algorand ARC-2 anchoring, independent verification.
 Project-URL: Homepage, https://github.com/deyan-paroushev/actproof-py
 Project-URL: Documentation, https://github.com/deyan-paroushev/actproof-py/tree/main/docs
@@ -11,34 +11,14 @@ Project-URL: Security, https://github.com/deyan-paroushev/actproof-py/blob/main/
 Project-URL: Catalogue, https://github.com/deyan-paroushev/actproof-events
 Author-email: Deyan Paroushev <deyan@advisa.tech>
 Maintainer-email: Deyan Paroushev <deyan@advisa.tech>
-License: MIT License
-        
-        Copyright (c) 2026 Deyan Paroushev
-        
-        Permission is hereby granted, free of charge, to any person obtaining a copy
-        of this software and associated documentation files (the "Software"), to deal
-        in the Software without restriction, including without limitation the rights
-        to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-        copies of the Software, and to permit persons to whom the Software is
-        furnished to do so, subject to the following conditions:
-        
-        The above copyright notice and this permission notice shall be included in all
-        copies or substantial portions of the Software.
-        
-        THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-        IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-        FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-        AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-        LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-        OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-        SOFTWARE.
+License-Expression: Apache-2.0
 License-File: LICENSE
 Keywords: algorand,attestation,canonical-json,compliance,evidence,governance,receipts,rfc-3161,rfc-8785,scitt,timestamping,transparency,verification
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
 Classifier: Intended Audience :: Information Technology
 Classifier: Intended Audience :: Legal Industry
-Classifier: License :: OSI Approved :: MIT License
+Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Operating System :: OS Independent
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
@@ -50,11 +30,11 @@ Classifier: Topic :: System :: Archiving
 Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Requires-Dist: click<9.0,>=8.1
-Requires-Dist: cryptography<46.0,>=42.0
+Requires-Dist: cryptography<46.0,>=41.0
 Requires-Dist: py-algorand-sdk<3.0,>=2.6.1
 Requires-Dist: requests<3.0,>=2.32.0
 Requires-Dist: rfc8785<0.2,>=0.1.4
-Requires-Dist: tsp-client==0.2.1
+Requires-Dist: tsp-client<0.3,>=0.2.1
 Provides-Extra: dev
 Requires-Dist: mypy>=1.10; extra == 'dev'
 Requires-Dist: pytest-asyncio>=0.23; extra == 'dev'
@@ -72,17 +52,18 @@ Description-Content-Type: text/markdown
 
 # actproof
 
-Verifiable receipts of regulated acts. Canonical JSON (RFC 8785), RFC 3161
-trusted timestamps, Algorand ARC-2 anchoring, independent verification by
-any party with a Python install.
+Verifiable evidence receipts for institutional records, regulated acts, and
+public attestations. Canonical JSON (RFC 8785), RFC 3161 trusted timestamps,
+Algorand ARC-2 anchoring, independent verification by any party with a Python
+install.
 
 `actproof` produces cryptographic receipts that any third party can verify
-without trusting the issuing platform. A receipt binds: the regulated act
-being recorded (from the `actproof-events` catalogue), the canonical JSON
-of the issuer's evidence, a qualified timestamp from a trusted timestamp
-authority, and a transaction on the Algorand public ledger that carries
-the same hash. The verifier reproduces the bytes locally and confirms each
-binding.
+without trusting the issuing platform. A receipt binds: the record or act
+being documented (optionally classified against the `actproof-events`
+catalogue for regulated acts), the canonical JSON of the issuer's evidence,
+a qualified timestamp from a trusted timestamp authority, and a transaction
+on the Algorand public ledger that carries the same hash. The verifier
+reproduces the bytes locally and confirms each binding.
 
 ## What actproof does not claim
 
@@ -278,18 +259,91 @@ actproof composes five published standards rather than inventing new ones:
   v2 parser when COSE_Sign1 + SCITT Transparent Statement becomes
   standardised.
 
-## What's NOT in v0.1.0
+## Independent use outside Quoruna
+
+`actproof` is a standalone Python library. It does not require Quoruna, an
+account, a hosted service, or any vendor trust. The intended use cases:
+
+* **Regulated industries.** Compliance evidence with verifiable timestamps:
+  pharma batch records, financial reporting attestations, NIS2 incident
+  reports, EUDR due-diligence statements, AI Act risk assessments.
+* **Civil society and journalism.** Verifiable provenance of reporting,
+  research outputs, and document releases without a trusted intermediary.
+* **Academic research.** Pre-registration of analysis plans, anchored
+  research artifacts, reproducibility receipts.
+* **Public-sector records.** Public decisions, council resolutions,
+  procurement evidence, transparency anchors.
+* **Other receipt and attestation systems.** Any application that today
+  emits "trust us" PDFs can emit an actproof receipt instead and let the
+  recipient verify without contacting the issuer.
+
+Quoruna is one consuming application. It is not the only intended
+consumer. The library API is independent of any particular product or
+hosted service.
+
+## API stability
+
+The package currently exposes a deliberately large API surface to let
+adopters work at whatever level suits them. Before the v1.0 release,
+the following discipline applies:
+
+* **Stable.** `canonicalize`, `hash_canonical`, `hash_canonical_hex`,
+  `build_manifest`, `manifest_to_dict`, `manifest_from_dict`,
+  `hash_manifest`, `hash_manifest_hex`, `Receipt`, `read_receipt`,
+  `write_receipt`, `verify_receipt`, `CheckResult`, `VerificationResult`.
+  These will not break between minor versions before v1.0.
+* **Experimental.** `Catalogue`, `validate_manifest`, RFC 3161 TSA
+  chain configuration, the `AnchorMode` enum, and the signer
+  abstraction. Subject to refinement before v1.0.
+* **Internal-but-exported.** Constants like `IJSON_MAX_SAFE_INT`,
+  `ARC2_NOTE_FORMAT`, and `SCHEMA_DISCRIMINATOR_V3`. Available for
+  power users but may change.
+
+The full list is in `actproof/__init__.py`. v1.0.0 will declare the final
+stable surface and freeze it under semantic versioning.
+
+## Roadmap
+
+* **v0.4.0** — Pluggable anchor backend architecture (`AnchorBackend`
+  Protocol). Algorand stays as the production backend; the protocol
+  abstraction makes Hedera Consensus Service, Stellar memo-hash, Bitcoin
+  OP_RETURN, and Ethereum implementations feasible without changes to
+  the canonicalisation, receipt, or verifier code. Also migrates off
+  `tsp-client` 0.2.1 onto `rfc3161-client` (Trail of Bits) to remove
+  the legacy pyOpenSSL cap.
+* **v0.5.0** — Receipt profile registry. Explicit named profiles
+  (`actproof-jcs-v1`, `actproof-algorand-arc2-v1`, `actproof-rfc3161-v1`)
+  and a stable verifier dispatch surface for adopters.
+* **v1.0.0** — Stable API frozen. Conformance test vectors finalised.
+* **v2.0.0** — COSE_Sign1 + SCITT Transparent Statement bridge once
+  RFC 9943 publishes.
+
+## What actproof does NOT yet ship
 
 * **EU Trusted List chain validation** for RFC 3161 tokens. The current
   verifier checks the token is well-formed and self-consistent; full
-  chain validation against EUTL is v0.2.x.
-* **Conformance test vectors** for cross-implementation interop. The
-  conformance suite lands in v0.3.0.
-* **GitHub Action wrapper** for one-call anchoring from a CI step. Lands
-  in v0.2.0.
-* **Worked examples** for NIS2, EUDR, and software-release use cases.
-  Land in v0.2.0.
+  chain validation against EUTL is on the v0.5.x roadmap.
+* **GitHub Action wrapper** for one-call anchoring from a CI step.
+* **Worked end-to-end examples** for NIS2, EUDR, AI Act, and
+  software-release use cases. Conformance vectors and example receipts
+  land in `examples/` and `docs/CONFORMANCE_VECTORS.md` in v0.3.x.
 
 ## License
 
-MIT. The actproof-events catalogue is CC0 / Apache-2.0.
+Apache-2.0. See `LICENSE`. The `actproof-events` catalogue (sibling
+repository) is CC0 / Apache-2.0.
+
+## Why Apache-2.0
+
+`actproof` is intended as reusable verification infrastructure. Apache-2.0
+provides:
+
+* The same broad permission to embed in commercial or proprietary work
+  as MIT.
+* An explicit contributor patent licence (Section 3 of the licence text),
+  which matters for cryptographic and protocol code.
+* A clearer legal posture for institutional and public-sector adopters.
+
+If you previously consumed `actproof <= 0.3.1` under MIT, those releases
+remain available on PyPI under MIT. All `actproof >= 0.3.2` releases are
+governed by Apache-2.0.