Forem: Sudip

🧟 Level 2: The DNA Blueprints & The Zombie Army (Solidity Quest)

Sudip — Sun, 10 May 2026 23:24:56 +0000

In Level 1, we dropped our "Citadel" (the Smart Contract) onto the Ethereum grid. It’s a safe, empty fortress. But a factory without a product is just a building.

Today, we are installing the most important part of our factory: The Storage Vaults. We need a way to define what a Zombie is and a place to keep an infinite army of them.
🧬 Step 1: The DNA Blueprint (Structs)

In a strategy game, every unit has "Stats"—HP, Mana, Attack Power. In our factory, every Zombie has DNA.

Instead of making separate boxes for every stat, Solidity lets us create a Struct. Think of a struct as a Technical Manual or a Blueprint that groups all the characteristics of a unit together.
Solidity

struct Zombie {
string name;
uint dna;
}

👁️ Player Vision: You walk into the center of the citadel and install a holographic terminal. This terminal defines the "Species." Every Zombie created from now on MUST follow this blueprint: It must have a Name and a DNA code.

📦 Step 2: The Infinite Army (Arrays)

Now that we have a blueprint, where do we keep the Zombies once they are built? We need a List.

In Solidity, we use an Array. Think of this like a Infinite Baracks. Every time a new Zombie is born, it gets a bunk bed in these barracks and an ID number.
Solidity

Zombie[] public zombies;

👁️ Player Vision: You pull a lever, and the floor of your fortress opens up to reveal a massive, underground storage hanger. It's empty for now, but it's labeled "THE ARMY." Because it’s public, anyone can look through the glass floor and see how many Zombies you have.

🔢 Step 3: Setting the "Physics" of DNA (State Variables)

We want our Zombie DNA to be exactly 16 digits long. To do this, we need a mathematical constant. We use a State Variable.

State Variables are "Hard-coded" into the blockchain. They are like the Laws of Physics in your game world.
Solidity

uint dnaDigits = 16;
uint dnaModulus = 10 ** dnaDigits;

👁️ Player Vision: On the wall of your factory, you bolt down a massive brass plate. It says: "DNA LIMIT: 16 DIGITS." This rule is now permanent. The factory's machines will use this plate to make sure no Zombie is born with a 17-digit mutation.

🛠️ The Full Code (Level 2)

Here is how our ZombieFactory.sol looks now:
Solidity

// SPDX-License-Identifier: MIT
pragma solidity >=0.5.0 <0.6.0;

contract ZombieFactory {

uint dnaDigits = 16;
uint dnaModulus = 10 ** dnaDigits;

struct Zombie {
    string name;
    uint dna;
}

Zombie[] public zombies;

}

🏆 Level 2 Cleared

We have the Blueprint (Struct), the Barracks (Array), and the Laws of Physics (State Variables).

Our factory is now "Data Ready." But wait... the machines aren't moving yet. We have the storage, but we don't have the Functions to actually create the Zombies.

In Level 3, we will build the "Creation Engine"—the functions that take a name and turn it into a living, breathing (well, undead) monster.

Is your DNA vault ready? Drop a 🧬 in the comments if you're following the quest!

🏗️ Building Web3: If Solidity Looked Like an Epic Strategy Game (Part 1)

Sudip — Sun, 26 Apr 2026 15:09:39 +0000

To be honest staring at code on a black screen is really boring. When I first started learning Web3 and Solidity I found that reading text did not work for me. My brain does not process syntax it processes worlds.

So I changed my perspective. I started looking at my code editor like a gaming console. Every line of code I type is not just text it is an action happening on a map, like a match of Dota 2 or Clash of Clans.

Today we are starting a journey to build a Zombie Factory on the Ethereum blockchain.. Before we write our first line we need to see the big picture.

🗺️ The Master Plan: What is our end goal?

Imagine a tech cyberpunk factory glowing with neon-green energy. This is an automated assembly line that creates digital monsters.

By the end of this series our Zombie Factory will work like this:

The input: a player types a name like "Niraj".

The DNA Mixer: a machine crushes that name. Spits out a random 16-digit DNA code.

The Assembly Line: robotic arms scan the DNA saying things like " two digits give it laser eyes next two digits, red skin".

The Vault: the finished Zombie is dropped into a blockchain-locked vault.

The Alarm: a rings out to the world saying "a new Zombie has spawned".

Every empire starts with a single base. Let’s claim our land.

🎮 Level 1: The Drop

Picture an empty dark grid floating in a digital void. This is the Ethereum blockchain waiting for your command.

Here is the exact code we are using to drop our "Main Base" onto the map:

Solidity

// SPDX-License-Identifier: MIT

pragma solidity >=0.5.0 <0.6.0;

contract ZombieFactory {

}

It looks like four lines.. Let’s put on our gaming Heads-Up Display and see what is actually happening.

📜 Line 1: The Diplomatic Flag (The License)

Solidity

// SPDX-License-Identifier: MIT

If you imagine this a flying drone drops a glowing scroll onto the center of our grid. It projects a MIT" sign.

The way it works is that this is your permit. You are telling the network "my blueprints are source anyone can read my code for free". You must declare this before you are allowed to build.

⚙ Line 2: Locking the Physics Engine (The Pragma)

Solidity

pragma solidity >=0.5.0 <0.6.0;

If you picture this a massive mechanical gear slams into the ground and locks the server settings to version 0.5.0.

The way it works is that pragma tells the computer which tools to use. You are saying, "only use this version to build my factory if you use old or experimental tools my base will collapse".

🏭 Line 3: Dropping the Citadel (The Contract)

Solidity

contract ZombieFactory {

If you imagine this a massive stone fortress drops from orbit. Crashes onto the grid. The screen shakes a neon sign flickers on: Zombie Factory.

The way it works is that in Solidity a contract is your Town Hall. It is the container, every piece of data and every machine we build later will be stored safely inside this building.

🛡️ Line 4: Activating the Kinetic Shield (The Scope)

Solidity

}

If you picture this as you type the bracket four pillars shoot up and create a pulsing green energy dome over your fortress.

The way it works is that this is your scope, anything inside the { and }'s safe inside your Zombie Factory walls. This is where your rules work outside the walls is the public blockchain.

🏆 Level 1 Cleared

Congratulations you just deployed your Smart Contract, the Zombie Factory.

If you visualized it right you did not type words you dropped a flag locked the physics crashed a fortress onto the map and activated a shield.

Now our Zombie Factory is safe but it is empty. In Level 2 we are going to walk and start mounting the Zombie Factory rules onto the walls.

Are you ready to level up? Drop a comment if your fortress is live.

📜 Credits & Inspiration

This series is inspired by the interactive lessons at CryptoZombies.io. They are the best at gamifying the blockchain. I am documenting my journey as I learn from them.

⚠️ Disclaimer

This blog is, for entertainment purposes only. I am a learner documenting my journey this is not professional advice. Always test your code before deploying it to a network the Ethereum blockchain.