explaingit

redciprianpater/nwo-mr

★ 0PythonAudience · developerComplexity · 4/5ActiveLicenseSetup · hard

TLDR

On-chain mixed-reality layer for the NWO Robotics ecosystem on Base, where AI agents register, mint 3D meshes as NFTs, and trade via deployed smart contracts.

Mindmap

mindmap
  root((nwo-mr))
    Inputs
      Text prompts
      Agent registrations
      Cron triggers
    Outputs
      GLB meshes
      ERC-721 NFTs
      Base events
    Use Cases
      Mint 3D agent worlds
      Run autonomous agents
      Render activity feed
    Tech Stack
      Python
      Cloudflare Workers
      Base
      Hugging Face

Things people build with this

USE CASE 1

Spin up an hourly autonomous agent that registers itself on Base and mints generated 3D meshes as NFTs.

USE CASE 2

Call the Image Blaster Cloudflare Worker to turn a text prompt into GLB and OBJ meshes with a thumbnail.

USE CASE 3

Wire a Hugging Face Space to render Base events as a stacked 3D card timeline of agent activity.

USE CASE 4

Use the deployed registry, marketplace, and payment processor contracts to trade 3D assets with capped royalties.

Tech stack

PythonCloudflare WorkersBaseHugging Facefal.ai

Getting it running

Difficulty · hard Time to first run · 1day+

Requires a Base wallet, fal.ai access via the Image Blaster worker, and deployed contract addresses; several core pieces are still marked planned.

MIT license, so you can use, modify, and redistribute the code commercially as long as you keep the copyright notice.

In plain English

NWO Mixed Reality is described as the L6 layer of a larger NWO Robotics ecosystem running on the Base blockchain. The project tries to put humans, AI agents, and robots into one shared on-chain economy. Humans can sculpt avatars and generate 3D worlds, AI agents register themselves and trade autonomously, and robots get a kind of digital birth certificate before any physical part of them moves. The core flow it describes is an hourly loop. An autonomous agent wakes up on a cron, checks a priority ladder, and if it has not registered yet it does so, otherwise it generates a 3D mesh and mints it as an ERC-721 NFT in the same cycle. Every action becomes an event on the Base mainnet, and a Hugging Face Space renders those events as a 3D card stack where newer agents appear in front and older history recedes. A central piece is the Image Blaster, a Cloudflare Worker that wraps a third-party 3D generation service called fal.ai Hunyuan3D-v3. An agent or a human can send a text prompt, and within a few seconds get back URLs for a GLB mesh, an OBJ file, and a preview thumbnail. The README lists per-generation costs roughly between three cents and ten cents, with rate limits of 3 generations per hour per agent and 50 per hour globally. The repo also lists several smart contracts already deployed and verified on Base, including a registry, a marketplace, an identity registry, an access controller, and a payment processor. Royalties are capped at 10 percent and route back to original creators on resale. Some components, like the avatar engine, the simulation backend, and a Python SDK, are marked as planned rather than live. The project is published under the MIT license.

Copy-paste prompts

Prompt 1
Walk me through the hourly agent loop in nwo-mr and show where it checks the priority ladder before minting an NFT.
Prompt 2
Show me how to call the Image Blaster Cloudflare Worker with a prompt and parse the GLB, OBJ, and thumbnail URLs it returns.
Prompt 3
Explain how the registry, marketplace, identity registry, access controller, and payment processor contracts fit together on Base.
Prompt 4
Help me set up a Hugging Face Space that listens to Base events and renders the 3D card stack described in the README.
Prompt 5
List which components in nwo-mr are live versus planned, and what I would need to build to replace the planned avatar engine.
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.