What operational events does H33-74 attest for banks?

Each event emits an H33-74 proof at the moment it occurs: credit and lending decisions (underwriting, approval, denial, exception override, renewal); transfer authorizations (domestic, cross-border, correspondent banking, FX settlement); AML and sanctions screening determinations; fraud scoring outputs and human-override decisions; model governance events; account access and privilege changes; and reconciliation outcomes.

Is the H33-74 primitive different for banking than for other industries?

No. The primitive is unchanged; only the application context differs. It is the same portable 74-byte post-quantum evidence primitive used across every context — a 32-byte on-chain commitment plus a 42-byte compact receipt, signed under three independent post-quantum signature families.

Which banking regulations does H33-74 evidence support?

H33-74 produces evidence that supports requirements under SOX (Section 302 and 404 ICFR), DORA (ICT risk management, incident reporting, resilience testing), OSFI B-13, PCI-DSS, and FedRAMP. H33-74 produces the durable, verifiable evidence these frameworks call for; it does not by itself make an organization fully compliant.

How is a banking proof verified?

Proofs are verified directly by an independent offline verifier, with no contact back to H33. Auditors examining decisions years later verify them against the original PQ-signed proofs — which carry the policy version, signer, model version, and override chain — rather than against the deprecated system that produced them. No reconstruction and no vendor cooperation are required.

What happens to the evidence when a bank changes its core platform or anchoring chain?

The evidence remains and does not migrate. H33-74 receipts from an old platform stay independently verifiable after a core-platform change. If a cryptographic concern forces a chain change, the historical receipt corpus gets a new chain anchor in one batched commitment; replacing systems, vendors, cloud, database, or chain is normal lifecycle engineering work, not an existential project.

H33-74 for Banking

Related · tier-1 reading. For what a portable artifact actually is, see Portable Artifact.

This is H33-74 — the portable 74-byte post-quantum evidence primitive that produces and anchors operational proof — applied to banking. The primitive is unchanged; only the application context differs. Chief Compliance Officers, Chief Risk Officers, Chief Audit Executives at banks need operational evidence that survives infrastructure change, vendor turnover, and regulatory horizon shifts. H33-74 makes that evidence cryptographically verifiable and chain-portable by construction.

The asset may move. The evidence remains. Every approval, transfer, decision, and policy action your banking produces gets a 74-byte post-quantum-signed proof at the moment it happens. The proof outlives the system that produced it, the vendor that hosts it, and the chain it was anchored to.

What gets attested in banking

Each of the following operational events emits an H33-74 proof at the moment it occurs. The collection composes into the operational history that audit, compliance, and regulatory teams reconstruct from.

Credit and lending decisions: underwriting, approval, denial, exception override, renewal.
Transfer authorizations: domestic, cross-border, correspondent banking, FX settlement.
AML and sanctions screening determinations: customer onboarding, ongoing monitoring, SAR/CTR generation, watchlist hits.
Fraud scoring outputs and human-override decisions.
Model governance events: AI/ML model deployment, retraining, validation, deprecation.
Account access and privilege changes: privileged access grants, segregation enforcement.
Reconciliation outcomes: daily, settlement-window, period-end.

Regulatory pressure that already justifies this

Banking is regulated under frameworks whose audit horizons now extend past the lifetime of the systems and vendors holding the evidence. H33-74 produces evidence that survives that horizon:

SOX. Section 302 and 404 ICFR for publicly listed bank holding companies. See: SOX crosswalk
DORA. ICT risk management, incident reporting, resilience testing for EU financial entities. See: DORA crosswalk
OSFI B-13. Technology and cyber risk supervision for Canadian FRFIs. See: OSFI B-13 crosswalk
PCI-DSS. Cardholder data environment if card issuing or acquiring. See: PCI-DSS crosswalk
FedRAMP. Federal cloud environments for government banking and treasury work. See: FedRAMP crosswalk

Scenarios this changes

Bank changes core platform after a vendor acquisition

The new core platform inherits zero operational history. H33-74 receipts from the old platform remain independently verifiable. Auditors examining 2027 transfer decisions in 2031 verify them directly against the proofs, not the deprecated core.

A regulator requests credit decisions from four years ago

The bank produces the original PQ-signed proofs for each decision. The policy version, signer, model version, and override chain are all part of the proof. No reconstruction. No vendor cooperation required.

Cryptographic concern forces chain change for treasury anchoring

The bank adds a new chain anchor for the historical receipt corpus in one batched commitment. The treasury asset is re-issued on the new chain as normal tokenization work. The evidence does not migrate.

What survives versus what gets replaced

Survives

Every approval, decision, transfer, compliance check, and policy action your operation produced — independently verifiable forever.

Gets replaced as normal lifecycle work

The core systems, the vendor SaaS contracts, the cloud, the database product, the chain you anchored to. Each replacement is engineering work, not an existential project.

Banking operational history compounds in value. Five years of approvals, decisions, and compliance determinations are usually worth more than the systems that produced them. H33-74 keeps that history independent of the infrastructure.

The proof itself is the flagship H33-74 attestation applied here — see the general evidence patterns this vertical reuses: AI attestation and AI decision attestation. Where protection must be shown to stay true over time (continuous control evidence), HATS records that history on this same H33-74 substrate.

How to start

Three integration patterns, ordered by how invasive each is.

Pattern 1 — Receipt at the policy engine

The decision system (policy engine, approval workflow, AI scorer) emits an H33-74 proof for every decision at the moment it is made. No change to upstream systems. Auditors verify proofs directly.

Pattern 2 — Receipt at the system of record

Each system of record (treasury, claims, records, EHR) is wrapped so that committed transactions emit H33-74 proofs in addition to the existing audit log. Existing systems remain unchanged. Proofs become a parallel canonical record.

Pattern 3 — Receipt at the integration bus

Service mesh or integration bus intercepts cross-system events and emits H33-74 proofs. Highest reach, requires bus integration. Useful where systems-of-record cannot be modified.

See the architecture

The mechanism that makes banking evidence chain-portable.

Chain Portability What Gets Preserved