GROK42.COMPUTER/#TERMINAL
GROK42 PROTOCOL [INTRO]
The GROK42 Protocol is an extension to the Digital Matter Theory (DMT) framework and is token-specific ($GROK42) to enable multiple art collections to exist within the $GROK42 NAT/UNAT supply and namespace.GROK42 introduces support for patterns in Bitcoin addresses and proposes a new DMT element field number 42 to represent any and all bitcoin addressess within transactions within specific blocks.GROK42 is a token on the TAP Protocol deployed as a DMT NAT (Non-Arbitrary Token) using element field 4 (block height) with no pattern defined. This means that all blocks can be claimed to mint $GROK42 NATs. The GROK42 Protocol is used to deploy UNAT (Unique NAT) art collections across any/all Bitcoin blocks.The first genesis collection uses Block 42 with no pattern defined. This 42 piece art collection consists of all unique 1 of 1 pieces handcrafted and inscribed on Bitcoin. Each Block 42 $GROK42 token is associated with each art piece numbered sequentially 1-42.The second collection is generative and uses the block range 767430 (block containing the first inscription 0) through block 842000 (The Grokening) containing the number 42 in block height and block transactions with bitcoin addresses containing variations of the word "grok" (case-insensitive, o or 0). Here is a dashboard tracking this collection's token supply and mint log:GROK42 #2 Collection Dashboard
| GROK42 Collections | Type | Block(s) | TXID |
|---|---|---|---|
| Genesis [#1] | non-generative | 42 | --- |
| Generative [#2] | generative | 767442 - 842000 | --- |
| Yours? | --- | --- | --- |
Read the GROK42 PRIMER ON GITBOOK
GROK42 PROTOCOL [SPEC]
Collection Registration
Collections are registered onchain as Ordinal inscriptions.It is required to use the metaprotocol field with the value of GROK42:REGISTER.The registration also requires the use of the metadata field for configuration.The collection name is formally registered in the inscription envelope payload as:<name>.grok42EXAMPLE:grokblocks.grok42METADATA ATTRIBUTES:id:<GROK42 DEPLOY TXID>
name:<name>
pattern:<pattern>
field:<field>
blocks:<block(s)>
protocol:<parent_protocol>EXAMPLE:
id:07555bcf148efa97cfed8717011e0f1429bf7a667d916faa6ca2d1cadd8a8ec2i0
name:grokblocks
pattern:grok
field:42
blocks:42-420
protocol:TAP-DMT
GROK42 PROTOCOL [SPEC]
Collection Registration
This example names the collection "grokblocks" and has pattern string requirement "grok" with a data source field number 42 (proposed DMT element field for tx bitcoin addresses) and a block range spanning blocks 42 through 420.The last parameter is optional and specifies which parent protocol the registration is associated with. $GROK42 was deployed on the TAP protocol using the DMT deploy operation.Note: bitcoin addresses adhere to the following rules for character exclusion:- Base58Check excludes 0, O, I, and l
- Bech32 excludes 1, b, i, and oNote: A specified pattern is always case-insensitive and automatically will interpret the number zero and letter o as equivalent.Note: Multiple collections can use the same blocks, block ranges or any overlapping blocks using different block ranges. Collection registration is not an exclusive claim on the specified block height numbers.Note: Collection names ARE unique and exclusive and can be considered the same as token tickers. They are effectively sub-tickers of $GROK42. In the above example, $GROKBLOCKS is the collection token ticker.
GROK42 PROTOCOL [SPEC]
Advanced Configuration
The example so far uses a single pattern and element field (block data source) across one or more blocks. To specify additional pattern requirements, formulas and advanced configurations that are necessary for generative art, an additional inscription is necessary.This inscription must be a child to the Collection Registration inscription using the Ordinals Provenance feature. Likewise, it is required to add GROK42:CONFIG to the Ordinals metaprotocol field.The benefit of this second inscription is that it enables a delayed art reveal. However, this advanced configuration could also be included in the registration inscription metadata if desired by the collection creator.The inscription should contain all information needed, including code, to generate the art according to the collection's standard.This goes beyond the GROK42 protocol at this point and will be up to creators to provide these details.to be continued
GROK42 PROTOCOL [SPEC]
GROK42:SPLIT
Since a GROK42 mint inscription (claimed blocks) can hold multiple art pieces from collections, there should be a way to split them out to transfer individually. This is where the grok42:split operation come in.delegate (child of grok42 mint):
OP_PUSH <mint txid>metaprotocol field:
grok42:splitmetadata field:
id:<collection txid>
⎸
⎯ other optional custom fields
