GravityBTC

Contents

The Informational Boundary of a Bitcoin Transaction

**Research ID:** `RESEARCH-20260823-004`

**Research Domain:** Bitcoin Native

**Research Status:** Finding established

**Finding Result:** `SUPPORTED_WITHIN_GOVERNED_SAMPLE`

**Primary Bitcoin Evidence Source:** Gravity's locally operated validating Bitcoin node

**Evidence Authority:** Independently verifiable Bitcoin consensus data, acquired and validated through Gravity's controlled local node environment

Executive Assessment

Gravity conducted a governed Bitcoin-native investigation of 100 non-block-reward transactions selected deterministically from 10 completed Bitcoin blocks.

The investigation asked:

> **What information does a Bitcoin transaction itself record about a settlement, and what information about the meaning of that settlement is absent from the Bitcoin transaction record?**

The study found that the examined Bitcoin records established substantial protocol-level information about transaction state and mechanics. The records preserved transaction identity, referenced inputs, created outputs and values, locking-script information, transaction structure, locktime, size, virtual size, weight, and block-inclusion context. Referenced prior outputs also permitted deterministic derivation of input values, transaction fees, and feerates where the required Bitcoin-native evidence was available.

At the same time, the examined protocol-native transaction records did not contain standardized fields establishing human identity, payer or payee role, invoice identity, commercial purpose, goods or services, human intent, external contractual meaning, or legal responsibility.

Gravity therefore finds, within the governed sample:

> **Bitcoin provides strong evidence of its own transaction state and mechanics. The external human, commercial, contractual, and legal meaning associated with that transaction remains a separate evidentiary layer unless independently supplied and verified.**

This finding does not establish that external context was absent.

It establishes only that the examined Bitcoin transaction records did not themselves establish that external context.

### Settlement Terminology

For purposes of this investigation, **settlement** is used only in a bounded Bitcoin-native sense: confirmed transaction inclusion and the resulting Bitcoin spend-state transition.

The term does **not** establish, by itself, that an external commercial obligation, invoice, contract, legal duty, ownership claim, or accounting treatment was satisfied.

That distinction governs the interpretation of this paper.

I. Research Question

The investigation asked:

> **What information does a Bitcoin transaction itself record about a settlement, and what information about the meaning of that settlement is absent from the Bitcoin transaction record?**

The thesis placed under examination was:

> Bitcoin records transaction and settlement mechanics with precision but does not itself record much of the human meaning surrounding that settlement.

The research question was established before capture.

This prevented the investigation from changing its objective in response to evidence observed after collection began.

II. Scope

The investigation was intentionally narrow.

It examined Bitcoin-native transaction evidence obtained from Gravity's own validating Bitcoin node.

The governed sample consisted of:

The sampling method was selected for **deterministic reproducibility**, not for statistical estimation of the entire Bitcoin transaction population.

Accordingly, numerical observations concerning fees, feerates, transaction sizes, input counts, output counts, and script classifications are descriptive properties of the governed sample. They are not presented as Bitcoin-wide population estimates.

The investigation was not designed to:

III. Evidence Authority

**Primary Bitcoin Evidence Source:** Gravity's locally operated validating Bitcoin node.

**Evidence Authority:** Independently verifiable Bitcoin consensus data, acquired and validated through Gravity's controlled local node environment.

The capture interface was `bitcoin-cli`.

External network sources were excluded from the evidentiary basis.

The research design explicitly prohibited:

The investigation therefore did not ask what external systems, businesses, wallets, investigators, counterparties, or other observers might know about a transaction.

It asked a narrower question:

> **What does the examined protocol-native Bitcoin transaction evidence itself establish?**

That boundary is essential.

IV. Evidence Architecture

Gravity separated the investigation into distinct evidentiary layers.

### A. Primary Bitcoin Evidence

Primary evidence consisted of:

Primary evidence was preserved before decoding.

This prevents decoded or interpreted representations from silently replacing the source material from which they were derived.

### B. Decoded Representation

The permitted decoded layer contained representations of:

Decoded representations remained subordinate to the preserved primary Bitcoin evidence.

Decoding did not expand the authority of the source.

### C. Derived Evidence

The investigation permitted deterministic derivation of:

Derived values were not treated as independent observations.

Their provenance remained tied to the Bitcoin evidence from which they were calculated.

V. Protocol-Native Evidence and Associated Context

A central distinction of this investigation is the difference between **Bitcoin-native evidence** and information merely associated with a Bitcoin transaction.

For purposes of this study, protocol-native evidence includes the transaction and block evidence examined directly from Gravity's Bitcoin node, together with deterministic representations and derivations whose provenance remains traceable to that evidence.

External information can be associated with the same transaction without becoming part of the protocol-native transaction record.

Examples may include:

Such information may be valid, important, and independently verifiable.

But its authority comes from its own evidence source.

A TXID does not transform every external claim attached to it into a Bitcoin-native fact.

The evidentiary rule is therefore:

> **Association with a Bitcoin transaction does not automatically inherit Bitcoin's evidentiary authority.**

VI. Methodological Controls

The investigation operated under explicit methodological invariants:

These controls prevent evidentiary-layer collapse.

Without them, an examiner could begin with a Bitcoin transaction, add outside assumptions or labels, and later describe the combined result as though every part of it originated from Bitcoin.

Gravity prohibits that transformation.

VII. Validation

The captured evidence passed the study's validation process.

Validation recorded successful checks for:

The validated corpus contained:

No validation errors were recorded.

The recorded SHA-256 integrity values matched the corresponding evidence represented in the study's manifests.

The research finding therefore rests on a validated evidence chain rather than on an unverified decode or narrative interpretation.

VIII. What the Examined Bitcoin Records Established

Across the governed sample, the transaction records exposed substantial machine-verifiable structure.

Examined input representations contained:

Examined output representations contained:

The decoded `scriptPubKey` representation included:

An address representation in this decoded layer must not be interpreted as a verified human identity.

Likewise, an output destination does not by itself establish that the associated human role is “payee,” and an input does not by itself establish a human “payer.”

Those are semantic claims requiring separate evidence.

Cryptographic control, authorization, or satisfaction of a Bitcoin spending condition is also not equivalent to verified human identity, beneficial ownership, legal capacity, or business role.

IX. Observed Structural Characteristics

The sample contained the following output-script classifications:

Across the 100 examined transactions there were:

The decoded transaction representations also contained or supported:

Bitcoin's transaction record is therefore not sparse.

It preserves considerable technical and cryptographic structure.

The important question is not whether Bitcoin records information.

It plainly does.

The question is **which class of information it establishes**.

X. Derived Transaction Mechanics

Because referenced prior-output evidence was preserved, the investigation could deterministically derive transaction economics without importing external semantic meaning.

Across all 100 governed transactions, fee and feerate calculations were available.

Within this sample, observed transaction fees ranged approximately from:

Observed feerates ranged approximately from:

These figures describe only the governed sample.

They are not estimates of Bitcoin-wide transaction economics.

More importantly, the calculations demonstrate an evidentiary distinction:

> **Increasing technical knowledge of a transaction does not automatically produce increasing knowledge of its external human meaning.**

A verifier may calculate a transaction fee.

That does not establish why the transaction occurred.

A verifier may resolve the outputs.

That does not establish an external contract.

A verifier may establish confirmed inclusion.

That does not establish which commercial obligation, if any, was satisfied.

XI. Structural Variation

The governed transactions varied in structure.

Input counts ranged from:

Output counts ranged from:

Virtual transaction size ranged from:

These observations demonstrate variation within the governed sample.

They do not establish the distribution of those characteristics across Bitcoin generally.

XII. The Semantic Boundary

Gravity separately examined whether the protocol-native transaction records contained standardized fields establishing external human meaning.

The examined semantic categories included:

Within the governed sample:

> **No protocol-native standardized field matching those semantic categories was found.**

This does not mean the transactions had no external meaning.

A transaction may have been associated with:

The investigation did not determine which of those possibilities applied.

That uncertainty is itself part of the result.

The transaction record alone did not establish those external classifications.

XIII. Spending Conditions and External Contracts

This investigation distinguishes Bitcoin spending conditions from external contractual meaning.

Bitcoin can establish cryptographic conditions governing when particular outputs may be spent.

Those conditions are Bitcoin-native facts.

They do not automatically establish the full external legal or commercial agreement that may exist around them.

Accordingly:

> **A cryptographic spending condition is not, by itself, proof of an external legal contract, contractual satisfaction, or legal responsibility.**

An external agreement may reference a Bitcoin transaction.

A Bitcoin transaction may participate in satisfying an agreement.

But the authority for the external agreement remains distinct from the authority of the transaction record.

XIV. Arbitrary Data and Meaning

No `nulldata` outputs occurred within the governed sample.

The study therefore does not claim that arbitrary-data-bearing outputs were absent from Bitcoin generally.

Instead, it establishes a broader evidentiary rule:

> **Bitcoin can preserve bytes associated with meaning without itself becoming the authority for the external meaning of those bytes.**

Where arbitrary bytes are preserved, Bitcoin can provide evidence that those bytes were committed to or included through the relevant transaction mechanism.

That fact does not automatically establish:

Preservation and interpretation are separate evidentiary operations.

XV. Cryptographic Authorization Is Not Human Identity

Bitcoin can provide evidence that transaction spending conditions were satisfied according to its protocol rules.

That is powerful evidence.

But a cryptographic key, signature, script satisfaction, or spend does not automatically establish:

Therefore:

> **Cryptographic authorization is not equivalent to verified human identity.**

Where identity matters, the identity claim requires its own provenance and authority.

XVI. Governed Finding

The study's governed finding remains:

> **The examined Bitcoin records preserve precise transaction mechanics—including transaction identity, referenced inputs, outputs and values, locking-script information, transaction structure, block inclusion, and sufficient Bitcoin-native relationships to derive transaction fees and feerates. Within the examined protocol-native record, Bitcoin did not provide standardized fields establishing human identity, payer/payee role, invoice identity, commercial purpose, goods or services, human intent, external contractual meaning, or legal responsibility.**

**Finding Result:** `SUPPORTED_WITHIN_GOVERNED_SAMPLE`

The adversarial review does not require reversal of this finding.

It requires precision around its boundaries.

XVII. Gravity Institutional Interpretation

Gravity does not interpret this study to mean that Bitcoin “lacks meaning.”

That would be inaccurate.

Bitcoin establishes substantial meaning within its own protocol domain.

The examined evidence establishes cryptographic relationships, spend conditions, transaction structure, ordering, values, and confirmed inclusion.

The institutional distinction is narrower:

> **Bitcoin provides exceptionally strong evidence of its own transaction state. Claims about who the parties are, why the transfer occurred, what external obligation it represented, or what legal or commercial consequence followed require evidence whose authority originates outside the transaction record.**

This is the boundary between **Bitcoin-native fact** and **external semantic claim**.

A verifier must preserve that boundary.

The verifier must know when the Bitcoin record ends and another evidentiary authority begins.

XVIII. Reliability Assessment

The finding receives strong evidentiary support within its declared scope because:

The conclusion is therefore strong with respect to the evidence class actually examined.

It is not an unrestricted claim about every Bitcoin transaction, every Bitcoin application, every higher-layer system, or every form of context that may exist outside the transaction record.

XIX. Limitations

The investigation retains the following limitations:

1. The sample consisted of 100 non-block-reward transactions drawn from 10 completed blocks.

2. The selection process was deterministic for reproducibility rather than statistically representative sampling.

3. The finding is bounded to the evidence classes and methodology declared before capture.

4. The study does not claim that every possible Bitcoin transaction has identical structure.

5. Numerical fee, feerate, structural, and script observations describe the governed sample and are not population estimates.

6. No `nulldata` output appeared in the sample; no Bitcoin-wide prevalence conclusion may be drawn from that absence.

7. Absence of standardized semantic fields must not be confused with absence of external context.

8. Cryptographic authorization must not be equated automatically with verified identity, legal ownership, or external legal authority.

9. Bitcoin-native spending conditions must not be equated automatically with complete external contractual meaning.

10. No exchange, block explorer, wallet attribution, entity attribution, clustering heuristic, or outside semantic enrichment contributed to the finding.

These limitations constrain the authority of the finding.

They are not retrospective disclaimers.

XX. Verification Chain

The investigation's evidence chain was:

**Serialized Bitcoin evidence**

→ **SHA-256 integrity manifests**

→ **deterministic decoding**

→ **prevout provenance validation**

→ **derivation recomputation**

→ **Bitcoin-record boundary analysis**

→ **governed research finding**

Principal record hashes:

**Research Plan**

`aec6cce507863e696aea6d08423a08ed4c9c4b05a57cda8676d3424c838782b7`

**Validation Record**

`b12ef8de8426b73e4d242219debf5f7f7029ef00668aac1116e5b1591aa8aac4`

**Analysis Record**

`8754e1b514330fdfd009148c5fdb7181ddac1d1dd99ffae4397c9334dae22568`

**Research Finding**

`9a6f388729efebd332b393eca29aec79ffec6013cc7e166dbb00ee41827c9741`

These hashes bind the investigation to the governed research records from which the finding was produced.

XXI. Final Research Conclusion

Study `RESEARCH-20260823-004` supports the following conclusion within its governed scope:

> **The examined Bitcoin records provided strong, reproducible evidence of transaction identity, transaction structure, referenced inputs, created outputs, values, locking conditions, block inclusion, and deterministically derived transaction mechanics. They did not themselves establish standardized external human, commercial, contractual, or legal meaning for those transactions.**

The distinction is not between a Bitcoin transaction having information and having none.

The distinction is between **different authorities of information**.

Bitcoin can establish facts within its protocol domain with exceptional precision.

External evidence can establish additional facts about people, obligations, agreements, business purpose, and legal consequence.

Those evidence classes may refer to the same event.

They must not be silently merged.

The central institutional conclusion is therefore:

> **Bitcoin can preserve evidence associated with meaning without itself becoming the authority for that meaning.**

And the corresponding verification principle is:

> **A verifier must preserve the boundary between what Bitcoin establishes and what another source merely claims about it.**

**Gravity Research Investigation**

**Research ID:** `RESEARCH-20260823-004`

**Domain:** `BITCOIN_NATIVE`

**Finding:** `SUPPORTED_WITHIN_GOVERNED_SAMPLE`

Publication Verification

Publisher
GravityBTC
Publication ID
PUB-20260825-THE_INFORMATIONAL_BOUNDARY_OF_A_BITCOIN_TRANSACTION
Verification Record
Open verification record
SHA256
Recorded in the publication verification record
Standard
Gravity Publication Authority Pipeline v1.0