MyZubster Visual is not designed to be just another image gallery.
It is the visual, storytelling and provenance layer of the MyZubster ecosystem.
The idea is to connect real-world experiences, digital artwork, AI agents, robotics, open-source development and bounty rewards through assets that can be publicly inspected and cryptographically verified.
GitHub:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual
Why MyZubster Visual Exists
Digital ecosystems generate a huge amount of visual material:
AI-generated artwork
photographs
robot identities
diagrams
dashboards
comic panels
maps
technical concepts
documentation
promotional graphics
The problem is that these assets often become disconnected files.
An image gets uploaded somewhere, copied somewhere else, renamed, modified and eventually nobody knows exactly which version is canonical.
MyZubster Visual approaches the problem differently.
Instead of treating an image only as content, we treat it as an artifact.
An artifact can have:
Asset ID
Filename
Category
Repository path
File size
MIME type
SHA-256
Metadata
Publication status
Bounty reference
Verification status
This creates a bridge between creative work and software-style version control.
The Basic Architecture
At a high level, the pipeline looks like this:
REAL WORLD / DIGITAL CREATION
↓
CAPTURE
↓
VISUAL ASSET
↓
METADATA
↓
SHA-256
↓
GITHUB REPOSITORY
↓
MYZ BOUNTY
↓
VALIDATION
↓
APPROVAL
↓
SETTLEMENT
The important idea is that creation and payment are separate events.
Publishing a file does not automatically mean somebody gets rewarded.
Verification comes first.
The GitHub Repository
The public repository is:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual
Assets can be organized by category.
For example:
assets/
├── comic/
└── bots/
metadata/
├── comic/
└── bots/
This gives us a simple separation between the actual visual artifact and the information required to verify it.
- The Cyberpunk Discovery Series
One of the first experiments is the MyZubster Cyberpunk Discovery Series.
The concept is to transform experiences, discoveries and ecosystem activity into visual storytelling.
The current collection contains eight published assets.
Daniel Combat Concept
Manifesto Neon
Daniel Chronicler
Alliance
Real Life to Story
Photos Evidence Dashboard
Roadmap
Visual Catalog Dashboard
- Cryptographic Integrity
Putting an image on GitHub is useful, but we wanted another layer of verification.
For that reason, the assets are associated with SHA-256 hashes.
A SHA-256 hash works like a digital fingerprint.
For example:
visual.png
↓
SHA-256
↓
c98e8612e0b13aa57c01154bcd1b0af...
If even a tiny part of the file changes, its SHA-256 changes.
That allows another system to download an artifact later and verify that it is exactly the expected file.
The comic integrity inventory is public:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/blob/main/metadata/comic/comic-sha256.txt
And its manifest is available here:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/blob/main/metadata/comic/comic-manifest.json
- Machine-Readable Manifests
Hashes alone are not enough.
Applications need context.
That is why MyZubster Visual also uses machine-readable manifests.
A simplified asset record looks like this:
{
"asset_id": "MYZ-BOT-007",
"filename": "space-station-ai.png",
"name": "Space Station AI",
"category": "ai-bot-avatar",
"mime_type": "image/png",
"repository_path": "assets/bots/space-station-ai.png",
"status": "published",
"metadata_ready": true
}
The real manifest additionally contains properties such as file size and SHA-256.
This means an application does not need to understand the visual itself to know what the artifact represents.
It can parse the JSON.
- AI & Bot Avatars
Another part of MyZubster Visual is the AI & Bot Avatar Collection.
We currently have nine canonical visual identities:
MYZ-BOT-001 — ClowBot
MYZ-BOT-002 — Crawler Bot
MYZ-BOT-003 — EVA IONI
MYZ-BOT-004 — GitHub Bounty Bot
MYZ-BOT-005 — MyZubster AI Bot
MYZ-BOT-006 — Notification Bot
MYZ-BOT-007 — Space Station AI
MYZ-BOT-008 — Telegram Bot
MYZ-BOT-009 — Verifier AI
You can browse them here:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/tree/main/assets/bots
Their complete machine-readable manifest is here:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/blob/main/metadata/bots/bots-manifest.json
And the SHA-256 inventory:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/blob/main/metadata/bots/bots-sha256.txt
- Verification
Before publishing the metadata, we verified every bot asset against the generated manifest.
Conceptually, the verifier performs:
actual_hash = sha256(file)
expected_hash = manifest["sha256"]
if actual_hash == expected_hash:
print("OK")
else:
print("FAIL")
For the nine current bot assets, verification returned:
OK MYZ-BOT-001
OK MYZ-BOT-002
OK MYZ-BOT-003
OK MYZ-BOT-004
OK MYZ-BOT-005
OK MYZ-BOT-006
OK MYZ-BOT-007
OK MYZ-BOT-008
OK MYZ-BOT-009
That distinction matters.
We are not simply saying that an asset exists.
We can test whether the bytes match the recorded artifact.
- Connecting Visual Assets to MYZ Bounties
This is where MyZubster Visual becomes part of a larger system.
Visual contributions can be connected to MYZ Bounties.
The current Cyberpunk Discovery Series bounty is available here:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/issues/2
The current AI & Bot Avatar Collection bounty:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/issues/3
The latter currently has a proposed reward of:
750 MYZ
and has reached:
VALIDATED
But VALIDATED does not mean PAID.
This is intentional.
- Upload ≠ Payment
One of the most important principles in the bounty architecture is:
UPLOAD ≠ PAYMENT
A contributor should not receive a payment simply because a file appeared in a repository.
The proposed lifecycle is:
PROPOSED
↓
VALIDATED
↓
APPROVED
↓
ACTIVE
↓
SUBMITTED
↓
UNDER_REVIEW
↓
VERIFIED
↓
REWARD_RECORDED
Each transition has a different meaning.
For example, VALIDATED can establish that the expected artifacts and integrity information exist.
APPROVED is a separate decision about the bounty and reward.
VERIFIED establishes that the required contribution passed its verification rules.
Only after the appropriate settlement process should the reward be recorded.
This separation is important for preventing accidental or duplicate payments.
- Why GitHub?
GitHub gives this experiment several useful properties immediately.
Public history
Changes are recorded through commits.
Versioning
We can see when an asset or manifest changes.
Issues
Bounties can be represented as auditable work items.
Automation
Future verification can run through CI or dedicated agents.
Open collaboration
Developers and creators can inspect the same artifacts.
The repository therefore becomes more than storage.
It can function as part of the provenance layer.
- From Real Life to Cyberpunk Storytelling
The long-term idea behind the Discovery Series is especially interesting.
Imagine somebody exploring a city using MyZubster.
They discover a location.
They take a photograph.
The photograph contains useful metadata.
The discovery is registered.
Evidence is verified.
That experience can then become part of a visual story.
The pipeline becomes:
REAL LIFE
↓
EXPLORE WITH MYZUBSTER
↓
DISCOVER
↓
CAPTURE EVIDENCE
↓
VERIFY
↓
CREATE
↓
CYBERPUNK STORY
↓
BOUNTY
↓
REWARD
Instead of inventing an entire digital universe independently of reality, parts of the fictional universe can emerge from real experiences.
- Real-World Evidence
This opens another important direction for MyZubster Visual.
Photographs do not necessarily need to be treated simply as pictures.
They can become evidence artifacts.
Potential metadata can include:
{
"asset_id": "MYZ-PHOTO-...",
"timestamp": "...",
"location": {
"latitude": "...",
"longitude": "..."
},
"sha256": "...",
"source": "...",
"verification_status": "..."
}
Not every photograph will contain every field, and location data should only be published when appropriate and intended.
But the architecture allows verified real-world observations to be connected with the digital ecosystem.
- Future Automation
The next stage is reducing manual work.
A future ingestion pipeline could perform:
UPLOAD
↓
DETECT FILE TYPE
↓
EXTRACT SAFE METADATA
↓
CALCULATE SHA-256
↓
ASSIGN ASSET ID
↓
GENERATE MANIFEST ENTRY
↓
CHECK DUPLICATES
↓
REGISTER ARTIFACT
↓
LINK BOUNTY
↓
REQUEST VERIFICATION
Agents could perform parts of this process.
For example:
Crawler Bot could discover resources.
Verifier AI could participate in artifact validation.
GitHub Bounty Bot could connect repository activity with bounty state.
Notification Bot could report lifecycle changes.
The avatars we are publishing now can therefore represent components of an eventual operational system.
- The Bigger Vision
MyZubster Visual sits at the intersection of several areas:
MYZUBSTER VISUAL
│
┌──────────────┼──────────────┐
│ │ │
AI STORYTELLING ROBOTICS
│ │ │
└──────────────┼──────────────┘
│
REAL-WORLD DATA
│
VERIFICATION
│
MYZ BOUNTIES
│
COMMUNITY
The goal is not merely to generate more content.
The goal is to make digital artifacts organized, attributable, verifiable and usable by both humans and software.
- Community Participation
The community bounty concept is available here:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/issues/1
The model we are experimenting with is simple:
Explore something.
Document it.
Create something from it.
Publish the artifact.
Verify the contribution.
Connect it to a transparent bounty workflow.
Over time, different contributors could build different stories, characters, discoveries and visual collections while sharing the same verification infrastructure.
What's Next?
The current repository is only the beginning.
The next technical steps include expanding:
automated metadata generation;
real-world photo evidence;
geospatial discovery artifacts;
duplicate detection;
bounty verification;
contributor attribution;
visual catalog APIs;
AI-agent integration;
robotics-related visuals;
automated validation;
settlement records;
public dashboards.
The important part is that the foundation is already inspectable.
The assets are public.
The metadata is public.
The hashes are public.
The bounty workflow is public.
That gives us something concrete to build on.
Explore MyZubster Visual
Main repository:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual
Cyberpunk Discovery Series:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/issues/2
AI & Bot Avatar Bounty:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/issues/3
Community Discovery Series:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/issues/1
Bot Manifest:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/blob/main/metadata/bots/bots-manifest.json
Comic Manifest:
https://github.com/MyZubster-Ecosystem/MyZubster-Visual/blob/main/metadata/comic/comic-manifest.json
MyZubster Visual
Real world → Evidence → Visual → Verification → Bounty → Ecosystem
Top comments (0)