Ledger Transaction

• CURIE: gmeow:LedgerTransaction
• IRI: https://blackcatinformatics.ca/gmeow/LedgerTransaction
• Category: class
• Defined by: gmeow:slices/attestation
• Box roles: CBox role, TBox role (What is this?)

A transaction recorded on a distributed ledger or blockchain — the information-object representation of the payload, not the on-chain bytes themselves.

Structure

Subclass of: gmeow:InformationObject

Practical Pattern

Use gmeow:LedgerTransaction as a specialized kind of gmeow:InformationObject. Add statement metadata or a standpoint when the assertion needs provenance, confidence, or vantage.

Common Companion Terms

gmeow:InformationObject

Usage Advice

Use when

• Use to model a ledger or blockchain transaction as evidence backing an attestation — the information-object view of the payload, when its hash, finality, and confirmation depth matter.

Avoid when

• Avoid reading ledger inclusion as real-world truth — blockchain inclusion proves ledger inclusion under chain rules, NOT correctness (module boundaries) — and avoid it for the raw on-chain bytes or for transparency-log evidence (gmeow:TransparencyLogEntry).

How to use

• Mint the transaction with gmeow:transactionHash (the EL minimum), record gmeow:finalityStatus, gmeow:confirmationDepth, and gmeow:ledgerInclusionProof, and locate it on its gmeow:BlockchainNetwork / gmeow:Block; chain-finality checks run in the solver layer (Principle 12).

Examples

• ex:tx1 a gmeow:LedgerTransaction; gmeow:transactionHash "0xabc..."; gmeow:finalityStatus gmeow:finalityStatusFinalized.