The honest authorship stance
The project's adopted disclosure is AI-produced visual assets under CryptoLegends creative direction and curation. This does not mean hand-drawn, no-AI, independently original, or automatically rights-cleared. Individual creator, tool, licence, and acceptance records still need review.
Every artifact in this recovery edition is marked candidate, with art approval pending and rights unreviewed. These previews are for local evaluation, not an approved commercial release.
Three layers, kept separate
- Source reference. A package-relative filename, dimensions, and SHA-256 of the supplied original. Original files remain untouched outside this app.
- Web derivative. A full-aspect WebP preview, at most 960 pixels on its long side. Its own hash records the exact displayed file. It is not a 4096px editable master or final 2048px renderer deliverable.
- Candidate record. A versioned JSON entry with the source relationship, current review state, and limitation notes. No wallet or chain call is needed to download it.
What checksums do, and do not, prove
SHA-256 can establish whether a file matches a trusted byte reference. It does not establish authorship, copyright ownership, aesthetic quality, achievement, or that a publisher has not replaced both a manifest and its image.
The local Node validator checks schema, path safety, referenced preview files, and byte hashes. Source-master verification is a separate operator command. The stricter release gate deliberately fails while art and rights remain unresolved.
Not a Genesis release
This is a new 12-record candidate preview, not the historical 80-record pilot, a production rarity distribution, allocated NFT IDs, an IPFS publication, or an immutable on-chain root. Earlier technical successes retain their original scopes; they have not been relabeled as approval.
See the status page for actual recovery checks and the release log for the scope change.
Check a downloaded preview
The file stays in your browser. No upload, wallet connection, or server-side processing.
A checksum is only useful against a trusted reference. This local check cannot prove who created the image or whether a publisher changed both image and manifest.