GalleryFRAYActivityLeaderboardStudio
GalleryArtistsFRAYActivityLeaderboardCode modulesHow it worksMy claimsStudio
HomeGalleryClaims

Discover, collect and make digital art that lives onchain. Built on KEEL, so every work stays viewable without depending on any one website.

Creative toolsPreserveDocumentationHow we verifyCode modulesLook up a workYour profile

Community

Public verification.

See the rules that decide which version of a work is shown. Anyone can propose a new version; approved versions go live after a public review period.

Attachments record matching content at exact revisions. Your viewer chooses which chain’s copy to present.

Nothing is pre-selected: you choose which network connection to read from. Note that an approved profile is a community decision; it doesn't by itself prove a work's files are genuine.

Inspect an attachment

Bitcoin mainnet first-envelope content to EVM, with uncompressed local content. Each result separates recorded acceptance, current profile admission and source status on the best submitted Bitcoin branch. A receipt records acceptance on this destination only.

Source status requires a membership path for the current submitted branch. An old proof can become stale after a branch update; refresh the evidence to distinguish an orphaned block from an unknown status.

Ethereum copy on Tezos

Inspect an exact Ethereum runtime-code range attached to a local KEEL revision. This route is undergoing acceptance testing; no public deployment is selected. Its current proof setup is for local testing.

Submission evidence

Paste the account proof, code bytes and exact source/local coordinates from your witness workflow.

Choose a deployment
Publish a candidate version

Publish the complete manifest first: proof program key, verifier implementation, checkpoint, finality rules, source schema and every mutable dependency. Its commitment is the Keccak-256 hash of the exact file bytes.