What treasury events does H33-74 attest?

Each of these emits a 74-byte proof at the moment of execution: transfer authorizations, FX executions, liquidity decisions, reconciliation outcomes, signer changes, counterparty changes, and policy version changes.

Is H33-74 changed for treasury operations?

No. H33-74 is the same portable post-quantum evidence primitive here as everywhere else. Only the application context differs: the receipt records the source and destination, amount, policy in effect, signer chain, and approval flow of a treasury action.

Which regulations does the evidence map to?

H33-74 produces evidence that maps to SOX 302/404, DORA, OSFI B-13, and AML/sanctions screening. It produces supporting evidence; it does not by itself make an entity compliant.

H33-74 for Treasury Operations

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

This is H33-74 evidence applied to treasury operations. CFOs, Treasurers, Chief Compliance Officers, and Heads of Treasury Operations need cryptographic evidence of every treasury action. H33-74 produces/anchors that evidence as a portable post-quantum proof at the moment each action occurs. The primitive is unchanged — only the application context (treasury operations) differs.

Every treasury action should be independently auditable years later, even if the treasury system, the bank, and the chain have all changed. H33-74 produces one cryptographically verifiable proof per treasury operations action. The collection of proofs is the operational history. The history survives the systems that produced it.

What gets attested in treasury operations

Each of the following treasury events emits an H33-74 proof at the moment of execution:

Transfer authorizations: the source and destination, the amount, the policy in effect, the signer chain, the approval flow taken.
FX executions: the currency pair, the rate, the venue, the policy applied, the trader and risk signer.
Liquidity decisions: cash positioning, sweep allocations, money market placements with the rationale.
Reconciliation outcomes: source-of-truth comparisons, variance thresholds, exception handling decisions.
Signer changes: addition, removal, threshold changes with the governance approval.
Counterparty changes: addition to or removal from approved counterparty lists with the diligence basis.
Policy version changes: each treasury policy update is itself an event under a meta-policy.

Workflow

1. Treasury action initiated

A treasury system produces a decision (transfer, FX, liquidity placement). The decision context is hashed to a 32-byte commitment.

2. Receipt emitted

The H33-74 substrate produces the 74-byte receipt. The receipt is the canonical audit record for that action.

3. Anchor scheduled

Anchoring strategy follows the operator's compliance and audit policy. High-value transfers may be anchored immediately. Routine cash movements may be batched.

4. Audit on demand

An auditor verifying a transfer from years ago retrieves the receipt and verifies it independently. The original signer chain, policy version, and approval flow are all in the receipt.

Regulatory anchoring

This use case lives under specific regulatory frameworks. H33-74 produces evidence that maps to each:

SOX 302 / 404. Transfer authorizations are ICFR controls. See the crosswalk.
DORA. ICT risk management for treasury platforms in EU financial entities. See the crosswalk.
OSFI B-13. Canadian FRFI treasury operations. See the crosswalk.
AML / sanctions. Transfer screening determinations emit receipts attestable to regulators.

What survives infrastructure change

Survives

Every treasury operations action your operation produced — independently verifiable forever.

Gets replaced as lifecycle work

The systems, the vendor SaaS contracts, the chains you anchored to.

The treasury operations evidence is chain-portable. When the underlying systems change, the treasury operations record carries forward as PQ-signed proofs anchored to whichever chain is appropriate at the time.

None of this redefines the primitive: H33-74 produces/anchors the same portable 74-byte post-quantum receipt for a treasury action that it does for any other event. How anyone independently checks a receipt — recompute the commitment, verify the signatures, confirm the anchor, with H33 not in the loop — is described under Verification.

See the architecture

Chain portability is the mechanism that makes treasury operations evidence infrastructure-independent.

Chain Portability What Gets Preserved