Stable identifiers point to explicit, versioned records; media changes never silently rewrite an owned edition.
Platform whitepaper Version 2.1.0 · September 2026
One world.
Every asset works.
MUZIKAZ World connects playable characters, mapped land, creator tools, reusable Builder packs, 3D and AR collectibles, toys, streetwear, retail drops, audio, games, and MZK in one asset system. This paper documents what has been built, how marketplace assets move into maps and Backpacks, and how value enters, moves through, and leaves the MZK economy.
Living public referencePlatform: world@2.1.0Avatar: avatar@1.0.0Last revised: 2026-09-10
Named slots, rigs, animations, and permissions make every approved character predictable to the engine.
Rarity creates identity and variety—not automatic competitive dominance.
Content hashes, approval status, and server-side authorization protect the path from catalog to session.
01 · The connected platform
From character file to living creative economy.
The project is designed as a loop rather than a set of isolated storefronts. A character can begin as a 3D model, become a playable avatar and AR collectible, appear on a physical product, headline a timed drop, live in a Backpack, and activate experiences on owned land. Creator output returns to the same catalog and market.
Connected markets
The Model Market presents Originals, Crew, Chaos, Beasts, Legends, New Legends, world packs, and campaign products. The Builder Market separately filters reusable, game-builder assets that can be bought, carried, and placed.
Browse the model market →Drop Backpack
A single inventory for avatars, lands, props, wearables, pets, vehicles, purchases, loadout entitlements, and assets listed for member-to-member trade.
Open Backpack →Creator stack
Land-gated model, image, and environment publishing; a live merch designer; asset assignments; approval workflows; reusable audio; and world placement tools.
Enter creator tools →World experiences
Walkable 3D environments, designated avatars, multiplayer presence and chat, RAD-TOX play, quests, a Voice3 mixer, and web-based AR previews.
Explore in 3D →Delivery languageBuilt means a working surface or server route exists.Policy means the accounting or governance rule defined here.Planned means no present entitlement is implied.
02 · World mapping & land
Every place resolves to a map, deed, and world record.
Build, publish, host
A canonical land deed unlocks avatar, asset, game, and environment upload gates. Owner and delegated roles control editing and placement; visitors retain public exploration and play. A deed is a world permission object, not merely a map picture.
Connected places
Volt City, Skyline Deck, Echo Gardens, Crew Plaza, Studio Ridge, Neon Docks, Bassline Badlands, and Pixel Peaks form the fixed route. Public-area claims are deeds inside those areas; dynamic wild-land claims may add one owner pin without inventing a fixed global supply.
- FundAcquire MZK after verified payment
- ClaimAtomic MZK debit + deed issue
- PinCorrelate profile, Backpack, space, pixel
- BuildPlace approved assets and environments
- OperateHost games, social rooms, stores, drops
Canonical-state rule: browser storage is only a display cache. Land ownership, MZK debits, deed assignment, listings, and world memory resolve through persistent wallet records. A permanent world object is valid only when profile, Backpack, space, map pixel, and owned asset agree.
Eight fixed district pins and seven routes provide the shared navigation frame. Selecting a beacon resolves district details and its connected market destination.
Five public-area plots expose availability and deed state. A claim is a plot inside its named district, not an extra district or an unsupported scarcity claim.
A player can set a spawn point, while eligible wild-land owners can add one owner pin. Profile, Backpack, home space, deed, and pixel remain correlated.
A world holds independently configurable asset instances. Placement records point back to the purchased Builder asset instead of copying or changing its source record.
03 · Builder Market, Backpack & maps
Buy once. Configure instances. Publish a version.
The Builder stack turns marketplace inventory into reusable world components. Authenticated members, qualifying builders, land owners, and supported MZK accounts can enter without a Genie Bottle gate; individual actions remain controlled by server-issued permissions.
Find
Filter listings by category and asset_usage = game_builder. A listing identifies the source asset, creator, price, license context, and availability.
Acquire
An idempotent purchase debits the buyer, credits the seller, closes the listing when required, and adds the asset reference to the buyer’s Builder Backpack.
Place
Authorized land and world roles create placement instances with their own position, rotation, scale, and configuration while preserving source provenance.
Map
The Game Space Builder assembles avatars, enemies, rewards, props, vehicles, pets, weapons, buildings, and land into a spawn manifest.
Publish
Drafts can be saved and exported; publishing spends the displayed Builder Coin cost and freezes a versioned gameplay manifest.
Development inventory
Builder assets live beside land/world records and placed instances. Creators can import or create an asset, list it for MZK, cancel their listing, and retain a durable transaction trail.
Enemy and reward roles
Map authors explicitly classify spawnable avatars as player, enemy, or reward content. A model does not become hostile, collectible, or valuable merely because it exists in a pack.
Two builders, two settlement layers.
The server-backed Builder Market, purchases, Backpack, and placement records are canonical account data. The current Game Space Builder composes, saves, exports, and publishes manifests in the member experience; its displayed MZK and Builder Coin charges describe that builder flow and must not be represented as an on-chain burn.
04 · Packs, toys, merch & retail
Every pack states what it unlocks.
MUZIKAZ’s retail layer turns world identity into products people can wear, collect, customize, scan, and bring back into digital experiences. Product checkout and digital ownership are distinct records; a physical order does not imply token ownership unless a drop explicitly grants it.
Streetwear + accessories
Hoodies, caps, wristbands, bottles, lanyards, and keychains sit beside character-specific products, colorways, logo placements, sleeve text, and custom artwork.
Toys + display figures
Character toys, mascot figures, bottle collectibles, and the IonCore display figure extend character IP into shelf-scale products. Digital 3D previews and collection identity support the retail drop without representing guaranteed manufacturing inventory.
3D + AR collectibles
The CHAINeS browser supports numbered collectibles, synchronized model viewing, WebXR/Scene Viewer placement, and optional USDZ Quick Look assets.
Drop lab
The member studio supplies product templates, safe areas, layers, uploads, character selection, typography, color, transforms, saved drafts, and order specifications.
Current pack architecture
Builder Loadout
Starter Avatar, unrevealed avatar, Community Spot, room shell, Builder Tool Kit, Creator Market Station, and RAD-TOX gear are provisioned as durable Backpack entries.
Character + world packs
Characters can connect to compatible pets, wearables, props, vehicles, graphics, land, environments, and gaming-studio bundles without merging those asset records.
Genie Bottle rewards
$5 grants 2,000 MZK and the Black Bottle; $30 grants 5,000 MZK and adds Violet; $100 grants 13,000 MZK; $200 grants 26,000 MZK, adds Golden, and includes a custom in-game asset order.
Retail drop lifecycle
- CharacterApproved IP + model record
- DesignProduct template + safe artwork
- DropEdition, price, window, availability
- CheckoutFiat/crypto payment verification
- FulfillPhysical order and explicit digital grants
Drop integrity
Every offer should state whether it is physical, digital, redeemable, consumable, tradable, limited, made-to-order, or bundled. Scarcity claims must follow actual inventory controls. Royalties, redemption deadlines, geographic shipping, refunds, taxes, and manufacturing partners must be disclosed at the point of sale.
05 · MZK economy
Every intake and burn leaves a receipt.
MZK is the platform utility and accounting unit used to access functions—not equity, debt, a share of revenue, or a promise of appreciation. The current store quote uses 100 MZK per US dollar, with a $40 / 4,000 MZK land-purchase minimum. Quotes, bonuses, and availability remain offer terms, not market-value guarantees.
Verified payment, quest reward, admin entitlement, or received transfer creates an idempotent credit.
The wallet record stores balance, items, memory, and an append-only activity trail.
Land, cart items, creator actions, consumable refills, game actions, or market trades request authorization.
The service classifies the debit as burn, seller transfer, treasury intake, or reversible reservation.
EventAsset functionLedger treatmentCurrent status
Verified MZK purchaseFund wallet and land/market accessCredit after payment confirmationBuilt
Quest participationReward useful creator activityIdempotent reward creditBuilt
Land claimIssue deed and building permissionAtomic debit + asset grantBuilt
Backpack market tradeMove listed asset to buyerBuyer debit + seller creditBuilt
Builder Market purchaseAcquire a reusable world-building assetIdempotent buyer debit + seller credit + Backpack grantBuilt
Game map assemblyAdd spawn objects and publish a manifestDisplayed MZK item spends + Builder Coin publish costBuilt
Retail/cart checkoutPurchase product or assetDebit + receipt + explicit grantBuilt
Voice3 sound placementAdd a reusable sound to a mix1 MZK debit; undo can reverse itBuilt
Consumable refill / game actionRestore or activate item utilityConfigured debit; e.g. carrot refill or RAD-TOX useBuilt
Protocol burnRetire settled utility unitsBurn receipt + supply counter updatePolicy / planned
Value enters only after proof.
External-payment intake remains pending until network verification. Reward intake requires a unique event ID. Loadout codes are one-time credentials: activation consumes the code and materializes its assets without silently replacing existing wallet state.
Authorization precedes function.
The engine checks identity, balance, ownership, price, and request ID before changing both asset and MZK state. Duplicate requests resolve to the original result. A failed operation must not debit the wallet.
Retirement must be explicit.
A spend is not automatically a burn. Transfers credit a seller; refundable reservations remain liabilities; treasury intake remains circulating until separately retired. Only an irreversible, publicly classified retirement may be reported as burned.
{
"eventId": "mzk:settlement:<unique-request-id>",
"walletId": "<authenticated-wallet>",
"assetId": "<land-product-or-consumable>",
"amountMzk": 5,
"function": "consumable_refill",
"disposition": "burn",
"status": "settled",
"createdAt": "<ISO-8601>"
}Transparency commitment: Until a server-backed burn registry and supply counters are published, the interface must call implemented reductions spends or debits, not token burns. Future burn reporting should expose gross intake, transfers, treasury-held units, reversed spends, retired units, and net circulating change without exposing private user data.
06 · Asset function matrix
Ownership answers “what can I do?”
Designate, equip, animate, spawn, appear in multiplayer, carry traits and permissions.
Claim, pin, build, configure, delegate, publish, host, list, and transfer.
Equip to compatible slots, customize appearance, save to loadout, trade when allowed.
Place, display, interact, consume, refill, or assign to products and environments.
Equip as companions, follow the player, receive compatible consumables, appear in scenes.
Store, spawn in permitted worlds, display, and connect to future traversal rules.
Record, upload, arrange, trim, loop, mix, export, and mint through explicit flows.
Use as thumbnails, textures, posters, store tiles, product art, badges, and overlays.
Buy, customize, fulfill physically, pair with a character, and receive only disclosed digital grants.
Function metadata: each asset should declare controller, type, media, compatibility, allowed actions, world scope, transferability, consumability, quantity, cost, cooldown, expiration, approval state, and provenance. Interfaces must disable unsupported functions rather than imply them.
07 · Avatar data model
Character and instance are different layers.
Character
Black Sheep defines the creative identity: lore, licensed media, rig and animation profiles, compatible fit families, default classes, and balanced base traits.
Avatar instance
Black Sheep #0013 binds an edition to its assets, traits, controller reference, compatibility, permissions, and schema version. XP, health, location, and cooldowns remain in game state.
Identity id · characterId · name · editionMedia modelUrl · iosModelUrl · thumbnail
Control ownerId · optional tokenId · collectionPlay classes · traits · abilities
Fit rigProfile · equipmentSlotsAccess allowedWorlds · landRoles
Motion animationProfile · named actionsMetadata metadata · approvalStatus · schemaVersion
Versioning rule: an avatar ID is stable, but resolved media must be pinned by a version or content hash for deterministic playback. Breaking contract changes require a new major schema; compatible additions require a newly published schema version and migration guidance.
08 · Control and loadout
Marketplace → Backpack → Equip → Enter World.
- AcquireBuy, claim, mint, or receive
- BackpackStore a reference to Avatar ID
- DesignateSelect one active avatar
- EquipValidate slots and fit profile
- SpawnVerify, load, attach, apply
Backpack references, never duplicates
An inventory entry records the asset ID, acquisition state, and listing lock. The canonical service resolves current media, traits, and compatibility. Transfers change the controller without moving large model data.
Active avatar is a session choice
Before spawn, a trusted service authenticates the player; authorizes control and world access; checks approval status; resolves pinned media; validates the loadout; calculates effective stats; and signs a short-lived, non-transferable session snapshot.
Standard slotsHeadFaceNeckTorsoHandsFeetBackTool 1Tool 2
Compatibility rule: each item declares a fit profile such as humanoid-small or black-sheep-rig@1, allowed slots, attachment bone, offsets, and conflict groups.
Control is not assumed to mean blockchain ownership.
ownerId identifies the authoritative account in this schema. A token ID is optional provenance metadata. When an on-chain collection is used, the server must verify chain, contract, token, and current controller before granting a session.
09 · Gameplay and progression
Permanent truth and live state move at different speeds.
Provenance
- Stable avatar and character IDs
- Controller reference and optional token metadata
- Edition and immutable traits
- Creator attribution and content hash
Living state
- XP, level, health, and quest progress
- Equipped items and unlocked actions
- Achievements, cosmetics, and location
- Cooldowns and world session state
Balanced progression
Traits create roles and play styles, not pay-to-win certainty. Progression unlocks expression and access: new dances, creator quests, badges, visual effects, and optional accessory slots. Competitive modes normalize power budgets while preserving character identity.
Roles are capabilities scoped to a land or world. They are evaluated server-side and do not follow an avatar into every destination.
10 · Interoperability
A strict creator standard makes an open world possible.
glTF 2.0 / GLB, optional USDZ, declared byte and geometry budgets, PBR textures, HTTPS or same-origin URLs, collision bounds, units in meters, origin, scale, and spawn clearance.
Versioned rig profile, attachment bones, skin weights, humanoid or custom classification, neutral pose, root motion policy, and retargeting map.
Supported semantic action names include: idle, walk, run, jump, turn, interact, dance, emote, use_tool, damage, and defeat.
Creator identity, rights declaration, malware and unsafe-content scans, moderation state, SHA-256 content digest, version history, and a revocation path for compromised files.
Submitted→Automated checks→Human review→Market Approved→Published
11 · Reference contract
One standardized object for market and world.
{
"id": "avatar_black_sheep_0013",
"characterId": "black_sheep",
"name": "Black Sheep #0013",
"edition": 13,
"ownerId": "user_123",
"assets": {
"modelUrl": "/public/models/avatars/rebel%20black%20sheep.glb",
"contentHash": "sha256:<64-lowercase-hex-characters>"
},
"rarity": "rare",
"classes": ["creator", "explorer"],
"traits": { "music": 85, "creativity": 90, "speed": 65 },
"rigProfile": "black-sheep-rig@1",
"equipmentSlots": ["head", "neck", "torso", "tool1"],
"animationProfile": "muzikaz-biped@1",
"animations": ["idle", "walk", "run", "jump", "interact"],
"worldPermissions": { "allowedWorlds": ["vibeverse", "studio"] },
"tradable": true,
"schemaVersion": "1.0.0"
}Normative source: The downloadable JSON Schema is authoritative for field names, required properties, value ranges, and enumerations. Narrative examples in this document are explanatory.