DEV Community

Daniel Ioni
Daniel Ioni

Posted on

MyZubster Dev Update — From Decentralization to NFTs and the Foundations of a Metaverse

MyZubster Dev Update — From Decentralization to NFTs and the Foundations of a Metaverse

Tonight was one of those development sessions where several independent pieces finally started becoming one system.

What began as infrastructure work around decentralization evolved into a complete blockchain flow: wallets, smart contracts, the MYZ token, Character NFTs, an on-chain marketplace, verified ownership transfers, and the first technical foundations of the MyZubster metaverse.

And, importantly, this wasn't just mocked in a UI.

We tested the complete flow on Ethereum Sepolia.

  1. Building toward a decentralized MyZubster

The goal is not simply to add blockchain features to an existing platform.

The goal is to progressively separate identity, ownership, value and digital assets from a purely centralized database.

The backend still plays an important coordination role, but blockchain becomes an independent verification layer for assets and transactions.

That means MyZubster can increasingly distinguish between:

what the platform says happened

and

what can be cryptographically verified to have happened.

That distinction is fundamental for the architecture we are building.

  1. Wallet ownership verification

Before allowing blockchain assets to interact with MyZubster accounts, we implemented wallet verification.

The flow is based on a challenge generated by the backend.

The user signs that challenge using their Ethereum wallet, and the backend verifies the signature.

No private key needs to be sent to MyZubster.

During tonight's test we successfully connected and verified two separate users and wallets: one acting as the seller and another acting as the buyer.

This gave us the identity layer needed for the marketplace.

  1. Deploying the MYZ token

We then deployed the MyZubster Token (MYZ) on Ethereum Sepolia.

MYZ uses 18 decimals and now exists as an actual smart contract on the test network.

For the marketplace test, the buyer received 100 MYZ.

That gave us something important: an ecosystem transaction could now be settled using MyZubster's own blockchain asset rather than a simulated database balance.

  1. Deploying the Character NFT contract

Next came the NFT layer.

We deployed the MyZubsterCharacter contract to Sepolia with a maximum supply of 10,000 Characters.

Then we performed the first real mint.

MyZubster Genesis Character #1 was created as token #1.

The backend recorded the asset, while the Ethereum network independently recorded its ownership.

This created the bridge between a MyZubster digital object and a blockchain-native asset.

  1. Synchronizing blockchain and backend state

Minting an NFT isn't enough.

A useful platform needs to know whether the blockchain state and application state agree.

So the NFT backend verifies the transaction on-chain before marking an asset as minted.

For Genesis Character #1, the system verified the mint transaction and synchronized its contract address, token ID, owner wallet and blockchain information with the MyZubster asset record.

This pattern will be important far beyond Characters.

The same architecture can eventually represent land, objects, collectibles, access rights, achievements and other metaverse assets.

  1. Building the MYZ NFT marketplace

With identity, MYZ and NFTs working, we connected them into a marketplace.

Genesis Character #1 was listed for:

10 MYZ

The listing recorded the seller, wallet, asset, blockchain network and asking price.

A second MyZubster account then entered the flow as the buyer.

Its wallet was independently verified through the same signature challenge system.

At that point we had two authenticated users controlling two independently verified blockchain wallets.

  1. Executing a real on-chain purchase

Then came the important test.

The buyer sent:

10 MYZ → seller

on Ethereum Sepolia.

After that transaction was confirmed, the seller transferred:

Character NFT #1 → buyer

The resulting balances confirmed the payment:

Buyer: 100 MYZ → 90 MYZ

And Ethereum confirmed that ownership of token #1 had moved from the seller wallet to the buyer wallet.

No ownership change was simulated.

The NFT actually changed hands on-chain.

  1. On-chain marketplace verification

The backend then received the payment transaction hash and NFT transfer transaction hash.

Instead of trusting those values, MyZubster checked Ethereum.

It verified the MYZ token contract, transferred amount, transaction confirmation, NFT contract, token ID and resulting owner.

Only after those checks passed did the marketplace finalize the sale.

The final result was:

success = true
verifiedOnChain = true
listing.status = sold
asset.status = sold

The MyZubster database and Ethereum ownership state were synchronized.

That completed our first end-to-end blockchain marketplace transaction.

  1. From NFTs toward the MyZubster metaverse

This is where the larger architecture starts becoming visible.

A metaverse needs more than a 3D world.

It needs persistent identity.

Persistent ownership.

Transferable objects.

An economy.

Rules for interaction.

A way for different services to agree on who owns what.

Tonight we connected several of those foundations:

MyZubster Account

Verified Wallet

MYZ Economy

NFT Assets

Marketplace

On-chain Ownership

Persistent Digital World

Characters can become blockchain identities inside virtual environments.

NFTs can represent objects.

MYZ can provide an economic layer.

The marketplace provides exchange.

And the blockchain provides an ownership layer independent from the application database.

That is the beginning of a metaverse architecture—not because we called something a metaverse, but because the underlying primitives required to build one are starting to exist.

  1. Building it in the open

The work is being developed and documented through MyZubster on GitHub.

We also created a visual representation of the NFT marketplace flow and added it to the MyZubster Gateway repository.

The system now has a reproducible story:

mint → list → pay → transfer → verify → synchronize

Every stage can be inspected, tested and progressively improved.

What comes next

This is still testnet infrastructure, not the final production network.

The next phase is about turning these primitives into a richer world: NFT inventory and profiles, Character visualization, marketplace UI, metaverse objects and environments, MYZ utility, richer metadata, interoperability between MyZubster services, stronger decentralized infrastructure, security review and eventually a carefully planned path beyond Sepolia.

But tonight crossed an important threshold.

MyZubster moved from describing a decentralized digital economy to successfully executing one.

A user owned an NFT.

Another user paid for it using MYZ.

The NFT changed owners on Ethereum.

The blockchain verified the transaction.

And MyZubster synchronized the result.

That is a small transaction technically.

Architecturally, it is the foundation of something much larger.

MyZubster — building the bridge between biodiversity, decentralized technology, digital ownership and persistent virtual worlds.

MyZubster #Web3 #Ethereum #NFT #Metaverse #Blockchain #OpenSource #Decentralization #ERC721 #ERC20 #BuildInPublic

Top comments (0)