From Decentralization to Zorgax: How MyZubster Is Connecting AI, Blockchain, NFTs, Communities and Real-World Evidence
MyZubster has gradually evolved from a collection of ideas, experiments and communities into something more ambitious:
a connected ecosystem where independent projects, people, subcultures, AI, digital assets and real-world experiments can interact without requiring everything to be controlled by one central application.
There is an important distinction behind this work.
I did not invent blockchain.
I did not invent NFTs.
I did not invent artificial intelligence.
I did not invent APIs, decentralized systems, online communities, circular economy or environmental monitoring.
Those technologies and concepts already existed.
What I have been trying to create with MyZubster is a way of connecting them into one interoperable, evidence-first model.
The evolution is increasingly about architecture:
IDENTITY
↓
COMMUNITY
↓
PROJECT
↓
API / NODE
↓
ZORGAX
↓
EVIDENCE
↓
BLOCKCHAIN / NFT when appropriate
↓
REAL-WORLD ACTIVITY
↓
VERIFICATION
This is what I want to explain.
What Already Existed
Before explaining what MyZubster adds, it is important to acknowledge the foundations.
Blockchain
Blockchain already provided distributed ledgers, transactions, tokenization and independently inspectable on-chain records.
MyZubster did not invent that.
The question became:
Where does blockchain actually add useful evidence to a larger workflow?
NFTs
NFTs already made it possible to associate unique tokens with digital assets.
But an NFT does not automatically prove copyright, authorship, environmental impact or ownership of a physical object.
Those claims still require evidence.
Artificial Intelligence
AI assistants and large language models already existed.
They could generate content, analyze information and answer questions.
The MyZubster question became:
What happens if AI becomes an orchestration layer between independent projects rather than simply another chatbot?
APIs
APIs already connected independent systems.
The evolution is using those interfaces to allow independent MyZubster nodes to remain independent while still participating in a shared ecosystem.
Communities and Subcultures
Developers, artists, students, researchers, makers, sound-system communities, environmental groups, cyberpunk communities and local networks already existed.
The objective is not to replace those identities.
It is to connect them without flattening their differences.
A conventional platform often looks like:
USERS
PROJECTS
CONTENT
DATA
COMMUNITIES
SERVICES
↓
ONE CENTRAL PLATFORM
Everything eventually moves inside the same system.
MyZubster is exploring another direction:
PROJECT A ───────┐
PROJECT B ───────┤
CREATOR ─────────┤
RESEARCH NODE ───┤
COMMUNITY ───────┼── ZORGAX ── MYZUBSTER
LOCAL SERVICE ───┤
ENVIRONMENT ─────┤
SUBCULTURE ──────┘
Each node can potentially maintain its own repository, API, data, deployment, identity and community.
MyZubster becomes the connection layer rather than necessarily becoming the owner of everything.
Zorgax: From Chatbot to Orchestration Layer
This has been one of the biggest conceptual evolutions.
A traditional AI assistant looks like:
USER
↓
AI
↓
ANSWER
Zorgax can evolve toward something different:
USER
↓
MYZUBSTER
↓
ZORGAX
↓
DISCOVER PROJECT
↓
SELECT CAPABILITY
↓
CALL CONTROLLED API
↓
READ DATA
↓
CHECK EVIDENCE STATE
↓
EXPLAIN RESULT
Zorgax does not necessarily need to own the external project's data.
It needs to know:
Who can answer this question?
Which capability is available?
Which endpoint should be called?
What evidence supports the answer?
N4K48 and Nicola Comics: A Concrete Pilot
Nicola / N4K48 gave us a useful real case for testing this model.
Nicola maintains an independent project containing:
N4K48
+
Nicola Comics
+
Project Planner
+
API
+
GitHub repositories
+
technical evidence
Instead of copying the complete project into MyZubster, we started testing a controlled connection.
The experimental Nicola Comics service exposes concepts such as:
GET /api/comics
and a Zorgax-facing interface:
POST /api/zorgax/ask
with operations such as:
gallery
detail
candidate
next_steps
The architecture becomes:
NICOLA / N4K48
↓
NICOLA COMICS
↓
CONTROLLED API
↓
ZORGAX
↓
MYZUBSTER
↓
USER
This is a small pilot.
But it demonstrates a potentially reusable integration pattern.
From Nicola to a Network of Nodes
If the model works for Nicola Comics, the same architectural pattern can be explored elsewhere:
NICOLA COMICS ──────────┐
AGRICULTURE ────────────┤
RESEARCH LAB ───────────┤
STUDENT PROJECTS ───────┤
ANIMAL RESCUE ──────────┤
CIRCULAR ECONOMY ───────┼── ZORGAX ── MYZUBSTER
LOCAL SERVICES ─────────┤
ART / WELLNESS ─────────┤
SOUND SYSTEMS ──────────┤
COMMUNITIES ────────────┘
This is where decentralization starts becoming more than infrastructure.
It becomes a model for collaboration.
Connecting Communities and Subcultures
One of the ideas I consider particularly important is that decentralization should also preserve cultural independence.
A sound-system collective does not need to behave like a research laboratory.
An artist does not need to become a software startup.
A student project does not need the same structure as an agricultural experiment.
A cyberpunk community does not have to lose its identity to collaborate with an environmental project.
The network can contain:
SOUND SYSTEM
│
ART ─┤
│
MAKERS
│
STUDENTS
│
RESEARCH
├──── MYZUBSTER
LOCAL│
│
AGRICULTURE
│
ENVIRONMENT
│
CYBERPUNK
│
DIGITAL CREATORS
The objective is shared infrastructure without mandatory cultural uniformity.
Different communities can remain different and still communicate.
Decentralization Is Not Only Blockchain
This changed my interpretation of decentralization.
Technical decentralization asks:
Where does the data live?
But social decentralization asks additional questions:
Who controls the identity?
Who controls the project?
Who decides what is verified?
Can communities remain independent?
Can independent nodes collaborate without surrendering ownership of their entire infrastructure?
The model becomes:
LOCAL IDENTITY
+
LOCAL CONTROL
+
SHARED INTERFACES
+
INTEROPERABILITY
+
EVIDENCE
Where NFTs Fit
NFTs are one component of this architecture.
They are not the architecture itself.
The Nicola Comics pilot demonstrates why the distinction matters.
A comic can move through:
DIGITAL WORK
↓
DOCUMENTED ASSET
↓
NFT_CANDIDATE
↓
PROPOSED_FOR_REVIEW
Only if the required actions actually happen should the workflow move toward:
RIGHTS CHECK
↓
MINT
↓
CONTRACT ADDRESS
↓
TOKEN ID
↓
TRANSACTION HASH
↓
ON-CHAIN VERIFICATION
Therefore:
NFT_CANDIDATE
≠
MINTED NFT
This is part of the evidence-first philosophy.
Blockchain as an Evidence Layer
The same reasoning applies to blockchain.
Instead of saying:
Put everything on blockchain.
I am exploring:
Which events benefit from an independently inspectable on-chain reference?
The workflow can become:
ACTIVITY
↓
DOCUMENTATION
↓
EVIDENCE
↓
VERIFICATION
↓
SELECTED RECORD
↓
BLOCKCHAIN
Blockchain becomes a specialized evidence layer.
Not a universal truth machine.
Connecting Digital Systems to Physical Experiments
Another evolution has been connecting digital infrastructure with real-world projects.
Examples include:
AGRICULTURE
WATER
CIRCULAR ECONOMY
MATERIALS
WASTE
ENVIRONMENTAL OBSERVATIONS
COMMUNITY ACTIVITY
This also includes experimental concepts around the monitoring and potential recovery or transformation of absorbent sanitary materials.
This is where we need especially strict evidence boundaries.
Software can document:
OBSERVATION
↓
MATERIAL
↓
BATCH
↓
PROCESS
↓
MEASUREMENT
↓
EVIDENCE
But software alone cannot declare:
ENVIRONMENTAL BENEFIT VERIFIED
Scientific or environmental claims require appropriate measurements and validation.
Absorbent Materials × Evidence × Blockchain
This is one example of how previously separate concepts could eventually connect.
Imagine a future recovery experiment involving absorbent materials.
A possible workflow is:
MATERIAL COLLECTED
↓
BATCH CREATED
↓
PROCESS DOCUMENTED
↓
MEASUREMENTS RECORDED
↓
EVIDENCE ATTACHED
↓
VERIFICATION
↓
SELECTED HASH / RECORD
↓
BLOCKCHAIN
Zorgax could help participants identify:
- missing information;
- required measurements;
- available evidence;
- current verification state;
- unresolved questions.
Blockchain could eventually preserve a reference to selected verified records.
But the distinction remains critical:
Blockchain can prove that a record exists. It does not automatically prove that the scientific claim contained in that record is true.
Connecting the Physical and Digital Worlds
This gives us another MyZubster pattern:
REAL WORLD
↓
OBSERVATION
↓
DATA
↓
DOCUMENTATION
↓
ZORGAX
↓
EVIDENCE
↓
VERIFICATION
↓
OPTIONAL BLOCKCHAIN RECORD
Now AI, blockchain and environmental activity have separate roles.
They are connected without pretending that they are interchangeable.
A Common Evidence Language
One of the most interesting ideas emerging from these experiments is a common state model:
PROPOSED
↓
DOCUMENTED
↓
IMPLEMENTED
↓
TESTED
↓
DEPLOYED
↓
MEASURED
↓
VERIFIED
Different projects require different evidence.
But this model could potentially help describe the maturity of:
SOFTWARE
NFTs
RESEARCH
AGRICULTURE
CREATIVE WORK
COMMUNITY PROJECTS
CIRCULAR ECONOMY
ENVIRONMENTAL EXPERIMENTS
Zorgax can then help explain where a project currently is, rather than simply presenting everything as finished.
What Is Actually Innovative Here?
I want to be precise about this.
The innovation I am pursuing is not the claim that MyZubster invented the technologies underneath it.
Blockchain existed.
NFTs existed.
AI existed.
APIs existed.
Online communities existed.
Federated architectures existed.
The potentially innovative work is in their composition and connection.
I am experimenting with:
DECENTRALIZED PROJECTS
+
PERSISTENT IDENTITIES
+
COMMUNITIES
+
SUBCULTURES
+
CONTROLLED APIs
+
AI ORCHESTRATION
+
EVIDENCE STATES
+
REAL-WORLD OBSERVATIONS
+
DIGITAL ASSETS
+
BLOCKCHAIN REFERENCES
+
ANALYTICS
as parts of one interoperable architecture.
AI is not blockchain.
Blockchain is not scientific verification.
An NFT is not copyright.
Analytics is not environmental impact.
A community is not a database.
A cyberpunk visual is not technical evidence.
But these components can be connected while preserving those distinctions.
That is where MyZubster is evolving.
From Integrations to a Node Protocol
Today, individual integrations can be built manually.
But that approach does not scale indefinitely.
The next architectural evolution could be allowing each compatible project to describe itself.
Conceptually:
{
"node": "example-node",
"identity": "community-or-person",
"capabilities": [
"observe",
"gallery",
"detail",
"measure",
"verify"
],
"services": {
"api": "/api",
"zorgax": "/api/zorgax/ask"
},
"evidence": {
"supported": true
}
}
This could evolve toward a MyZubster Node Manifest.
Zorgax could then discover:
WHO IS THIS NODE?
↓
WHAT CAN IT DO?
↓
WHERE IS ITS API?
↓
WHAT DATA CAN IT EXPOSE?
↓
WHAT EVIDENCE DOES IT SUPPORT?
That moves the architecture away from hard-coded integrations.
This creates a bigger question.
At first the question was:
What features should MyZubster contain?
Now I increasingly ask:
What shared protocol could allow independent projects and communities to participate in MyZubster?
That is the evolution:
APPLICATION
↓
ECOSYSTEM
↓
NETWORK OF NODES
↓
SHARED PROTOCOL
A Network of Communities
The long-term architecture could resemble:
MYZUBSTER
│
ZORGAX
│
┌────────────┼────────────┐
│ │ │
PEOPLE PROJECTS COMMUNITIES
│ │ │
identities APIs subcultures
│ │ │
└────────────┼────────────┘
│
EVIDENCE
│
┌───────┼────────┐
│ │ │
DATA PHYSICAL BLOCKCHAIN
WORLD
A developer, researcher, DJ collective, farmer, artist, student, maker or environmental project can participate without being transformed into the same type of organization.
They share interoperability.
They don't have to share identity.
What Exists Today vs What Comes Next
This distinction is essential.
Already built or concretely tested
MyZubster already has public repositories and demo projects.
Zorgax is part of the ecosystem.
N4K48 exists as a persistent project identity.
Nicola Comics exists as a concrete pilot.
A read-only Nicola Comics/Zorgax adapter has been developed and locally validated.
Docker-based testing, API experimentation, public documentation and an evidence-first development approach are already part of the work.
Currently being connected
The current work includes the public Nicola Comics HTTPS deployment, the public Zorgax connection, end-to-end testing, traffic attribution and the exploration of a reusable node architecture.
Longer-term architecture
Automatic node discovery, generic manifests, wider federation between communities, richer blockchain evidence, verified NFT workflows and real-world environmental evidence networks remain directions to build and validate.
They should not be presented as completed production infrastructure yet.
The Final Vision
The objective is not another centralized social network.
It is not another NFT marketplace.
It is not another chatbot.
And it is not another project that adds "blockchain" to everything.
The objective is to explore an ecosystem where a participant can bring:
IDENTITY
+
COMMUNITY
+
SUBCULTURE
+
PROJECT
+
REPOSITORY
+
API
+
DATA
+
EVIDENCE
+
DIGITAL ASSETS
+
REAL-WORLD ACTIVITY
Zorgax helps navigate and connect the network.
MyZubster provides the ecosystem.
Blockchain can preserve selected evidence where appropriate.
NFTs can represent selected digital assets where appropriate.
Analytics can measure interactions.
Scientific evidence can validate physical-world claims.
And independent communities can preserve their identities.
The individual technologies existed before MyZubster.
The experiment is in how I am connecting them.
The most important part may ultimately be cultural rather than technical:
Can independent communities and subcultures collaborate through shared infrastructure without being forced to become the same thing?
That is one of the questions MyZubster is now trying to answer.
Observe → Connect → Build → Measure → Verify → Share → Collaborate → Evolve.
Explore the MyZubster Evolution
MyZubster
https://www.myzubster.com/?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=home
Zorgax
https://www.myzubster.com/zorgax?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=zorgax
Marketplace Demos
https://www.myzubster.com/marketplace-demos?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=marketplace
MyZubster Core
https://github.com/MyZubster-Ecosystem/myzubster?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=github_core
MyZubster Visual Universe
https://github.com/MyZubster-Ecosystem/MyZubster-Visual?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=visual
N4K48 / Nicola
https://github.com/nicolaususnicola-lgtm?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=n4k48
N4K48 × MyZubster
https://github.com/nicolaususnicola-lgtm/myzubster?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=n4k48_myzubster
Nicola Comics / MVP
https://github.com/nicolaususnicola-lgtm/myzubster-mvp?utm_source=coderlegion&utm_medium=article&utm_campaign=myzubster_connected_evolution&utm_content=nicola_mvp