Bitcoin Transaction Discovery by Repurposing nLockTime

Summary

The Lockchain Protocol uses Bitcoin transactions’ mandatory four-byte nLockTime field as a compact metadata header for a meta-protocol. By restricting encoded values to an unused range of past Unix timestamps, it assigns fields for a protocol signal, type, variant, and sequence identifier while remaining within Bitcoin consensus and policy rules, according to the document.

The stated goal is efficient transaction discovery: indexers can inspect this fixed-size header before deciding whether to examine larger payloads, such as OP_RETURN outputs or witness data. The proposal claims no additional marginal block-space cost and introduces neither a new on-chain storage mechanism nor new cryptographic primitives. The supplied description explains the design rationale but offers no measured indexing results, deployment evidence, or security analysis, so its practical efficiency and operational limits cannot be assessed from this text alone.

Key ideas

• The protocol repurposes the nLockTime field as a compact metadata header.
• Encoded values identify a protocol signal, type, variant, and sequence.
• Indexers can filter transactions using the fixed-size header before inspecting larger payloads.
• The design claims no new on-chain storage mechanism or cryptographic primitive.
• The description provides no measured performance or security evaluation.

Tags

# Efficient Bitcoin Meta-Protocol Transaction and Data Discovery Through nLockTime Field Repurposing


# Efficient Bitcoin Meta-Protocol Transaction and Data Discovery Through nLockTime Field Repurposing









We describe the Lockchain Protocol, a lightweight Bitcoin meta-protocol that enables highly efficient transaction discovery at zero marginal block space cost, and data verification without introducing any new on-chain storage mechanism. The protocol repurposes the mandatory 4-byte nLockTime field of every Bitcoin transaction as a compact metadata header. By constraining values to an unused range of past Unix timestamps greater than or equal to 500,000,000, the field can encode a protocol signal, type, variant, and sequence identifier while remaining fully valid under Bitcoin consensus and policy rules. The primary contribution of the protocol is an efficient discovery layer. Indexers can filter candidate transactions by examining a fixed-size header field, independent of transaction payload size, and only then selectively inspect heavier data such as OP RETURN outputs or witness fields. The Lockchain Protocol applies established protocol design patterns to an under-optimised problem domain, namely transaction discovery at scale, and does not claim new cryptographic primitives or storage methods.

Shown in full with attribution under the source's licence. Licence: abstract CC0

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.