Rooted In Code about strip image 01
Rooted In Code about strip image 02
Rooted In Code about strip image 03
Rooted In Code about strip image 04
Rooted In Code about strip image 05
Rooted In Code about strip image 06
Rooted In Code about strip image 07
Rooted In Code about strip image 08
Rooted In Code about strip image 09
Rooted In Code about strip image 10
Rooted In Code about strip image 11
Rooted In Code about strip image 12
Rooted In Code about strip image 13
Rooted In Code about strip image 14
Rooted In Code about strip image 15
Rooted In Code about strip image 01
Rooted In Code about strip image 02
Rooted In Code about strip image 03
Rooted In Code about strip image 04
Rooted In Code about strip image 05
Rooted In Code about strip image 06
Rooted In Code about strip image 07
Rooted In Code about strip image 08
Rooted In Code about strip image 09
Rooted In Code about strip image 10
Rooted In Code about strip image 11
Rooted In Code about strip image 12
Rooted In Code about strip image 13
Rooted In Code about strip image 14
Rooted In Code about strip image 15
Rooted In Code about strip image 01
Rooted In Code about strip image 02
Rooted In Code about strip image 03
Rooted In Code about strip image 04
Rooted In Code about strip image 05
Rooted In Code about strip image 06
Rooted In Code about strip image 07
Rooted In Code about strip image 08
Rooted In Code about strip image 09
Rooted In Code about strip image 10
Rooted In Code about strip image 11
Rooted In Code about strip image 12
Rooted In Code about strip image 13
Rooted In Code about strip image 14
Rooted In Code about strip image 15
Rooted In Code about strip image 01
Rooted In Code about strip image 02
Rooted In Code about strip image 03
Rooted In Code about strip image 04
Rooted In Code about strip image 05
Rooted In Code about strip image 06
Rooted In Code about strip image 07
Rooted In Code about strip image 08
Rooted In Code about strip image 09
Rooted In Code about strip image 10
Rooted In Code about strip image 11
Rooted In Code about strip image 12
Rooted In Code about strip image 13
Rooted In Code about strip image 14
Rooted In Code about strip image 15

About The Project

One home for the Roots

Rooted In Code brings together RIC v1, RIC v2, and the upcoming RIC v3 as one connected on-chain art system.

What is Rooted In Code?

Rooted In Code is a fully on-chain art project about permanence, layering, memory, and digital identity.

It began with fixed 1/1 works stored on-chain, expanded into interactive and generative Roots, and is now moving toward a connected v3 system where earlier tokens can pass memory forward and new Roots can change state over time.

RIC v1 lineage artwork

RIC v1

Curated Layer

RIC v2 lineage artwork

RIC v2

Generative Layer

RIC v3 lineage artwork

RIC v3

State, Memory, and Identity

_ The image is the surface.

_ The state is the behavior.

_ The memory is the lineage.

_ The language layer becomes the inner profile.

V1 Echoing Spirit

Echoing Spirit · Flicker

v1: Curated

The Origin Layer

RIC v1 is the first Rooted In Code collection.

It consists of 3 static Genesis 1/1 works and 57 curated fully on-chain Roots that established the project’s origin layer.

Each piece began as stacked layers of AI-generated fragments of non-existing people, shaped through pixel structures and finished with animation and glitch interventions.

The Genesis works were hand-composed and drawn with care before Rooted In Code became interactive and generative. They carry the first ideas of the project: permanence, layering, and digital identity.

The later v1 Roots expanded that language toward interaction, variation, and on-chain visual life. Some of them also carry Skin metadata, preparing them to pass memory forward into v3.

Rooted In Code v1 archive image

Genesis 1/1

Static, hand-composed origin works. Fully on-chain PNGs embedded in SVG.

Rooted In Code v1 archive image

Curated Roots

Early fully on-chain works forming the first Rooted In Code collection body.

Rooted In Code v1 archive image

Interactive Roots

Works that began exploring movement, interaction, and on-chain visual behavior.

Rooted In Code v1 archive image

Skinned Roots

A subset prepared with Skin metadata so selected visual memory can pass forward into v3.

v2: Generative

The Generative Layer

RIC v2 carried Rooted In Code from curated works into a generative contract collection.

Each v2 Root is generated on-chain with its own visual structure, traits, accessory, and background color. These records can become part of the v3 Legacy Memory layer.

v2 is still minting through Carve. RIC v1 holders can claim one free RIC v2 Root.

In the wider project, v2 acts as the generative memory layer between the origin works of v1 and the living state system of v3.

V1 Echoing Spirit
Rooted In Code v2 archive image

Generative contract collection

Generated on-chain as a contract collection rather than hand-curated one by one.

Rooted In Code v2 archive image

Accessory memory

Accessory records can become part of the memory carried into the next generation.

Rooted In Code v2 archive image

Background color memory

Background color becomes another remembered visual record in the lineage.

Rooted In Code v2 archive image

Bridge to v3

v2 stands between the origin works of v1 and the living state system of v3.

V1 Echoing Spirit

Echoing Spirit · Flicker

v3: Studio

State, Memory, and Identity

RIC v3 expands Rooted In Code into a living on-chain system.

Each Root begins with a body, but the artwork is not frozen at mint. Through the Studio, collectors will be able to shape selected visual states on-chain, including phase, visible layers, palette, scale, timing, and reseed.

v3 also introduces the Legacy Memory layer, allowing eligible v1 and v2 Roots to pass selected records forward into the next generation.

The mint is the birth event. The Studio is where behavior begins.

Memory artwork

Memory

Earlier Roots can pass selected records forward.

State artwork

State

A Root can change visible state through on-chain interaction.

Identity

Trait language forms the foundation of an inner profile.

Artist note

Rooted In Code is built as an evolving body of on-chain work.

Rooted In Code continues my ongoing research into fully on-chain art, permanence, generative systems, and the changing relationship between artist, collector, and protocol. The work is built to live as code, but also to remain open to touch, interpretation, and change.

Each collection adds another layer to the same question:

What does it mean for something to be on-chain art?

Can we preserve our memories, emotions, and identity through the medium of the blockchain?

@masteronchain

Project timeline

Rooted In Code timeline

  1. Origin

    where the Roots began.

    Passed
  2. Memory

    where earlier Roots pass forward.

    Current phase
  3. Birth

    where v3 begins.

  4. State

    where the artwork changes.

  5. Phase 05

    This layer is not ready to be revealed yet.

  6. Phase 06

    Details will appear when the system reaches this stage.