Project Poke Economy is a fan systems-design concept about something Pokemon-style games have never really solved: proving that a collection was earned.
If someone has thirty rare legendary creatures, that can mean two very different things. Maybe they spent hours catching them, transferring them, resetting saves, and doing the grind again. Or maybe they used a cheat device and created the same collection in minutes.
Both collections can look identical inside the game. The difference is the story behind them.
Project Poke Economy is about preserving that story and making it useful in a real trading economy.
It imagines a decentralized system where players can trade creatures, items, and account history while client software evaluates whether that history looks earned, botted, cheated, reversed, or trusted by outside communities.
The goal is not to make cheating impossible. The goal is to make legitimacy visible.
This is a fan systems-design concept, not an official Pokemon, Nintendo, Game Freak, or The Pokemon Company project.
Purpose
The purpose of Project Poke Economy is to give earned progress a durable record.
In a normal save file, a rare creature is mostly just data. The file may tell you what the creature is, what level it has, what moves it knows, and who owns it. It usually does not prove the story behind it.
Project Poke Economy tries to attach that story to the economy itself. A creature should carry evidence about where it came from, when it was caught, how it moved between players, which clients validated it, and which communities are willing to trust it.
That makes the project less about owning a digital object and more about owning a history that other people can inspect.
Who It Is For
The player audience is anyone who enjoys collecting, trading, and showing off rare creatures, but wants the effort behind those creatures to matter. The appeal is the feeling that a hard-earned collection has visible credibility.
The developer audience is technical players who want to build the software needed for that economy to exist. They might make clients, validators, marketplaces, asset packs, servers, protocol branches, or community trust layers.
The community audience is the group around the game: trading sites, tournament organizers, validator groups, YouTubers, and players who decide which histories count as canon. Those groups should be able to publish their own trust signals without owning the entire system.
The Intended Experience
A player would start by choosing a protocol provider or community. Different providers could have different maps, rules, economies, art packs, and trust standards.
After installing a client and connecting the required account or wallet, the player would begin a familiar Pokemon-style adventure. They explore, catch creatures, earn items, trade, and save progress. In the background, the client records evidence of what happened.
When that player later visits a marketplace, a listing should show more than stats and price. It should show whether the creature appears earned, whether the history has suspicious gaps, which validators trust it, and whether there are repentance entries or other context that affects confidence.
The desired experience is still a creature-collecting game first. The proof layer should support the fantasy, not bury the player in technical details.
The Core Problem
Pokemon trading depends on trust, but most of that trust is social. A player can say they earned something honestly, but the data alone often does not prove it.
Centralized online games solve this by keeping the real game state on official servers. If a player submits impossible data, the server rejects it. If a player cheats badly enough, the operator can ban them.
That works when the operator is stable, trusted, and legally safe.
It breaks down for fan projects.
If a fan-run server ever gets big enough, it can become a target. If the server disappears, the economy disappears with it. Player history, trade records, legitimacy signals, and community work can all vanish because one service was taken offline.
Project Poke Economy starts from a different assumption: the data should survive even if one client, server, community, or organization disappears.
The Blockchain Layer
The project proposes using a blockchain as the durable record of player history.
That does not mean every entry on the chain is automatically legitimate. The chain is just the record. It can contain honest progress, suspicious progress, obvious cheating, bot activity, corrections, and competing interpretations.
That distinction matters.
A player could write a record saying they obtained millions of rare creatures in a few minutes. The chain can store that claim. But other players’ software can still reject it as non-canon, suspicious, or worthless.
In this model, the blockchain stores history. The client software interprets history.
Canon Is a Judgment
Project Poke Economy treats authenticity as a judgment made by validators, clients, and communities.
A creature or account history can be considered canon if it passes the checks that a player, marketplace, or community cares about. Those checks might include timing, route progression, event availability, encounter rules, save history, trade history, and whether trusted organizations have signed off on the account’s behavior.
This makes cheating less about deleting bad data and more about labeling bad data.
If someone cheats, the system does not need to pretend the event never happened. It can remain in the record with enough context that other clients know how to treat it.
Anti: Paying for Signal
The original spec introduces the idea of “anti”: optional extra fees attached to a save entry.
Anti is not proof of honesty by itself. It is a visible signal.
If every save update has a cost, then mass-producing fake history becomes more expensive. A bot can still play the game, and a cheater can still write data. But the cost, timing, and pattern of those updates become part of the public evidence that other software can evaluate.
This is useful because botting is one of the hardest problems in this kind of economy. A bot can grind for hours, follow valid game rules, and create a history that looks more legitimate than an obvious cheat.
Anti does not solve that completely. It adds friction and gives validators another signal to weigh.
Trust Layers
The system also needs trusted organizations.
A community, marketplace, tournament group, or client developer could publish its own reputation layer on top of the raw blockchain data. That layer might say, “We observed this player during this time period, and we believe this account was not botting.”
Those organizations would not own the economy. They would only sign their interpretation of it.
That creates a useful failure mode. If one organization shuts down, its signatures and historical claims can still be read. Other organizations can continue building on the protocol. Players are not forced to start over just because one server or client disappears.
Client Software Matters
In this project, the client is not only a game launcher. It is also a trust interpreter.
When a player trades, buys, sells, or views a collection, their client should explain what it sees:
- whether the creature appears to follow valid progression
- whether the account has suspicious timing
- whether trusted organizations have backed the account
- whether the account has repentance entries
- whether a marketplace or app is applying its own rules honestly
That last point is important. The economy should not only exist inside one game client. Websites, trading tools, and marketplaces should be able to participate too. Each one needs to surface legitimacy clearly, because hiding risk would make the whole economy worse.
Repentance Entries
The spec also includes repentance entries.
If a player cheats, or if client software bugs out and marks honest data as cheated, the player needs a way to roll back to a previous clean point. A repentance entry would mark that correction in the public history.
That should not automatically make a player look bad.
Complex clients will have bugs. Honest players can get flagged incorrectly. A healthy economy needs a way to recover from mistakes without pretending they never happened.
The useful signal is not simply “this account has a repentance entry.” The useful signal is what happened, how often it happened, what was reverted, and whether trusted clients or communities agree with the correction.
Game Engine And Assets
Project Poke Economy separates three things:
- the protocol and authentication rules
- the game engine players use
- the visual assets that make the game feel complete
The authentication software and core game logic should stay small enough to distribute widely and preserve over time. The asset layer is different. Art, models, music, and other media are larger, more legally sensitive, and harder to preserve safely.
Keeping the protocol separate from the assets makes the economy more resilient. Even if one visual client or asset pack disappears, the underlying player history and verification rules can survive.
The Revised Architecture
The newer version of the idea is more practical than trying to make everything fully decentralized from day one.
A central organization can run a client and server where players actually play. That organization writes its branch of player history to the blockchain using its own keys. If that organization disappears, the data remains.
Another group can later build a new client, read the old data, and continue the economy under the same protocol or a compatible branch of canon.
That is the real value of the project: not perfect decentralization, but continuity.
The economy should outlive any one server.
What The First Version Should Prove
The first useful version does not need a full Pokemon-style game.
It should prove the smallest version of the loop:
- define a public save-entry format
- write account progress entries to a durable log
- build a validator that labels obvious impossible progress
- support repentance entries
- let a second client read the same data and reach the same legitimacy result
- show that external trust signatures can affect how a trade is presented
If that loop works, the rest of the project becomes more believable.
The dream is an economy where the value of a collection comes from transparent history. Players can still cheat. Bots can still exist. Communities can still disagree about what counts as canon.
But the evidence is visible, portable, and harder to erase.
That is the part worth exploring.
Source concept: Project Poke Economy repository draft.