Rooted In Code memory layer image 01
Rooted In Code memory layer image 02
Rooted In Code memory layer image 03
Rooted In Code memory layer image 04
Rooted In Code memory layer image 05
Rooted In Code memory layer image 06
Rooted In Code memory layer image 07
Rooted In Code memory layer image 08
Rooted In Code memory layer image 09
Rooted In Code memory layer image 01
Rooted In Code memory layer image 02
Rooted In Code memory layer image 03
Rooted In Code memory layer image 04
Rooted In Code memory layer image 05
Rooted In Code memory layer image 06
Rooted In Code memory layer image 07
Rooted In Code memory layer image 08
Rooted In Code memory layer image 09
Rooted In Code memory layer image 01
Rooted In Code memory layer image 02
Rooted In Code memory layer image 03
Rooted In Code memory layer image 04
Rooted In Code memory layer image 05
Rooted In Code memory layer image 06
Rooted In Code memory layer image 07
Rooted In Code memory layer image 08
Rooted In Code memory layer image 09
Rooted In Code memory layer image 01
Rooted In Code memory layer image 02
Rooted In Code memory layer image 03
Rooted In Code memory layer image 04
Rooted In Code memory layer image 05
Rooted In Code memory layer image 06
Rooted In Code memory layer image 07
Rooted In Code memory layer image 08
Rooted In Code memory layer image 09
Rooted In Code memory layer image 01
Rooted In Code memory layer image 02
Rooted In Code memory layer image 03
Rooted In Code memory layer image 04
Rooted In Code memory layer image 05
Rooted In Code memory layer image 06
Rooted In Code memory layer image 07
Rooted In Code memory layer image 08
Rooted In Code memory layer image 09
Rooted In Code memory layer image 01
Rooted In Code memory layer image 02
Rooted In Code memory layer image 03
Rooted In Code memory layer image 04
Rooted In Code memory layer image 05
Rooted In Code memory layer image 06
Rooted In Code memory layer image 07
Rooted In Code memory layer image 08
Rooted In Code memory layer image 09

Legacy Memory Layer

Earlier Roots are not lost

V1 / V2 Roots can carry memory forward, becoming part of the ancestry of the next generation.

A dedicated smart contract called Memory Layer will connect previous Rooted In Code tokens to the upcoming v3 mint. Eligible holders will be able to take part in the first mint phase, pass selected metadata forward, and enter the Studio before the public phase.

A snapshot will be taken before Phase 1 opens. Only Roots held at the snapshot block will be able to pass memory forward into v3.

Main lineage

V1
V1

Carries:

  • Name
  • Skin
V2
V2

Carries:

  • Accessory
  • Background
MEMORY LAYER

Snapshot

Eligible Roots held at the snapshot block are recorded before Phase 1 opens.

V3

Receives:

  • Inherited metadata
  • Provenance
  • Memory state

What should I do now?

1

If you hold V1, claim your free V2.

2

If you want V1 memory, hold a V1 before the snapshot.

3

If you want V2 memory, hold a V2 before the snapshot.

4

Wait for the Memory Layer snapshot announcement.

Explore the collections

RIC v1 collection artwork

RIC v1

Available on OpenSea and Manifold

RIC v2 collection artwork

RIC v2

Minting on Carve. Free claim available for RIC v1 holders

RIC v3 collection artwork

RIC v3

Upcoming. Mint planned through OpenSea / SeaDrop

Benefits for V1 and V2 holders

Phase 1 access

V1 and V2 holders at the Memory Layer snapshot block will be eligible for the first RIC v3 mint phase.

Free v3 mint eligibility

Phase 1 is planned as the free mint phase for eligible previous Rooted In Code collectors.

Early Studio access

Eligible holders will be among the first collectors able to enter the v3 Studio, where Roots can change visible state through on-chain interaction.

Memory-layer rarity

Memory-layer v3 Roots are designed to be among the rarest states in the collection because only eligible earlier Roots held at the snapshot can pass memory forward.

How it works

01

Snapshot announced

02

Eligible RIC v1 and v2 holders are recorded

03

Memory Layer records are prepared

04

OpenSea / SeaDrop phase opens

05

Eligible collectors mint v3

06

Memory is consumed and attached to the new Root

FAQ

Who is the Memory Layer phase for?

The Memory Layer phase is planned for eligible RIC v1 and RIC v2 holders. Only wallets holding eligible Roots at the snapshot block will be included.

Has the snapshot happened yet?

No. The snapshot date is currently TBD. The project is preparing the Memory Layer phase before Phase 1 opens.

What happens if I buy after the snapshot?

Eligibility is based on the wallet holding the Root at the snapshot block. If you buy after the snapshot, that Root may not be eligible to pass memory forward into the first Memory Layer phase.

What memory can v1 pass forward?

RIC v1 memory can carry the Root name and Skin data when present.

What memory can v2 pass forward?

RIC v2 memory can carry Accessory and Background color.

Is the Memory Layer mint free?

The planned price for the Memory Layer phase is free for eligible RIC v1 and v2 holders. Gas and any platform-related requirements will depend on the final OpenSea / SeaDrop configuration.

How many Memory Layer tokens are planned?

The current planned supply for the Memory Layer phase is 180 tokens.

What is the wallet limit?

The working plan is 1 v3 mint per each eligible RIC v1 or RIC v2 token.

What happens if I hold multiple v1 or v2 Roots?

The intended structure is that each eligible legacy Root should be able to pass memory forward once.

What happens if I move my Root before the snapshot?

Eligibility is based on the wallet holding the Root at the snapshot block. If a Root is moved before the snapshot, the receiving wallet may become the eligible wallet instead.

Will Memory Layer tokens be different from normal v3 mints?

Yes. Memory Layer tokens are intended to carry a connection to an earlier RIC v1 or v2 Root. This gives them an additional provenance and memory layer inside the v3 system.

Where will the mint happen?

Minting is planned through OpenSea / SeaDrop. The mint URL is not available yet.

Should I buy or move tokens now for eligibility?

The safest wording is that eligibility will be based on the snapshot block once announced. Until the snapshot details are final, collectors should avoid assuming eligibility from unofficial timing.

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.