.element Registry
Formal recognition and registration of discovered patterns from Bitcoin data
Formal Pattern Registration
Inscribing a .element
inscription using the following format:
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 | ||
pattern | Where If the | ||
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 |
1 | |
2 | |
3 | |
4 | |
5 | |
6 | |
7 | |
8 | |
9 | |
10 | |
11 | |
12 | |
13 | |
14 | |
15 | |
16 | |
17 | |
18 | |
19 | |
20 | |
21 | |
22 | |
23 | |
24 | Input |
25 | Input |
26 | |
27 | |
28 | |
29 | |
30 | Output |
31 | Output |
32 | |
33 | |
34 | |
35 | |
36 | |
37 |
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.
Last updated