Aiman Malikk

@Pixels I remember the early days when I first stepped into Pixels. It felt different from most games I had tried. Here was this open world on the Ronin Network where I could farm, explore, meet friends, and actually build something that felt like my own little corner of a digital universe. No heavy tutorials, no overwhelming complexity. Just land to tend, crops to grow, animals to raise, and a social vibe that made logging in each day enjoyable.
What started as a casual farming experience quietly grew into something much larger, and along the way, the team behind it learned hard lessons about what keeps players coming back and what breaks a game economy.
I have spent time thinking about why so many play-to-earn projects struggle. They launch with big promises of rewards, attract crowds quickly, but then face bots farming endlessly, economies inflating out of control, and loyal players watching value drain away.
The cycle repeats: hype builds, systems get exploited, and eventually interest fades. I saw this pattern enough times to understand it is not just bad luck. It comes from rewarding the wrong behaviors at the wrong moments without real tools to measure or adjust.
That is where the journey from Pixels to Stacked begins. The team did not set out to build another rewards app. They lived through the challenges inside their own game. Pixels started as a social casual experience focused on farming and creation, but to make it sustainable they had to experiment constantly with how rewards flowed to players.
Over time they processed hundreds of millions of individual rewards across millions of players. Those experiments taught them what actually moved the needle on retention, how certain rewards influenced spending, and why some players stayed for months while others left after a few days.
I like to picture it like building a house. You can slap together walls and a roof, but if the foundation is weak, the whole thing shifts when the weather turns. Early reward systems in Web3 games often felt like that: quick to launch but fragile under real use. The Pixels team kept refining their approach.
They looked at player data closely, not just total numbers but behaviors by cohort, by day, by activity type. They asked simple but tough questions. Why do some dedicated players reduce activity between day three and day seven? What habits show up in users who keep playing past day thirty? Which small actions in the game seem to link with longer-term engagement?
Those questions led to building infrastructure that could answer them in practice, not just theory. Stacked grew directly out of that work. It is a rewarded LiveOps engine, meaning it helps game teams run live operations with targeted rewards.
The core idea is straightforward: deliver the right reward to the right player at the right moment, then check whether that reward actually improves key outcomes like how long people play, how much they spend, and their overall lifetime value in the game.
What makes this feel real to me is that it was tested inside Pixels first. The system helped drive meaningful revenue for the game, reported in the range of twenty-five million dollars or more from the rewarded systems they developed.
That number matters because it shows the approach was not designed in a meeting room or a whitepaper. It came from production, from handling real adversarial conditions where bots and farmers test every weakness. Fraud prevention, anti-bot measures, and behavioral analysis at scale are not features you add later. They take years of live data and iteration.
On top of the reward engine sits an AI game economist. I think of this layer as a thoughtful advisor rather than a flashy tool. It analyzes player cohorts, spots patterns in churn, and surfaces experiments worth trying next.
For example, it might highlight that whales tend to slow down in a certain window and suggest a targeted reward that could re-engage them without overpaying everyone. Or it could point out mechanics that loyal users engage with early and recommend ways to introduce those to newer players.
The point is not automation for its own sake but giving studios faster insight to action inside the same platform.
I appreciate how this shifts the conversation away from generic quest boards. Most games can add a list of tasks and hand out points. Fewer can build a system that survives at scale when thousands or millions of players interact with it daily. Stacked carries that experience. It already powers rewards in Pixels and related experiences like Pixel Dungeons and Chubkins.
The infrastructure includes strong fraud resistance because the team learned exactly where leaks happen and how to close them without frustrating real players.
For players the experience aims to feel fair. Instead of idle timers or spammy tasks, rewards tie to actions that genuinely matter inside the game world. You might earn crypto, cash, or gift cards for meaningful progress, not just showing up. That changes the dynamic. Studios already allocate budgets for user acquisition. With a system like this, more of that spending can flow directly to players who engage deeply, creating a loop where value returns to the community in a measurable way.
The role of the $PIXEL token fits naturally into this broader picture. It started as the currency at the heart of the Pixels ecosystem, used for staking, progression, and rewards. With Stacked, it gains flexibility as a cross-game loyalty and rewards mechanism. At launch many rewards may still appear in PIXEL but the system is designed to support multiple types over time. This expands utility without forcing every new game to invent its own token. More games joining means more surfaces for demand, but the foundation remains the battle-tested engine from Pixels.
I have thought a lot about what makes infrastructure valuable in this space. It is not the loudest announcement or the fanciest interface. It is the quiet reliability that comes from years of fixing broken incentives.
Stacked positions itself as B2B infrastructure for other studios rather than tying its fate to any single title. That changes the risk profile. Success does not depend on one game exploding in popularity. It depends on delivering tools that help many games run healthier reward programs.
From my perspective the realism here matters. Play-to-earn does not have to be an all-or-nothing gamble. When done with careful design, data-driven adjustments, and respect for player behavior, it can support sustainable economies.
Pixels showed that a social farming game could grow while learning these lessons in public. Stacked packages that learning so other teams do not have to repeat every mistake.
I see this as part of a longer evolution. Games have always needed live operations to keep communities alive. Web3 adds ownership and real-value layers that make those operations more complex but also more powerful. By focusing on targeting, measurement, and insight, Stacked tries to make the complex part manageable.
Players get rewards that feel earned. Studios get clearer return on the budgets they already spend. And the ecosystem around $PIXEL gains depth as it moves from powering one world to supporting many.
Building this took time. There were failed experiments, data that surprised the team, and adjustments made under live pressure. That history gives the system its strength. When someone says the rewards engine works, the evidence sits in the hundreds of millions of rewards already distributed and the revenue it helped generate. It is not abstract. It is production-hardened.
As I look at where things stand, I feel the shift is practical rather than revolutionary in tone. More value can reach players directly when systems are built thoughtfully. More studios can experiment with rewards without fearing immediate economic collapse.
And players in games like Pixels can continue enjoying the farming, exploration, and creation while knowing the backend works to keep things balanced.
This journey from a single social farming game to a broader rewards infrastructure shows what consistent iteration can achieve. I have come to respect the hard, unglamorous work of tuning economies so they last.
Stacked represents that work made usable for others. It keeps the focus where it belongs: on players who show up and engage, on data that reveals real patterns, and on systems that improve with experience rather than break under it.
#pixel $PIXEL #Pixel