Technical Overview

With the Robot's Forge, our Ordinal stack houses a minting standard similar in implementation to BRC-721, but of course fully on-chain through recursion and NOT using IPFS in any capacity. In unison, a recursive HTML (FORGE) to act as a fully on-chain replacement for a minting website.

PNG Inscriptions

All of the 246 traits of this collection have been inscribed as PNGs to be referenced by the forge at mint.

Recursive HTML + JSON Inscriptions

A deployment JSON (or other) and mint JSON files are integrated within the forge / mint recursive HTML inscriptions.

  • The mint inscription includes a JSON holding important details such as DNA, and indexing variables for provenance. The code below is only a reference example, in Recursive Robots we added our necessary data into the meta tag but everything is indexable.

  • {"p":"FORGE",



    "head": "6c8edcd37b16ad6ff87f8ee14de6fa82344139a348b4923c3c75fec24a4fa7e9i0", // Head inscription ID reference

    "body": "6c8edcd37b16ad6ff87f8ee14de6fa82344139a348b4923c3c75fec24a4fa7e9i0"} // Body inscription ID reference

  • The forge inscription includes a deployment JSON that provides collection reference details, supply, traits, and provenance. The deployment code below is just an example reference of our Forge deployment. You can customize this as needed for any projects, the sky is the limit.

  • {"p":"FORGE",



    "supply": "10000",

    "common":"0", // Sat enum







Collection Indexing - Provenance JSON Inscription

Once the collection has minted out we need to run a one time indexing to resolve the final list of holders. This will be inscribed as a reference for the community and builders to have for the rest of time. We will need to check that the HTML matches what we should expect as a valid inscription, the order of inscription since this is a first come first serve mint with a 10K supply, and then finally check the sat data of each valid inscription within the collection. This tool has not been created yet, but of course as always the data is all on-chain so it just needs indexed a single time.

Last updated