Selected work / Ethereum / characters
Ethereum Codex Pets
An unofficial fan-made collection of animated Ethereum-themed desktop companions.

The idea
A gallery that leads to a portable pet.
This selection keeps the gallery, a character page and another character page. The stills document the public interface as captured in September 2026.
Unofficial fan art. Named people and organizations have not endorsed the collection. Original artwork and package rights require review before reuse.
Three selected moments
A closer look.
Move through the selected stills.

01 / Selected moment
The gallery
The gallery from the captured Ethereum Codex Pets interface.
Open full image ↗
02 / Selected moment
A character page
A character page from the captured Ethereum Codex Pets interface.
Open full image ↗
03 / Selected moment
Another character page
Another character page from the captured Ethereum Codex Pets interface.
Open full image ↗Make something of your own
Build your own.
Take the idea into Codex and adapt it to your own subject, sources and audience.
Reconstructed recipe · Not the original prompts
An end-to-end recreation has not been tested.
01BriefDefine the experience
Build a new interpretation of Ethereum Codex Pets: An unofficial fan-made collection of animated Ethereum-themed desktop companions. Read the repository instructions and preserve existing work first. Reconstruct the idea from this selection; do not promise an exact recreation. Start with one complete useful flow.
02IngredientsPrepare sources and assets
Preserve selected spritesheets, manifests, animation timings, transparency and package structure with character provenance. Use supplied or authorized artwork and avoid copying brand assets as endorsements.
03InteractionBuild the core flow
Build lightweight gallery previews, per-character share pages and validated downloads. Load only visible animations, support reduced motion, and test a pet package in the intended runtime before describing it as installable.
04Verify & preserveLeave a working handoff
Check the real production route, keyboard operation, mobile layout, reduced motion, asset loading and failure states. Record what passed and what remains untested. Leave source, lockfiles, setup instructions, data provenance and unique selected assets in a compact package. Exclude secrets, dependencies and caches. Label reconstructed prompts honestly; a local package is not a NAS backup.