🚀 DEV UPDATE — Nico Comics × MyZubster
Over the last few days, we moved from an idea to something people can actually open, query, test, and verify online.
Nico Comics × MyZubster started as a pilot exploring the connection between comics, software development, digital identity, Zorgax, and — eventually — NFTs and Neon Plaza.
Here’s what we’ve built so far.
🎨 Nico Comics takes shape
We created the first 3 comic boards in the N4K48 × MyZubster series:
01 — From a Software Idea to the Metaverse
02 — The Software Takes Shape
03 — Towards Neon Plaza
The boards are now organized in a public catalog with metadata, individual records, and explicit verification states.
The first board has been identified as:
NFT_CANDIDATE / PROPOSED_FOR_REVIEW
But that does not mean an NFT has already been minted.
Its rights status remains:
TO_VERIFY
We are not claiming a contract address, token ID, transaction hash, or any other blockchain event that we cannot verify.
🧠 We built a Zorgax integration layer
The pilot now exposes a read-only adapter that allows Nico Comics to be queried through four explicit actions:
gallery
detail
candidate
next_steps
This means an assistant such as Zorgax can retrieve the gallery, inspect a specific comic, identify the proposed NFT candidate, and explain the next steps.
No automatic minting.
No wallet operations.
No payments.
No catalog modifications.
First we verify. Then, if appropriate, we move something on-chain.
🌐 We deployed the project publicly
The service is now running on Render:
https://myzubster-mvp.onrender.com
The deployment is connected to the project’s GitHub repository and automatically updates from commits to main.
We also made the public endpoint configurable through:
NICOLA_COMICS_BASE_URL
without hardcoding localhost addresses or storing secrets in the repository.
🧪 Then we automated verification
We built a public smoke-test script that does more than test the application locally.
It actually calls the deployed HTTPS service.
Our GitHub Actions pipeline verified:
✅ Public catalog reachable
✅ All 3 N4K48 boards present
✅ gallery working
✅ detail working
✅ candidate working
✅ next_steps working
✅ Correct candidate: n4k48-comic-001
✅ rights_status = TO_VERIFY
✅ No fabricated on-chain claims
The result:
PUBLIC PILOT VERIFICATION: PASS
The same CI run also completed 25 software tests and the Docker verification successfully.
🛠 And we already found real production bugs
While turning the old landing page into the new Nico Comics website, the comic images were not loading.
Instead of continuing to change the frontend blindly, we inspected the deployment logs.
The server showed the real problem:
HTTP 404
for the comic image requests.
We traced the issue and changed the way those assets are served.
That is exactly the development loop we want this pilot to follow:
build → deploy → observe → verify → fix.
🔗 The next boundary: public MyZubster Zorgax
We also identified the integration point inside the public MyZubster Zorgax architecture and prepared a minimal read-only bridge proposal.
The end-to-end flow we want to prove is:
Public Zorgax → gallery → detail/card → image → candidate → rights/on-chain status → next_steps
We are not claiming that this E2E integration is complete yet.
The upstream bridge still needs to be applied and deployed on the MyZubster side, followed by a real public end-to-end test.
🎯 Where we are now
Nico Comics is no longer just an idea or three images.
We now have:
comics → catalog → API → Zorgax adapter → public deployment → Docker → automated tests → CI → HTTPS verification → public website
And, more importantly, we are trying to follow one simple rule:
Don’t claim something is complete unless we can prove it.
The next milestone is connecting the public MyZubster Zorgax flow and completing the full end-to-end verification.
After that, we can start seriously exploring the path:
Nico Comics → provenance → NFT proof → MyZubster → Neon Plaza.
🧑💻 N4K48 × MyZubster — Pilot 2026
