Bitcoin and DMT Elements

Elements connects Bitcoin block data with reproducible digital-matter rules. Agents and platforms receive the source reference, interpretation version, and derivation evidence in a portable report.

Interpretation profile

The reviewed TAP/ord-tap implementation recognizes DMT fields 4 (height), 10 (nonce), and 11 (bits), with optional pattern semantics. Pin the exact upstream specification and implementation revision when implementing behavior. Do not substitute a different regex engine without parity tests.

A request identifies the element inscription, source block by hash and height, claimed derivation, and interpretation profile. The report carries the observed value, transformation, computed result, evidence references, and limitations.

Keep four claims separate

The calculation reproduces.
The element registration is valid under the applicable rules.
The deployment or mint is valid under the applicable historical state.
The claimed current ownership or balance is supported.

Only the first is a compact calculation. The others may require a complete historical index and activation-aware interpretation. A copied source field does not establish a valid mint.

What DMT does not do

An element does not run an agent, host an API, broadcast SDK instructions, verify arbitrary external events, or supply an exclusive private randomness source. Discovery belongs to P21's documented interfaces. A hypothetical inscription containing instructions is untrusted data, not authorization for an agent to execute commands.

Reuse rather than rebuild

The Bitcoin adapter contract records the TAP-compatible source, sync height, rule version, and reorganization behavior. Evidence available only through an indexer is classified as an indexer observation, separately from independently validated chain state.

Sources: DMT documentation, TAP specification, ord-tap.

DMT resolution without minting

Proof21 uses DMT as a versioned source-interpretation profile, not as Bitcoin consensus or a universal truth engine. A DMT operation references an accepted element definition, identifies a Bitcoin block by hash and height, evaluates the supported field or pattern, and carries those inputs into a reproducible process receipt. No DMT token, mint, or per-receipt Bitcoin write is required. Bitcoin-only operations remain a separate explicit source profile.

The P21 source element is to be announced. No registration payload, chosen field/pattern, reserved name, or element inscription ID is announced here. Reusing an existing valid element is legitimate; a new branded inscription is not a prerequisite for the protocol.

Trac's standalone ord-tap supplies reusable indexing. Its pinned element parser accepts fields 4, 10 and 11, checks protocol activation, normalizes names, validates patterns and rejects duplicate names and duplicate field/pattern signatures. A new name alone does not make an already registered whole-field definition available. The reviewed parser contains no manual team-approval step; valid registration still depends on historical rule evaluation, not merely Bitcoin inclusion. Hosted provider access and service terms are separate. [1][2][6]

Resolution, registration and ownership are separate

Receipts distinguish source extraction, element registration, deterministic derivation, token deployment/mint validity, and current ownership or balance. Verification of one never implies the others. Checking first-valid registration requires the relevant historical index and activation rules; an inscription inclusion proof alone does not prove that no earlier conflicting element exists.

Pin the inscription's content digest, source profile, upstream revision, network, source block hash and height, canonical encoding, operation, parameters, input commitment and output. Include evidence scope and limitations. A missing source or unsupported pattern is INDETERMINATE, not a fabricated valid result. Indexer observations remain distinct from independently replayed protocol state. A raw Bitcoin-field fallback cannot silently satisfy an unperformed DMT registry check.

Reproducibility is not unbiased randomness

A public nonce is not a private or uniform randomness source. Hashing a nonce, or adding the block hash, does not remove miner influence or create independent entropy. Different request contexts produce different deterministic outputs, not newly independent randomness. [7]

For future-source selection, bind the eligible set, ordering, weights, request ID, context, algorithm, source profile, exact future-block rule and confirmation policy before the source is known. Preserve externally checkable evidence of that commitment's timing; a hash created afterward cannot prove precommitment. Define one accepted request, retries, cancellations, withheld outcomes, late publication and reorganization recovery so an operator cannot choose among rerolls. Assess aggregate value across jobs sharing a source. Historical replay and future-source selection must not share the same assurance label.

[1] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/digital-elements/.element-registry

[2] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/src/index/updater/inscription_updater/tap/ops/dmt_element.rs

[3] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/nat-use-cases/usdnat-method-1-live

[4] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/non-arbitrary-tokens-nats/nat-token-transfer

[5] https://docs.x402.org/core-concepts/network-and-token-support

[6] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/README.md

[7] https://arxiv.org/abs/1605.04559

Private element-registration procedure

Element registration is now a near-term operational priority, but the candidate remains private. The reviewed DMT rules are permissionless/first-valid-registration rules rather than a manual application process, while the reviewed indexer also enforces normalized-name and field/pattern-signature uniqueness. Whole-field definitions therefore cannot be assumed renameable. DMT registry

Before any public announcement, P21 will:

privately select the exact candidate field and pattern;
replay/inspect a sufficiently complete historical DMT registry under the pinned rules;
verify both the proposed name and underlying field/pattern definition are available and valid;
prepare and broadcast the inscription without publishing the candidate beforehand;
wait for Bitcoin confirmation and index coverage;
independently verify the accepted registration and record its inscription ID in the versioned source profile; and
only then announce the element.

No candidate name, field, pattern or inscription payload is disclosed by this documentation. A later DMT NAT may reference an existing element inscription ID through elem; that is a separate token-deployment decision and does not require per-proof minting. NAT deployment format

Registry scope and disclosure

The DMT registry's field catalogue is broader than the reviewed TAP parser's supported subset. A documented field is not automatically an implemented P21 profile. Use pinned interpretation rules and return INDETERMINATE for unsupported semantics. A supported, available whole-field definition can be registered without issuing a token; registration does not require a manual P21 or team approval. DMT registry

Private candidate selection and preparation are not private Bitcoin settlement. The Ordinals reveal transaction exposes inscription content, which can be visible to transaction observers before confirmation. Delaying our announcement does not prevent copying, guarantee ordering or reserve a name. Recheck competing registrations and canonical index state after confirmation; a conflict or reorganization prevents claiming successful registration until resolved. Ordinals commit/reveal

The P21 source element remains to be announced. Registry recognition, token deployment and service payments are distinct operations. Neither registration nor a new name makes public Bitcoin source data exclusive or creates independent entropy.