Gardens, not slot machines: what OEGP taught me about onchain gamification

Most "gamified" crypto apps are slot machines wearing a quest log. Points for swapping. Streaks for trading. A leaderboard bolted onto a DEX like a spoiler on a minivan. OEGP Garden is my argument that we can do better, and this is the full written case.

The thesis under test: care mechanics beat reward mechanics.

One thing up front, because honesty is the house style: OEGP failed as a market. The original founders took the mint proceeds and left the space, and from the consumer's perspective the product was abandoned. Hold that thought, because it turns out to be the most interesting part of the whole story.

Points on a swap is not gamification. It's a coupon.

Call the loyalty-points playbook what it is: a discount program. You were going to swap anyway; now you get a cookie. Coupons don't create engagement, they rent it, and the moment the emissions stop, so does the "community."

Actual gamification changes what people want to do, not what they get paid to do. Nobody pays you to water a Tamagotchi.

The three chain-native properties worth designing games around

If you're going to build a game on a blockchain, use the materials only a blockchain has. The founding essay names three, and OEGP is a deliberate probe of all of them:

Persistence: state that outlives the session, the server, and frankly the company. A plant that keeps growing whether or not the frontend exists is a different kind of object. Shared state: everyone sees the same garden. Your plant's growth stage isn't a number in my database; it's a fact we both agree on. Provenance: the chain remembers who planted, who tended, who held through winter. History becomes a game mechanic instead of a marketing screenshot.

Points systems use none of these. A Postgres table could do the job, and usually does.

The part where the founders left

Here is what abandonment normally means in consumer software: the servers go dark, the app stops loading, and everything you built inside it evaporates. Your farm in some shuttered Facebook game does not exist anymore, anywhere, in any sense. The company was the product, so the company's exit was the product's funeral.

OEGP got abandoned and the garden did not die. The contracts kept running. The plants kept their state. Every growth stage, every tending record, every plant in all 9,888 was still sitting on Ethereum, waiting for someone to look at it. The founders left with the mint money, and what they left behind was not a corpse but an unattended garden.

That is the difference between a product and a protocol wearing a product. Because the game state lives onchain, anyone can walk in, build a new interface on top of it, and resurrect the product experience: bring the community back, and potentially find the financial success the original team walked away from. No permission needed, no acquisition, no license, no negotiation with a dead company's lawyers. The Garden App is exactly that: a stranger's interface on an abandoned game, and the game works.

This is the permissionless argument made concrete. In web2, product innovation on someone else's abandoned work is legally and technically impossible. Onchain, abandonment converts a product into a commons. The founders can leave; the garden can't be taken with them.

To be clear about both halves: the original team abandoning their consumers is a failure and deserves to be named as one. And the fact that their exit was survivable at all is a property no other software distribution model has ever offered.

A walkthrough of the greenhouse

OEGP is a collection of 9,888 dynamic botanical NFTs on Ethereum that grow through nine stages of life. The Garden App is where you live with them:

The Garden: every plant you own: species, current stage, what it needs next The species field guide: the rarity ladder runs from the 88-supply Origin Tree through Astral Lotus, Prism Bonsai, Lantern Orchid, and on down Planting and ritual flows: tending actions write to the contract, and growth stages read from it. There is no separate "game database." The contract state is the save file.

That last point is the whole architecture in one sentence. When the chain is the save file, the app becomes a lens instead of a gatekeeper. Anyone can build a different window into the same living garden, and the garden survives every one of those windows shutting down. That is persistence doing product work, not whitepaper work. The resurrection above is not a nice theory; it is this exact property, cashed in.

The conservatory, not the trading floor

The app is cream, green, and terracotta. Soft light. Botanical illustration. It looks like a greenhouse, and in a market where every product ships the same near-black dashboard with neon green candles, that is a strategic choice, not an aesthetic one. Heresy 3 from the founding essay: the interface is the strategy.

Interfaces tell users how to behave. A trading terminal says: watch the number. A conservatory says: come back tomorrow and see what's grown. Same chain, same contracts, completely different relationship. (Yes, I'm aware this site you're reading is a near-black dashboard. The difference is knowing which product calls for which.)

What actually brought people back

Not rewards. Streaks and growing things.

The retention pattern was consistent: people showed up daily to tend, check a growth stage, keep a streak alive. Care mechanics reward consistency over volume. You can't whale your way to a prettier garden, and that's precisely why tending one feels like it means something.

The industry keeps trying to buy this outcome with emissions, and the numbers keep telling the same story: token incentives rent daily active users at a price that rises forever, while care loops earn them at a price that falls. Every "engagement" chart that collapses when rewards end is the coupon thesis proving itself again. Nobody comes back daily to admire a points balance. People come back daily to something that grows.

Explore the garden at oegp-garden-app.replit.app or read the code on GitHub.

Or don't, and keep shipping quest logs. Someone has to make my case for me.