MyZubster: From a Centralized VPS to a Network of Independent Nodes — The Work of Nicola N4K48 and Wasim

Open source, Docker, Tor, interoperability, verifiable knowledge, and distributed governance: we are exploring an ecosystem where contributors can build, verify, and eventually operate independent nodes.

Decentralization does not begin with a cryptocurrency. It begins when multiple people can develop, verify, and operate a system without depending entirely on a single administrator.

This is the direction we are exploring with MyZubster, an open-source ecosystem connecting a marketplace, AI tools, independent projects, contributors, and verifiable knowledge.

Our goal is not simply to create another marketplace.

We want to build an ecosystem where developers, artists, researchers, and local communities can contribute their own projects, document their work, demonstrate their skills, and progressively operate independent infrastructure.

Two contributors are helping turn this vision into a concrete technical roadmap:

Nicola (N4K48) and Wasim (@wasim-builds).

Their work represents two complementary approaches to decentralization.

1. Nicola N4K48: Building an Independent Node

Nicola is developing an experimental model connecting creative projects, digital catalogs, software agents, and Docker-based infrastructure.

His work addresses a fundamental question:

Can an independent project maintain its technical autonomy while interoperating with the wider MyZubster ecosystem?

The documented checkpoints include local catalog and agent verification, alongside a previously completed authenticated connection test between the MyZubster VPS and the N4K48 node.

Following credential rotation, the agent has remained offline pending authorization for any further authenticated testing.

This is an important principle: decentralization must not come at the expense of security.

Nicola's GitHub contributions

Nicola's work demonstrates how an independent creative project can also become an experiment in autonomous infrastructure, verifiable contributions, and interoperability.

2. Wasim: Designing Resilient and Reproducible Infrastructure

While Nicola is experimenting with an independent node, Wasim is working on the technical foundations that could make this model safer, more resilient, and easier to reproduce.

His contributions currently cover four major areas.

A. Tor Onion, HAProxy, and Docker

Wasim has prepared an architecture proposal involving:

  • Docker containerization
  • HAProxy reverse proxy
  • Tor Onion connectivity
  • Threat modeling
  • Reproducible local tests
  • Rollback procedures
  • Security evidence

The objective is to investigate ways of improving service resilience and reducing infrastructure dependencies.

His reported tests were performed in an isolated local environment, without exposing host ports, using real credentials, or consuming external VPS resources.

The design is documented in:

Important: This is currently a technical proposal under review, not a production Tor service or an operational independent node.

B. Pastebin → GitHub → Zorgax Interoperability

Another contribution focuses on connecting external information sources to MyZubster's verifiable knowledge system.

Wasim has updated a technical design for an evidence-ingestion workflow with security protections, provenance checks, and human review.

The proposal includes:

  • HTTPS-only source restrictions
  • Redirect blocking
  • Protection against requests to private network addresses
  • Deterministic rejection tests
  • Payload limits
  • Sensitive-information filtering
  • Mandatory human review before accepting evidence

The proposed evidence format uses:

myzubster.knowledge.evidence.v1

The goal is to establish a clear distinction between information that has been submitted, imported, reviewed, and verified.

External information should not automatically become trusted knowledge.

Related work:

C. Contributor Passport Privacy

Wasim has also participated in reviewing privacy protections for the MyZubster Contributor Passport.

The underlying principle is straightforward:

A contributor's personal information should not become publicly accessible without appropriate consent controls.

This is particularly important when connecting identities, technical contributions, skills, evidence, and reputation.

D. GitHub CI Reliability and Hardhat 3

Decentralized infrastructure also requires reliable and independently verifiable software.

Wasim has contributed to GitHub Actions troubleshooting and reviewed the migration to Hardhat 3.

His review covered a change separating NFT tooling from the main application's dependency structure.

We are also investigating CI failures in our development fork.

3. What Are We Building Together?

Our long-term objective is to evolve MyZubster into a federated ecosystem of independently operated projects.

A simplified conceptual architecture looks like this:

 MyZubster Ecosystem | +-------------+-------------+ | | | Nicola Node Future Node Future Node N4K48 Wasim? Contributor | | | Docker/Agent Tor/HAProxy Independent Local Catalog Docker Application | | | +-------------+-------------+ | Interoperability | Zorgax / APIs | Knowledge & Evidence | Contributor Passport | Marketplace | DAO Governance

This diagram represents a proposed architecture, not an already operational federation. Wasim has not yet confirmed an independently operated production node.

The idea is that contributors could retain control over their own projects while choosing how to connect them to a shared ecosystem.

Different MyZubster components would serve complementary purposes.

Zorgax could help contributors explore and organize connected knowledge.

The Contributor Passport could document identities, skills, contributions, and supporting evidence.

The Marketplace could enable contributors to offer services, products, and technical expertise.

Independent nodes could host projects without requiring every service to run on the founder's central VPS.

DAO governance could eventually help distribute responsibilities, decision-making, infrastructure costs, and rewards.

4. Why We Want to Reduce Dependence on a Single VPS

A centralized infrastructure creates practical limitations.

One administrator may be responsible for hosting costs, maintenance, security, availability, and operational decisions.

This creates both technical and organizational risks.

Our goal is to investigate a model in which:

  • Contributors can independently operate parts of their infrastructure.
  • Projects communicate through documented interfaces.
  • Credentials remain under the control of their respective operators.
  • Tests can be reproduced without production access.
  • Infrastructure costs and responsibilities can be distributed.
  • Contributions and knowledge are supported by verifiable evidence.
  • Independent projects retain their identity and autonomy.

This transition cannot be achieved through a single deployment.

It requires reproducible tests, shared protocols, security reviews, operational agreements, and genuine collaboration.

5. Toward a DAO and Sustainable Contributor Economy

We are also exploring a DAO-inspired governance model for distributing work, responsibilities, costs, and rewards.

Our goal is to avoid building an ecosystem whose long-term survival depends entirely on one founder's personal resources.

However, a DAO is not created simply by issuing tokens or opening a GitHub discussion.

A sustainable governance model requires:

  • Clearly defined responsibilities
  • Transparent decision-making
  • Verifiable contributions
  • Fair and documented compensation arrangements
  • Sustainable infrastructure funding
  • Dispute-resolution procedures
  • Independent oversight

These mechanisms remain under development.

Related discussions:

Our objective is to develop a model in which independent contributors can create value, receive recognition, and potentially participate in sustainable economic activity.

6. What Has Been Tested, and What Still Needs to Be Proven?

One of the most important principles behind MyZubster is distinguishing proposals from verified implementations.

Already documented

  • GitHub contributions and technical reviews
  • Local Docker testing
  • N4K48 catalog and agent checks
  • A previously completed authenticated VPS-to-node checkpoint
  • Hardhat 3 migration review
  • Contributor Passport privacy review

Currently under review

  • Wasim's Tor/HAProxy architecture
  • Pastebin-to-Zorgax evidence ingestion
  • Additional CI reliability work
  • Reproducibility and security of the proposed infrastructure

Not yet demonstrated

  • A stable federation of multiple independently operated production nodes
  • Effective failover between independent infrastructure operators
  • Fully operational decentralized governance
  • Sustainable distributed infrastructure financing
  • End-to-end interoperability across all proposed services

These distinctions matter.

We want our technical claims to be supported by reproducible evidence, not just ambitious announcements.

7. An Invitation to Open-Source Contributors

MyZubster is open to developers, researchers, creators, and independent project operators interested in experimenting with interoperability and decentralization.

You do not need to own a VPS or invest money to begin contributing.

Useful contributions can include:

  • Code reviews and security analysis
  • Docker-based local experiments
  • API interoperability testing
  • Privacy and consent mechanisms
  • Knowledge graph research
  • Documentation
  • Accessibility improvements
  • Independent verification of technical evidence

We believe meaningful collaboration starts with small, clearly scoped, reproducible contributions.

Explore the project

Main project

Nicola N4K48

Wasim

Decentralization roadmap

Conclusion: Decentralization Is Something We Build Together

MyZubster is not yet a fully decentralized federation.

We are building and testing the components that could make such a federation possible.

Nicola is helping us understand how an independent project can operate as a node.

Wasim is helping us investigate how those nodes can become more secure, reproducible, interoperable, and resilient.

The next milestone is to verify that these components can work together safely, under distributed operational responsibility.

We are not simply trying to connect servers.

We are exploring how to connect people, projects, skills, evidence, and independent infrastructure.

And we want that process to remain open, transparent, and verifiable.

The future of MyZubster should not depend on one person operating everything. It should be something contributors can build, verify, and sustain together.

Daniel Ioni (h4x0r)

Creator & Administrator — MyZubster Ecosystem

opensource #decentralization #docker #webdev