Marble Evolution DAPP — Reversible Upgrades + Legendary Slide Retrofits for Racing Games
Core Vision
Players own marbles as lasting assets. They race them in an online game that sends evolution seeds, gold coins, and special flags. The DAPP receives those sends, logs every change, and lets owners expand or reallocate the marble’s capabilities over time. Certain combinations trigger legendary events that travel back with the marble and, for one race only, let it temporarily reshape the slide it runs on. The result is long-term ownership with real agency: marbles grow, adapt, and occasionally rewrite the race itself.
Game Side (team to build and run)
• Online marble racing client with physics-driven slides and variable track conditions.
• Race modes that award seeds, gold coins, and evolution materials.
• Clean integration points: pull current marble state from DAPP at race start, push results and new seeds back after finish.
• Special “Legendary First Run” mode activated only when the DAPP sends a retrofit flag — the slide dynamically adopts the marble’s full current upgrades (shine, pattern, wax coat, weight, placement config) for that single race instance.
• Economy and progression balanced around the DAPP’s reversible mechanics so players stay engaged across many races instead of one-way power creep.
DAPP Side (we provide architecture, contracts, and state logic)
Marbles exist as owned on-chain assets with two layers:
• Base data sent from the game (immutable core + initial evolution seed).
• Evolution Log that records every shine, pattern/color, wax/machine-wax coat, weight shift, and placement configuration.
The DAPP adds expansion options the original game seed did not contain, and it continuously saves every player choice back to the marble.
A gold coin sent with the marble lets the owner prune specific past entries from the log and reallocate that capacity to new upgrades on the same marble or another. This creates reallocatable investment paths rather than permanent additive locks.
When the game sends particular upgrades plus a legendary flag, the DAPP registers a one-time Retrofit event. That event returns with the marble. On the first race the game consumes it and applies the marble’s complete current state to the slide itself. After that race the event closes. Only the game controls when legendary flags are issued; the DAPP simply records and forwards the triggered state.
All evolution history persists. Visual metadata (layered shines, patterns, surface wax, weighted appearance) can live on IPFS so the evolved marble looks distinct in both game and DAPP interfaces.
Why the split works
The game team focuses on racing feel, track variety, economy tuning, and live operations. The DAPP team owns ownership, state integrity, reversible evolution, and the legendary bridge that makes individual marbles feel consequential. Players experience expanded options through the DAPP layer while the game retains balance control via what it chooses to send.
Monetization & Longevity Hooks (shared)
• Gold coins as the reallocation currency create ongoing sinks and secondary markets.
• Legendary retrofits become rare, witnessed moments that drive social proof and demand for high-evolution marbles.
• Persistent ownership across seasons or future game modes keeps value alive without forcing constant new mints.
This structure turns a simple racing loop into a living collection system where every marble carries visible history and occasional world-altering potential.
We hold the full DAPP spec, state transition tables, and contract outlines ready to hand off or co-develop with the game team. They take the client, visuals, and operations. We keep the marble lattice and bridge logic.
Current status
DAPP foundation built. Game bridge can already call the functions and listen to events. Marbles carry persistent, resettable, legendary-capable state on Nervos.