actproof 0.3.3__tar.gz → 0.3.4__tar.gz

{actproof-0.3.3 → actproof-0.3.4}/CHANGELOG.md

@@ -16,6 +16,38 @@ release. Once 1.0.0 ships, semantic versioning will be strictly followed.
 - **v1.0.0** — API frozen.
 - **v2.0.0** — COSE_Sign1 + SCITT Transparent Statement bridge, once RFC 9943 publishes.
 
+## [0.3.4] — 2026-05-25
+
+**On-chain note in three encodings.** A receipt's anchor record now carries
+the exact ARC-2 transaction note as written to the ledger, rendered in
+UTF-8, hex, and base64. A receipt can be checked against a block explorer,
+an indexer API, or a byte-level tool without re-deriving the note from the
+manifest hash.
+
+### Added
+
+- **`OnChainNote`** — a frozen dataclass exported from the package, with
+  `utf8`, `hex`, and `base64` fields. **`on_chain_note_from_bytes`** is the
+  single builder that derives all three encodings from one note byte string.
+  Hex is lowercase without a `0x` prefix; base64 is standard-padded.
+- **`AnchorRecord.on_chain_note`** — a new optional field. `anchor_manifest`
+  populates it from the note bytes in every anchor mode. When a receipt is
+  read without the field, `__post_init__` reconstructs it losslessly from
+  `note_payload_b64` and the ARC-2 prefix, so receipts written by earlier
+  releases continue to read and verify unchanged.
+- Eight tests covering the three encodings, the builder, the reconstruction
+  path, and round-tripping through `receipt_to_dict` and `receipt_from_dict`.
+
+### Notes
+
+- Backward compatible. No breaking changes and no dependency changes.
+  Receipts written by 0.3.3 and earlier gain the reconstructed
+  `anchor.on_chain_note` block on read; receipts written by 0.3.4 carry it
+  as stored.
+- `note_payload_b64`, the prefix-stripped payload, is retained alongside the
+  new field. A decision on its long-term status is left to the receipt
+  format specification.
+
 ## [0.3.2] — 2026-05-19
 
 **License switch from MIT to Apache-2.0.** Forward-looking positioning of

{actproof-0.3.3 → actproof-0.3.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: actproof
-Version: 0.3.3
+Version: 0.3.4
 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
@@ -45,8 +45,6 @@ Requires-Dist: types-requests; extra == 'dev'
 Provides-Extra: docs
 Requires-Dist: mkdocs-material>=9.5; extra == 'docs'
 Requires-Dist: mkdocs>=1.6; extra == 'docs'
-Provides-Extra: events
-Requires-Dist: actproof-events>=1.4.0rc1; extra == 'events'
 Provides-Extra: gcp
 Requires-Dist: google-cloud-kms<4.0,>=2.0; extra == 'gcp'
 Requires-Dist: google-crc32c<2.0,>=1.5; extra == 'gcp'
@@ -59,6 +57,12 @@ public attestations. Canonical JSON (RFC 8785), RFC 3161 trusted timestamps,
 Algorand ARC-2 anchoring, independent verification by any party with a Python
 install.
 
+**Project site: [actproof.org](https://actproof.org).** The site explains
+the full ActProof stack and the reasoning behind it. ActProof Events
+defines the act, `actproof` proves the record, and applications consume
+both. Start there for the architecture. This README is the package
+reference.
+
 `actproof` produces cryptographic receipts that any third party can verify
 without trusting the issuing platform. A receipt binds: the record or act
 being documented (optionally classified against the `actproof-events`

{actproof-0.3.3 → actproof-0.3.4}/README.md

@@ -5,6 +5,12 @@ public attestations. Canonical JSON (RFC 8785), RFC 3161 trusted timestamps,
 Algorand ARC-2 anchoring, independent verification by any party with a Python
 install.
 
+**Project site: [actproof.org](https://actproof.org).** The site explains
+the full ActProof stack and the reasoning behind it. ActProof Events
+defines the act, `actproof` proves the record, and applications consume
+both. Start there for the architecture. This README is the package
+reference.
+
 `actproof` produces cryptographic receipts that any third party can verify
 without trusting the issuing platform. A receipt binds: the record or act
 being documented (optionally classified against the `actproof-events`

{actproof-0.3.3 → actproof-0.3.4}/actproof/__init__.py

@@ -6,7 +6,7 @@ actproof: anchor signed JSON manifests; verify anyone's anchored receipts.
 
 from __future__ import annotations
 
-__version__ = "0.3.3"
+__version__ = "0.3.4"
 
 
 # ─────────────────────────────────────────────────────────────────
@@ -80,6 +80,7 @@ from actproof.receipt import (
     ARC2_NOTE_FORMAT,
     AnchorRecord,
     IssuerEvidence,
+    OnChainNote,
     PlaintextRecipient,
     Receipt,
     ReceiptError,
@@ -88,6 +89,7 @@ from actproof.receipt import (
     build_receipt,
     issuer_evidence_from_dict,
     issuer_evidence_to_dict,
+    on_chain_note_from_bytes,
     read_issuer_evidence,
     read_receipt,
     receipt_from_dict,
@@ -179,6 +181,8 @@ __all__ = [
     "read_issuer_evidence", "write_issuer_evidence",
     "ALGORAND_MAINNET", "ALGORAND_TESTNET", "ALGORAND_BETANET",
     "ARC2_NOTE_FORMAT", "ARC2_DAPP_NAME", "ARC2_FORMAT_VERSION_JSON",
+    # receipt.py (v0.3.4): on-chain note in three encodings
+    "OnChainNote", "on_chain_note_from_bytes",
     # timestamp.py (v0.0.6)
     "TimestampAuthority", "TSAAttempt", "AcquisitionResult",
     "TimestampError", "acquire_timestamp_token",

{actproof-0.3.3 → actproof-0.3.4}/actproof/anchor.py

@@ -95,6 +95,7 @@ from actproof.receipt import (
     ARC2_FORMAT_VERSION_JSON,
     ARC2_NOTE_FORMAT,
     AnchorRecord,
+    on_chain_note_from_bytes,
 )
 from actproof.signers.interface import ALGORAND_MIN_FEE_MICROALGOS
 
@@ -518,6 +519,9 @@ def anchor_manifest(
     # commitment, the transaction is the carrier.
     note_bytes = build_note_bytes(manifest_hash, batching_profile)
     note_payload_b64 = base64.b64encode(note_bytes[len(_ARC2_PREFIX):]).decode("ascii")
+    # The full on-chain note in three encodings, all from this one
+    # note_bytes value, so the three encodings cannot drift apart.
+    on_chain_note = on_chain_note_from_bytes(note_bytes)
 
     network = _network_for_mode(mode)
 
@@ -536,6 +540,7 @@ def anchor_manifest(
             note_dapp_name=ARC2_DAPP_NAME,
             note_format_version=ARC2_FORMAT_VERSION_JSON,
             note_payload_b64=note_payload_b64,
+            on_chain_note=on_chain_note,
         )
 
     # DEMO and PRODUCTION: real submission.
@@ -600,4 +605,5 @@ def anchor_manifest(
         note_dapp_name=ARC2_DAPP_NAME,
         note_format_version=ARC2_FORMAT_VERSION_JSON,
         note_payload_b64=note_payload_b64,
+        on_chain_note=on_chain_note,
     )