DEV Community

Daniel Ioni
Daniel Ioni

Posted on

From Metaverse Wallets to Zorgax Pro: What We Built This Week in MyZubster

From Metaverse Wallets to Zorgax Pro: What We Built This Week in MyZubster

Building an ecosystem is not just about adding features.

It is about connecting identity, marketplaces, AI, payments, visual storytelling, and real-world experimentation without breaking the security boundaries between them.

Over the last development cycle, we pushed several new pieces into the MyZubster ecosystem.

This post is a technical recap of what changed — and where we are going next.

  1. Connecting the Metaverse Market to a Multichain Wallet Hub

One of the main steps was connecting the MyZubster Marketplace architecture with a new non-custodial multichain Wallet Hub.

The marketplace can now represent transactions using:

ETH
BTC
XMR
TARI
MYZ
BARTER
FREE

The important architectural decision is simple:

MyZubster must never custody users' private keys.

The frontend can expose public receiving addresses, but seed phrases, private keys and signing credentials remain outside the application.

The Wallet Hub therefore acts as a public payment-routing layer rather than a custodial wallet.

The implementation landed in:

PR #811 — Connect metaverse market to multichain wallet hub

And it is now part of the main development history:

MyZubster repository

Conceptually, the flow is:

Metaverse

Marketplace

Wallet Hub

ETH / BTC / XMR / TARI

Independent transaction verification

No browser-side private-key storage is required.

  1. Starting the Monetization Layer for Zorgax

The next question was obvious:

How can Zorgax become an actual service instead of only an AI component?

We started building a subscription architecture.

The initial catalog contains:

Zorgax Free

Zorgax Pro
€9.90 / month equivalent

Zorgax Developer
€29.90 / month equivalent

Crypto payment intents can be created for:

ETH
BTC
XMR
TARI

But there is an important distinction between creating a payment intent and granting access.

A client cannot simply tell the API:

"I paid."

and receive Zorgax Pro.

The intended architecture is:

Checkout Intent

Crypto payment

Blockchain verifier

VERIFIED

Subscription

ACTIVE

30-day access period

EXPIRED / RENEW

Payment references are also designed to be single-use, preventing the same transaction reference from activating multiple subscriptions.

The current monetization work is tracked here:

PR #812 — Zorgax monetization foundation

The remaining critical step is connecting real network-specific verification for Bitcoin, Monero, Ethereum and Tari before enabling production payments.

  1. Security Before Monetization

Crypto monetization becomes dangerous very quickly if payment infrastructure and key management are mixed together.

Our rule is therefore:

PUBLIC ADDRESS → application can know it

TRANSACTION ID → application can verify it

PRIVATE KEY → application must not receive it

SEED PHRASE → application must not receive it

SIGNING CREDENTIAL → stays outside frontend

The marketplace should verify settlement.

It should not become the wallet.

This separation also makes the architecture easier to extend.

Each blockchain can eventually have its own adapter:

Bitcoin → Electrum / Bitcoin verification

Monero → Monero node / wallet RPC verification

Ethereum → Ethereum RPC verification

Tari → Tari wallet/network verification

All of them can ultimately produce the same internal result:

payment.verified = true

Only then does the entitlement layer activate the paid service.

  1. We Also Started Organizing the Visual Layer

Code is only part of an ecosystem.

We also reorganized several MyZubster visual assets into a clearer repository structure:

docs/
└── visuals/
├── life-2027/
├── market/
├── storytelling/
└── zorgax/

The new commit is:

Commit af8b1dd — organize MyZubster visual assets for LIFE 2027

It includes nine newly organized assets covering the environmental pilot direction, permaculture/AI, marketplace entities, Zorgax characters and MyZubster storytelling.

The visual structure now mirrors the technical structure of the project instead of keeping everything in one generic asset directory.

  1. LIFE 2027: Keeping Exploration Separate From Claims

Some of these visuals support our exploratory LIFE 2027 direction.

That distinction matters.

MyZubster is exploring environmental and agricultural pilot concepts, including areas such as water efficiency, environmental monitoring, soil conditions and AI-supported decision systems.

But exploratory work is not the same thing as an approved or funded LIFE project.

So our public communication needs to preserve that boundary:

Concept
→ pilot
→ measurable evidence
→ scientific / technical validation
→ consortium development
→ potential LIFE 2027 proposal

Not:

visual → partnership → funded project

That difference is especially important when open-source software starts interacting with environmental claims.

  1. The Architecture Is Starting to Connect

The interesting part is not any individual feature.

It is how the pieces are beginning to connect:

              MyZubster
                  │
    ┌─────────────┼─────────────┐
    │             │             │
  Zorgax       Metaverse     LIFE 2027
    │             │          exploration
    │             │
    │        Marketplace
    │             │
    └─────── Wallet Hub
                  │
         ┌────────┼────────┐
         │        │        │
        ETH      BTC      XMR
                           │
                          TARI
Enter fullscreen mode Exit fullscreen mode

Zorgax can become a service.

The Market can become an economic layer.

The Wallet Hub can provide non-custodial payment rails.

The Metaverse can become the interface connecting them.

And environmental pilots can remain a separate evidence-driven real-world experimentation layer.

  1. What's Next

The next development milestone is not another pricing page.

It is payment verification.

We need to turn:

"I sent a transaction"

into:

"The network independently confirms
that this transaction satisfies
this specific checkout intent."

After that, Zorgax Pro can move from subscription architecture toward an actual paid service.

The sequence is:

quote
→ payment intent
→ blockchain transaction
→ confirmation verification
→ entitlement
→ Zorgax Pro
→ expiry
→ renewal

Without giving the application custody of the user's wallet.

That is the direction we are building toward.

Follow the development

MyZubster on GitHub

Multichain Wallet Hub — PR #811

Zorgax Monetization — PR #812

LIFE 2027 visual organization commit

Suggested DEV.to title:
From Metaverse Wallets to Zorgax Pro: Building MyZubster's Multichain Economy

Tags: #opensource #webdev #blockchain #ai

Per la cover userei proprio la nuova MyZubster Visuals Organization — LIFE 2027, perché collega visivamente Zorgax, Market, LIFE 2027 e storytelling.

Top comments (0)