Building the MyZubster Metaverse: Sessions, Verified Identities, CI Hardening, and the Road Ahead
Description and use
MyZubster built a metaverse with verified identities, hardened session management, upgraded CI to Node.js 24, and added distributed rate limiting.
Problem
Implement a secure, verifiable metaverse where every action is tied to an authenticated session and verified identity, while modernizing CI to Node.js 24 and hardening the system against abuse.
Outcome
The project achieved a public Metaverse interface with 25 characters, 7 verified explorers, session‑based authorization, and CI upgraded to Node.js 24 without regressions.
Workflow
- Authenticate user and establish session
- Create session lease with expiration
- Resolve character ownership for session
- Authorize world action against policy
- Mutate world state
- Propagate real‑time updates
- Enforce distributed rate limiting
- CI pipeline runs with Node.js 24
- Deploy to Vercel
- Verify post‑merge workflows
Evidence
The public Metaverse page is available at: https://www.myzubster.com/metaverse
25 public characters
7 verified explorers
No blocking browser-console errors
Successful Vercel production deployment
Client → authenticated request → session credential validation → active lease verification → character ownership resolution → action policy validation → world-state mutation
We updated the affected workflows:
uses: actions/checkout@v4
uses: actions/setup-node@v4 to:
uses: actions/checkout@v5
uses: actions/setup-node@v5
All 16 workflow YAML files parsed successfully.
No affected v4 references remained.
Only files under .github/workflows were modified.
- Record date: 2026-10-19T05:56:02.570Z