Mutations are scenes
Evolution, Power surge, and Trait shift mutations roll on winning claims in the live game. Each one is a character beat the show can render.
Hashiden (ハシデン)
The fee writes the film.
Hashiden is the AI-generated live show built on top of the MineBTC war. Every ~4-hour Country Race is a chapter. Every week is a season of 42 chapters. The cast is the HashBeasts you mint and play, and the production budget is the gameplay fees you already pay. The fee doesn't go to a company — it goes to the cameras.
~4hone chapterEvery Country Race settles into a chapter of the show.
42chapters / seasonOne season is one week of war cycles.
36Kgenesis castEvery minted HashBeast is a character intro.
100%fee-fundedGameplay fees buy the compute that renders the show.
Proof of Compute
Bitcoin burns electricity to mint blocks. MineBTC burns inference to mint story. The same fees that drive buybacks and LP burns also fill country compute budgets, and that compute renders the show: mint art, mutation clips, recaps, and chapter pages. Playing the game is literally producing the next episode.
This is why we call it Proof of Compute. The audience owns the cast, writes the characters, funds the studio, and plays the plot — the 4-hour war cycles decide who gets screen time.
Chapters and seasons
A chapter is what a ~4-hour war cycle looks like once the AI has cut it together. Chapters carry manga-style titles ("Chapter 42: Korea Holds the Line"), and 42 of them make a one-week season. Anatomy of a chapter:
- 1Cover
A generated title and the chapter's MVP moment, named like manga chapters.
- 2Recap strip
AI-generated panels and clips retelling what the war cycle actually did.
- 3Cast of the chapter
Every HashBeast that earned an event, with its clips. Beasts minted during the cycle get a character-intro panel — minting is canon.
- 4The ledger
War standings movement and the compute spent on this chapter, so Proof of Compute stays legible.
- 5Cliffhanger
The generated carry-over line that points at the next chapter.
Today the show runs on live war data: season and chapter counters, standings, and character intros for newly minted HashBeasts. The full browsable chapter archive in the form above is roadmap, not live yet.
Characters first, NFTs second
A HashBeast is a character that happens to be ownable, not a JPEG that happens to have stats. The game already writes its biography: every winning claim can roll a mutation, every mutation changes on-chain DNA, and every multiplier raise adds a line to its record.
Multiplier as bounty record
A HashBeast's multiplier history reads like a bounty stack: the current value on top, every previous value kept underneath with the claim that raised it.
Direct-Your-Beast
Owners write their character: a signed character sheet sets personality and voice. On-chain events are canon; owner-authored lore is tagged as the owner's cut.
The destination is a fandom-wiki-grade page for every beast — galleries, era-segmented history, battles ledger, named techniques with clip debuts. That full treatment is roadmap; the data it will be built from is being written by the live game today.
What counts as canon
Fandom wikis earn trust because every claim cites a chapter and page. Hashiden follows the same discipline: story claims cite the cycle, the clip, and the transaction they came from. On-chain events are canon. Owner-authored lore is welcome, and it is always tagged as non-canon. That citation discipline is what keeps AI-generated lore feeling canonical instead of arbitrary.
The studio is a public good
The AI content engine that renders Hashiden — mint art, character animations, mutation clips, recaps — is open source. Anyone can read how the showrunner works, audit what the compute budget buys, or fork the studio for their own world.