MyZubster Development Update: Real Blockchain Anchoring, OAuth and Circular-Economy Pilots
Over the last few days, MyZubster moved forward across several technical and community workstreams: blockchain traceability, OAuth authentication, circular-economy pilots, visual documentation and institutional engagement.
Here is a developer-focused overview of what is now working and what remains to be built.
A Real Anchor on Base Sepolia
The AHP traceability prototype completed its first real blockchain transaction on Base Sepolia.
The current pipeline can:
- validate structured traceability events;
- verify Ed25519 digital signatures;
- store append-only records in MongoDB;
- calculate canonical SHA-256 event hashes;
- build a Merkle root from an event batch;
- publish that root through an EVM transaction;
- return the transaction hash, block reference and confirmation state.
The first confirmed testnet transaction is:
0x6dcf39faac6d1eabbaf0e6857ae329d41a1de74cf8320f8f9f048a2dca7ce649
The anchor was confirmed on chain ID 84532, with simulated: false.
This milestone demonstrates technical integrity and timestamping. It does not independently prove that a real-world recycling operation happened. Physical claims still require measurements, authorized operators, custody records and independent verification.
Privacy-First Traceability
The architecture keeps operational evidence off-chain.
The public blockchain receives only minimal data such as a Merkle root. It must never receive:
- names or email addresses;
- health information;
- household-level usage histories;
- precise locations of vulnerable people;
- readable consent records;
- private photographs or documents.
QR or NFC identifiers may connect physical containers or lots to public verification pages, but those identifiers must remain random and non-personal.
Gmail OAuth and Automatic Synchronization
Google OAuth has been configured for MyZubster.
The platform supports a consent-based Gmail integration using the read-only scope:
https://www.googleapis.com/auth/gmail.readonly
Automatic synchronization uses:
- explicit user consent;
- offline OAuth access;
- an encrypted refresh token;
- a stable 32-byte Base64 encryption key;
- revocable synchronization;
- protected status endpoints.
Authentication and mailbox access should remain separate. A user should be able to access MyZubster without granting Gmail permissions and connect Gmail only when the related feature is requested.
GitHub OAuth
GitHub OAuth has also been configured for identity onboarding.
The requested scopes are limited to:
read:user
user:email
The flow verifies the GitHub identity, creates a short-lived signed ticket and returns the user to the MyZubster onboarding interface.
No repository-write permission is requested.
New Visual Documentation
Several new images were added to the MyZubster Comic Universe:
- blockchain and circular recycling;
- controlled healthcare-waste traceability;
- circular community pilots;
- underground subcultures moving toward circular economies;
- Free Party culture;
- the Space Station narrative returning to real territories.
The visual material is being linked to relevant GitHub repositories such as:
space-station;I-ECO-01;urban-lab-nurse;- the main MyZubster repository.
Each README distinguishes clearly among operational evidence, pilot concepts, historical references and fictional storytelling.
An image can explain an architecture, but it cannot prove implementation or certification.
Institutional AI Discussion
MyZubster has also been invited to participate in an online institutional hearing related to the update of Italy’s National Artificial Intelligence Strategy for 2026–2028.
The submitted documentation covers:
- responsible and transparent AI;
- human supervision;
- open-source infrastructure;
- privacy-preserving services;
- environmental data verification;
- accessible community participation;
- small pilots with measurable acceptance criteria.
The invitation is an opportunity for dialogue. It is not presented as funding, endorsement or a formal partnership.
Current Development Priorities
The next technical milestones are:
- complete the full AHP event chain;
- implement QR/NFC lot linkage;
- add duplicate-scan and custody-transfer controls;
- build public Merkle inclusion-proof verification;
- test corrections and key rotation;
- introduce failed-anchor retries;
- publish reconciliation reports;
- improve the OAuth onboarding interface;
- expose Gmail synchronization status and revocation controls;
- keep documentation synchronized across repositories.
Contributors Welcome
Useful contribution areas include:
- Node.js and Express;
- MongoDB data integrity;
- EVM testnet adapters;
- JSON canonicalization and Merkle proofs;
- OAuth security;
- privacy engineering;
- accessible frontend development;
- technical documentation;
- circular-economy measurement models.
Project links:
MyZubster is still experimental, but the direction is concrete: build open systems where every claim can be classified as implemented, measured, verified, proposed or fictional.
That distinction is part of the infrastructure.