---
# System prepended metadata

title: Token image editor

---

# Token image editor

## Overview

The token image editor should allow users to edit the layers in their token image. 

## Outsource requirements

### Context![Imagen de WhatsApp 2025-02-14 a las 11.49.00_6598e560](https://hackmd.io/_uploads/HJ4jtzpFkl.jpg)


Ivy boys is an NFT collection where each token image created from 14 layers, built upon each other. While there are metadata for each one of the images, the attributes follows a one-to-many mapping. For instance, while the metadata might state that the token include 'blue pants', there might be multiple blue pants images. Consequently, we are unable to recreate the image consistently from the metadata alone. 

### Task

For this task, we need to define a one-to-one map of each layer for each token. As such, for each token, we would need to get the following data:

```json
// 1.json
{
    type: normal, // either male | female | lengendary | silver | gold
    layer1: "./01 Background/Aperture#100.png",
    layer2: "./02 Body/LightNeutral#97.png",
    ...
    layer15: "./15 Accesories/Bouquet#14.png"
}
```




### Resources

You will receive a folder with the following content

- Tokens -- a folder containing all 7,777 images where you would need to use to reference
- Layers (Male) -- contains folders of each layers and the traits used to built them
- Layers (Lengendary) -- contains folders of each layers for legendary NFT's and the traits used to built them
- Layers (Female) -- contains folders of each layers for female NFT's and the traits used to built them
- Layers (Silver) -- contains folders of each layers for Silver NFT's and the traits used to built them
- Layers (Gold) -- contains folders of each layers for Gold NFT's and the traits used to built them
- Metadata -- contains the original metadata for the 
- Output -- store your output here. `1.json` has already been done.
