MyZubster: Building a Decentralized Future

Leader ●2 ●24 ●155
calendar_today • schedule11 min read

From Two Developers to a National Digital Network: Can We Build an Internet That Belongs to Its Participants?

How MyZubster is exploring independent nodes, local AI, verifiable knowledge, digital identity and a new model of technological cooperation.

By Daniel Ioni — MyZubster Open Ecosystem

An ongoing collaboration with Nicola / N4K48


What if we stopped building platforms and started connecting independent people?

For years, the technology industry has encouraged us to build bigger platforms.

More users. More data. More centralized infrastructure.

Every successful platform promises convenience, integration and a better experience.

But there is a fundamental question we rarely ask:

What happens to our independence when our entire digital existence depends on infrastructure controlled by someone else?

As developers, we have become extremely good at connecting applications to centralized services.

Perhaps our next challenge should be connecting independent applications to each other.

That is the idea behind our current MyZubster experiment.

I am Daniel Ioni, and together with an independent developer named Nicola, also known as N4K48, I am investigating how personally controlled software can become part of a wider digital ecosystem.

Our experiment began with two independent environments.

I operate the MyZubster infrastructure on a VPS.

Nicola develops his own software on a separate Windows computer.

We have built a Node Bridge designed to exchange selected information between these environments without requiring Nicola to expose his complete local application to the public Internet.

The updated Bridge is already deployed and tested on the VPS.

Our next milestone is the authenticated end-to-end connection with Nicola's actual computer.

But while building this connection, we began asking a much more ambitious question.

Could an experiment involving two developers eventually provide useful lessons for building a nationwide network of independent digital services?

Not a single platform controlling everything.

A federation connecting independently operated systems.

Here is what such a future would require.

1. Decentralization without interoperability is just fragmentation

Imagine a country with thousands of independent servers.

Every university has a node. Every association has another. Municipalities operate their own infrastructure. Developers maintain independent applications.

It sounds decentralized.

But what happens if none of these systems can communicate?

We have not built an ecosystem. We have created thousands of isolated islands.

This is why open standards must come first.

A future federated MyZubster architecture should investigate compatibility with established approaches for decentralized identity, verifiable credentials and interoperable data exchange.

Public, versioned APIs would allow third-party developers to implement compatible services without depending on our original codebase.

Existing European digital identity initiatives are particularly relevant.

Interoperability with the European Digital Identity Wallet, eIDAS and appropriate national identity systems deserves investigation.

However, our current experimental software has not demonstrated that compatibility.

Supporting a standard requires actual implementation, conformance testing and, where applicable, regulatory assessment.

The broader principle is straightforward:

An ecosystem becomes meaningful when its participants can leave, migrate and still communicate.

If users cannot move between compatible services, decentralization becomes another marketing term.

2. Our first practical experiment: the Node Bridge

Large technological transformations need small, testable beginnings.

Our beginning is a connection between two independently managed computing environments.

The MyZubster VPS runs a Docker-based broker behind Nginx and an HTTPS endpoint.

Nicola's environment contains his experimental software, local database components and AI-related services.

A lightweight Python agent is designed to initiate outbound communication with the VPS.

It retrieves authorized requests, processes them through Nicola's local application and returns limited results.

This architecture means we do not need to expose his entire local development API directly to the Internet.

But building the first version revealed an important problem.

Our broker used temporary job assignments. When an assignment expired, the request could be offered to another agent.

Unfortunately, an outdated agent could still submit a result associated with its expired assignment.

We reproduced this behavior and corrected it by requiring a unique identifier for every assignment.

An outdated result is now rejected rather than accepted as the result of the current operation.

Our corrected implementation passed automated regression tests and an integration test inside a separate Docker deployment.

We updated the production broker on the VPS and subsequently rotated its credentials.

The next step is completing the real authenticated connection with Nicola's computer.

Notice what this experience teaches us.

A distributed system is not simply an application running on multiple computers.

It must handle delays, disconnections, retries, outdated information and conflicting operations.

If we cannot solve these problems for two independent environments, we have no credible foundation for discussing thousands of nodes.

3. Local AI could change who controls information

Artificial intelligence will influence almost every digital service.

But that does not necessarily mean all information must be transferred to a remote AI provider.

Nicola's independent project explores an alternative.

His experimental MyZubster MVP uses technologies including Ollama and Qdrant to support locally executed AI and retrieval-augmented generation.

Its underlying philosophy is evidence-first development.

The application should distinguish between an exact stored observation and a plausible AI-generated answer.

This becomes especially important when AI participates in education, professional workflows or public services.

Imagine a federation in which participants maintain appropriate datasets locally.

An independent node could answer a permitted question or provide an authorized service without necessarily transferring its entire underlying database.

Some operations might still require cloud services. Others could remain local.

The important innovation would be having a meaningful choice.

However, running AI locally does not automatically establish privacy, security or regulatory compliance.

Those properties must be designed and evaluated independently.

4. What about Tor?

Our broader infrastructure experiments also include Tor.

That creates an opportunity to investigate different communication paths for independent services.

Tor onion services can provide network privacy properties that differ from conventional Internet hosting.

But we should avoid mixing concepts.

Tor is not synonymous with decentralization.

HTTPS is not equivalent to anonymity.

And an encrypted connection is not automatically an authorized connection.

Our currently verified Node Bridge communicates through conventional HTTPS.

A dedicated onion transport for the complete Nicola connection remains a possible future experiment, not a completed technical result.

In a mature federation, alternative communication methods could improve flexibility and potentially resilience.

Every method would need an appropriate threat model, security testing and clear operational documentation.

The objective should be practical autonomy, not technological mysticism.

5. Digital identity must become portable

Today's digital identity is often fragmented across commercial platforms.

People maintain different profiles, credentials and records of their achievements.

Organizations face similar problems.

A federated digital ecosystem could investigate ways to improve identity portability and selective information sharing.

Decentralized identifiers and verifiable credentials offer relevant technical approaches.

But adopting these technologies responsibly requires much more than creating a wallet or issuing a token.

Identity recovery matters.

Credential revocation matters.

Fraud prevention matters.

Privacy matters.

Legal responsibility matters.

A citizen should not be expected to become a cryptography expert merely to use a digital service.

If this model is ever to become widely adopted, its user experience must compete with the convenience offered by centralized applications.

That means accessible onboarding, appropriate recovery mechanisms, understandable permissions and reliable technical support.

It also means offering different participation models.

Some people may want to operate their own infrastructure.

Others may prefer services operated by trusted associations, cooperatives or professional providers.

Decentralization should expand people's choices rather than create a new technical barrier.

6. Can knowledge become independently verifiable?

This is one of the most interesting questions emerging from our collaboration.

When someone says they have learned a skill, how can they demonstrate their progress?

Traditional profiles rely heavily on self-description.

Repositories can provide useful evidence of development activity.

Technical reports can document methodology.

Tests can demonstrate specific software behavior.

Educational institutions can assess competence.

What if we could connect these different forms of evidence?

MyZubster is exploring a knowledge-proof approach built around inspectable records, versioned source material, cryptographic digests and acknowledged contributions.

Our work with Nicola has already contributed to a documented knowledge-transfer experiment with a recorded commitment on a blockchain test network.

That commitment can be used to verify the integrity of the corresponding evidence package.

However, this does not mean the blockchain has automatically certified someone's skills.

Cryptographic integrity and human assessment are different things.

An effective knowledge system would need both technical verification and appropriate evaluation.

Imagine a student who builds a working application, publishes its source code, documents its tests and receives an appropriate assessment from an authorized institution.

Imagine that the resulting portfolio could be accessed through compatible services without depending on a single educational platform.

That is the kind of long-term possibility worth researching.

7. Why our experiment also includes a comic

Technology is not experienced only through source code.

People understand complex ideas through stories, visual identities and creative expression.

During our collaboration, Nicola developed a series of illustrated chapters around his digital identity, N4K48.

The story follows his journey from an independent software idea toward the fictional cyberpunk environment of Neon Plaza.

Its fourth chapter is called The Bridge to Be Built.

It reflects the very real technical challenge we are currently addressing.

This creates an unusual connection.

The comic communicates the development journey.

The software repository records implementation work.

The test evidence documents verified technical behavior.

The knowledge records help connect the relevant information.

We are also exploring transparent provenance for digital creative work.

One original N4K48 comic is currently documented as a proposed NFT candidate.

It has not been minted, and relevant rights must be verified before any authorized commercial application.

The broader objective is not to tokenize everything.

It is to develop better ways of documenting creative work and connecting its history to appropriately verified records.

8. A nationwide ecosystem needs governance, not just servers

Suppose independent nodes become technically interoperable.

Who establishes common rules?

Who handles disputes?

What happens when participants publish illegal content, abuse shared services or dispute the validity of a credential?

These problems cannot be solved through server architecture alone.

A larger federation would need transparent governance.

One possible direction is a multi-stakeholder organization involving independent developers, users, educational institutions, civil society and participating service providers.

It could coordinate technical standards, develop shared policies and provide transparent processes for addressing disputes.

But governance must not become another mechanism for concentrating control.

Independent participants need meaningful representation.

Protocol decisions should be open to scrutiny.

Operators must remain accountable for their own legal obligations.

We want to investigate shared rules without recreating the same centralized dependencies that motivated the project.

9. There is no sustainable decentralization without an economy

Someone must pay for infrastructure.

Someone must maintain the software.

Someone must respond when security problems emerge.

Someone must create documentation, assist users and conduct independent assessments.

Open source is a development and licensing model, not a magical source of unlimited operational funding.

If MyZubster eventually expands beyond its laboratory stage, we will need a sustainable economic model.

Possible approaches include research grants, professional services, educational initiatives, managed infrastructure and partnerships around useful applications.

There is no requirement to launch a speculative token.

Any potential crypto-asset or payment-related feature would require a separate economic justification and appropriate regulatory analysis.

The best foundation for sustainability is demonstrable value.

If independent participants receive genuine benefits from interoperability, privacy choices and shared services, sustainable business and organizational models become easier to investigate.

10. The regulatory challenge

A national-scale ecosystem cannot operate outside legal responsibility.

Its architecture would need to account for applicable data-protection obligations, digital identity requirements, AI regulation and other rules relevant to the services it actually provides.

The GDPR, European AI Act, eIDAS framework and potentially MiCA are among the areas requiring professional assessment when their respective conditions apply.

Creative projects introduce copyright and licensing considerations.

Sensitive information requires additional protections.

Financial services may introduce further obligations.

These frameworks are not interchangeable, and no single technology establishes automatic compliance.

Our current project is experimental.

We are not claiming formal regulatory approval, institutional adoption or readiness to handle sensitive public-sector information.

Legal design must evolve alongside technical design.

11. Five stages from laboratory to possible national adoption

Here is a realistic way to structure the ambition.

Stage 1: Build and verify

Complete the authenticated test between the VPS and Nicola's independent computer.

Release reviewed Bridge code.

Publish reproducible tests.

Document security boundaries and known limitations.

This is our current stage.

Stage 2: Invite independent participants

Connect additional nodes operated by different people.

Validate onboarding, consent, access revocation and operational recovery.

Test small, non-sensitive applications with willing communities.

Stage 3: Create regional federation experiments

Move beyond a single central broker.

Develop compatible implementations and multiple independently administered coordination services.

Evaluate interoperability and resilience under realistic operating conditions.

Stage 4: Investigate institutional integration

Work with appropriate technical, academic or institutional partners where opportunities arise.

Evaluate relevant standards, accessibility, governance and compliance.

Identify applications that deliver measurable benefits.

Stage 5: Support wider adoption

If the previous stages succeed, develop the accessibility, organizational capacity and sustainable funding needed for broader participation.

National adoption should emerge from demonstrated value rather than an announcement.

We cannot declare an infrastructure ready simply because its roadmap contains the word national.

12. The most important metric is independence

Millions of registered users would make an impressive headline.

But they would not automatically prove that we had built a meaningful decentralized ecosystem.

We should measure something more important.

Can independently operated systems communicate?

Can participants leave without losing access to portable information?

Can permissions be revoked?

Can services recover from failures?

Can another developer reproduce our results?

Can people participate without advanced technical knowledge?

Can governance decisions be understood and challenged?

And can the ecosystem sustain its operations without becoming dependent on a single powerful actor?

These questions are more difficult than counting accounts.

They are also much more relevant to our stated objective.

Conclusion: The future does not need another digital empire

I do not believe that building a decentralized future means replacing today's dominant platforms with MyZubster as another dominant platform.

That would reproduce the same fundamental problem.

Our ambition is to investigate an ecosystem where independently managed applications, digital identities, creative projects and verifiable records can cooperate through open interfaces.

The collaboration with Nicola is our starting point.

His software remains independently developed.

Our VPS provides the current coordination infrastructure.

The Node Bridge establishes a limited technical connection between these environments.

Local AI helps explore how information might remain under participants' control.

The comic makes the journey understandable beyond technical documentation.

And our knowledge-proof experiments investigate how development work and learning might leave inspectable records.

We are not yet operating a decentralized national network.

We are building and testing the components that might eventually make such a network possible.

The next milestone is simple, concrete and essential:

One authenticated request. Two independent computers. A verified result.

If we can reproduce that successfully, document its limitations and allow others to build on it, we will have something more valuable than another technological promise.

We will have the beginning of an open, testable approach to digital cooperation.

And every future step will have to earn its place through evidence.


Explore MyZubster

MyZubster Open Ecosystem
https://github.com/MyZubster-Ecosystem/myzubster

Nicola / N4K48 — Independent MVP
https://github.com/nicolaususnicola-lgtm/myzubster-mvp

N4K48 Comic Series
https://github.com/nicolaususnicola-lgtm/myzubster-mvp/tree/main/docs/n4k48-comics

Knowledge-Transfer Documentation
https://github.com/nicolaususnicola-lgtm/myzubster-mvp/blob/main/knowledge/KNOWLEDGE-TRANSFER-2026-09-18-DANIEL-NICOLA.md

Our Technical Development Story on DEV Community
https://dev.to/danielioni/beyond-the-platform-building-myzubster-with-local-ai-independent-nodes-comics-and-verifiable-kcm


*Project status: October 4, 2026. This article presents a research and development vision. Institutional partnerships, national deployment,

🔥 Join developers growing publicly
Share your knowledge, build in public, and grow your developer presence with a global community.

More Posts

How AI Is Changing Web Development, and What Developers Still Need to Understand

Daniel Decker - Nov 10

The Sovereign Vault — A Comprehensive Guide to Protocol-Driven AI

Ken W. Algerverified - Jun 4

AAIF Hits 10 Projects. Its CTO on What to Adopt Now and the Security Gaps Left Open

Tom Smithverified - Oct 23

Building Beyond Platforms: How MyZubster and N4K48 Are Connecting Independent Software, AI, Comics

Myzubster - Oct 4

ERC20 Edge Cases Every Smart Contract Engineer Should Know

BinnaDev - Jun 24
chevron_left
4.4k Points • 181 Badges
Rimini
112Posts
17Comments
33Connections

Related Jobs

View all jobs →

Commenters (This Week)

6 comments
4 comments
1 comment

Contribute meaningful comments to climb the leaderboard and earn badges!