MyZubster Life is becoming an interoperability layer

Over the last few weeks, we have been working on a new part of the MyZubster ecosystem:

MyZubster Life — External Ecosystem Gateway.

The idea is simple:

Different open ecosystems should be able to interact without losing their independence.

We don't want to create another closed metaverse.

We want to experiment with a public layer where developers, creators, researchers and contributors coming from different ecosystems can voluntarily enter, build and collaborate.

And we want to do it in public.

🌍 The first external ecosystems

The initial MyZubster Life registry now includes four different integration paths.

🟢 Vircadia World

Vircadia is being explored as an external open-source metaverse interoperability target.

We have already started contributing upstream:

https://github.com/vircadia/vircadia-world/pull/17

The goal is not to absorb Vircadia into MyZubster.

The goal is to understand how independent worlds, characters and public integration boundaries can coexist.

Status:

Experimental

🔴 Decentraland SDK

We are also experimenting with the Decentraland SDK ecosystem.

Instead of starting with marketing or integration claims, we started by contributing code upstream.

Our contribution addresses authoritative CRDT state synchronization retries and includes a regression test:

https://github.com/decentraland/js-sdk-toolchain/pull/1556

This work is particularly interesting for MyZubster because distributed world state is one of the fundamental problems that interoperable digital environments eventually need to solve.

Potential future research areas include:

ECS interoperability
scene metadata
world state synchronization
portable character metadata
provenance between worlds
browser-based experiences

Status:

Experimental

🥽 Immersive Web / WebXR

A global digital environment should not depend entirely on one proprietary client.

That's why WebXR is important to us.

We started contributing to:

https://github.com/immersive-web/webxr-samples

Our current work explores a sample for visibilitymaskchange / XRVisibilityMaskChange.

WebXR potentially gives MyZubster Life something extremely important:

an open browser-based bridge into immersive environments.

Instead of requiring every user to install a specific metaverse application, parts of Life could eventually become accessible directly through compatible browsers and XR devices.

Status:

Experimental

☁️ Aruba as an infrastructure candidate

Not every external participant belongs in the same category.

Aruba is not being treated as an open-source metaverse community.

We classify it separately as an:

Infrastructure Provider

We are exploring whether European infrastructure could eventually support areas such as:

cloud
hosting
DNS
storage
certificates
geographic distribution
public Life services
infrastructure resilience

Status:

Exploratory

And this distinction matters.

Exploratory does not mean partnership.

MyZubster does not claim that Aruba, Vircadia, Decentraland or Immersive Web endorse or partner with MyZubster unless explicit evidence supports that statement.

🚪 How the Life Gateway works

People coming from external communities are not automatically imported into MyZubster.

Participation is voluntary.

The current model defines several levels.

Visitor

Explore public MyZubster Life surfaces.

No special privileges.

Contributor

Contribute through the normal public workflows:

code
documentation
characters
translations
visual content
observations
datasets
research

Creator

Build compatible experiences after normal project review.

Maintainer

A maintainer role must be explicitly granted through MyZubster governance.

Being a maintainer, developer or contributor in another ecosystem does not automatically grant privileges inside MyZubster.

And external gateways can never automatically grant administrator privileges.

🪪 Identity boundaries matter

Interoperability does not mean silently merging identities.

GitHub username
Decentraland identity
Vircadia identity
wallet
XR runtime identity
cloud-provider account

is not automatically a MyZubster identity.

If identity linking is introduced, it must be:

voluntary, explicit and verifiable.

This principle is important because interoperable systems should not become identity-harvesting systems.

Users should decide which parts of their public identity move between environments.

🔎 Provenance before federation

Another fundamental part of the architecture is provenance.

For an external integration, MyZubster should be able to record things such as:

upstream project
canonical repository
provider
version
branch
commit
license
asset license
upstream issue
upstream pull request
integration status
upstream acceptance
partnership evidence

This creates an important distinction between:

something we experimented with

and

something another project officially accepted.

🧭 A small status vocabulary

We introduced a deliberately simple vocabulary.

`exploratory`

We are evaluating something.

No integration or affiliation is implied.

`experimental`

Technical work exists, but it may still be under development or review.

`upstream_validated`

Relevant work has been accepted upstream.

Even this does not automatically mean partnership.

`partner`

Reserved for cases where explicit partnership evidence exists.

This prevents a common open-source problem:

turning a GitHub fork, issue or pull request into a marketing partnership that never actually existed.

🧬 Interoperate, don't absorb

This may be the most important architectural principle behind MyZubster Life:

MyZubster should interoperate with external ecosystems rather than absorb them.

Vircadia should remain Vircadia.

Decentraland should remain Decentraland.

WebXR should remain an open Web standard ecosystem.

Infrastructure providers should remain independent providers.

MyZubster Life can become a layer where compatible pieces meet.

🛠️ The gateway is now entering the software

This architecture is no longer only documentation.

We have started implementing a dedicated public Life Gateway in the MyZubster frontend.

The /life experience is being reorganized around:

external ecosystems
contribution entry points
integration status
upstream evidence
identity boundaries
provenance
Life roles
infrastructure providers

The source remains public:

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

And the external ecosystem policy is maintained in the repository:

https://github.com/MyZubster-Ecosystem/myzubster/blob/main/docs/LIFE_EXTERNAL_ECOSYSTEMS.md

🤝 This is an invitation, not an announcement of partnerships

If you contribute to Vircadia, Decentraland, WebXR or another open ecosystem, you don't need permission from MyZubster to inspect what we're building.

You can read the code.

Question the architecture.

Open an issue.

Propose a better interoperability model.

Build an experiment.

Or tell us why something won't work.

That's the point of building this in public.