.element Registry

Formal recognition and registration of discovered patterns from Bitcoin data

Formal Pattern Registration

Inscribing a .element inscription using the following format:

<name>.<pattern>.<field>.element

The first deployment of an element is the only one that has claim to the name. Names are not case sensitive (DOGE = doge).

The NAME field (<name>.<pattern>.<field>.element) can not be reused to represent other elements.

Examples:

Valid: dmt.11.element

Valid: vitalik.12.element

Valid: satoshi.1.11.element

Valid: hal.2.11.element

Invalid: dmt.3.11.element

Invalid: gary.11.element

Parameter	Required	Optional	Description
name			Where <name> identifies the title of your element with the following characters excluded, whitespace is also excluded: /.[]{}:;"'
pattern			Where <pattern> is the pattern discovered in the desired <field> of choice. The field consists of the following fields within block data of Bitcoin. We've excluded redundant and non-relevant block data fields such as 'confirmations'. If the <pattern> field is left off, you are invoking the whole field and disregarding the pattern sequence identification within that field, thus treating the value of the field itself as the non-arbitrary root of information. Visit $NAT for a live example.
field			<field> represents a mapped dataset of the block data of Bitcoin. Use the following table as a reference.

Field Parameter

Field	Block Data
0	Block "block_hash" : "hex",
1	"size" : n,
2	"strippedsize" : n,
3	"weight" : n,
4	"height" : n,
5	"version" : n,
6	"versionHex" : "hex",
7	"merkleroot" : "hex",
8	"time" : xxx,
9	"mediantime" : xxx,
10	"nonce" : n,
11	"bits" : "hex",
12	"difficulty" : n,
13	"chainwork" : "hex",
14	"nTx" : n,
15	"hex" : "hex",
16	"txid" : "hex",
17	"tx_hash" : "hex",
18	"size" : n,
19	"vsize" : n,
20	"weight" : n,
21	"version" : n,
22	"locktime" : xxx,
23	"blocktime" : xxx,
24	Input "asm" : "str",
25	Input "hex" : "hex"
26	"sequence" : n,
27	"txinwitness" : "hex",
28	"value" : n,
29	"n" : n,
30	Output "asm" : "str",
31	Output "hex" : "str",
32	"reqSigs" : n,
33	"type" : "str",
34	"witness":boolean,
35	"btc_fee": n,
36	"is_coinbase": boolean,
37	"coinbase":"hex"

Note: If you find fields that need to be supported, new fields will be added to the end of the list.

---

Trac Core will be providing indexing service of all .element inscriptions Mscribe.io will provide platform support and record keeping for registered .element inscriptions and Deployer inscriptions.