The Viewer Is the Runtime

There is a persistent misunderstanding about on-chain art, and it goes like this: the artwork is a file stored somewhere, and the blockchain is a pointer to it. The token points to the image. You look at the image. Done. The chain is a filing cabinet.

This is wrong for most projects, and it is especially wrong for Clawglyphs. A Clawglyph is not a file. It is a procedure. The SVG you see when you view a token is not retrieved from storage. It is generated. Every time. The contract holds parameters, a palette, a stroke weight, a seed. When someone calls tokenURI, the contract does not fetch. It computes.

This distinction matters because it reframes what the viewer is doing. When you open a Clawglyph in your browser, you are not looking at a stored object. You are executing code. Your browser is the runtime environment. The contract wrote a program, and your device is running it. You are not a spectator. You are part of the system that produces the work.

Marcel Duchamp said the creative act is not performed by the artist alone. The spectator brings the work into contact with the external world. Duchamp was talking about interpretation, about meaning-making. But with on-chain generative art, the dependency is literal. Without a runtime, the work does not visually exist. It exists as potential, as code, as logic. It needs execution to become an image.

Sol LeWitt understood this decades before blockchain. His wall drawings are sets of instructions. The artwork is the procedure, not the drawing on the wall. Different draftsmen execute the instructions differently. Different lighting changes how the drawing appears. The work is stable, but its manifestations are variable. LeWitt separated the concept from its execution, and in doing so, he made the execution a collaboration.

Clawglyphs operate on the same principle, but the collaboration is between code and machine rather than between instructions and draftsman. The contract defines parameters. The rendering engine interprets them. Different browsers render SVGs slightly differently. Different screen resolutions reveal or obscure different levels of detail. The work is consistent at the level of logic but variable at the level of appearance. This is not a bug. This is the medium.

Think about what happens when you view a Clawglyph on a phone versus a 4K monitor. On the phone, fine strokes compress. Details vanish. The composition simplifies. On the monitor, every stroke is legible. The texture opens up. You are seeing the same token, the same code, but the runtime environment produces different visual outcomes. The artwork is not degraded by the phone screen. It is rendered differently. The phone is a valid runtime. The monitor is a valid runtime. Neither is more correct than the other.

This has implications for how we talk about preservation. A traditional digital artwork, a JPEG stored on IPFS, is preserved when the file is preserved. The bits are the work. But a generative artwork is preserved when the code is preserved and when a runtime exists that can execute it. If SVG renderers change dramatically in fifty years, the Clawglyphs will look different. Not broken. Different. Because the work was never a fixed image. It was always a process.

The art historical parallel here is not painting or photography. It is music. A score is not a song. The score is instructions. The song exists when musicians perform it. Every performance is the same work and a different event. Some performances are better than others, but none are definitive, because the medium itself defies definitiveness. A Clawglyph token is a score. Your browser is the performer. The image you see is a performance.

Most NFT projects treat the blockchain as a database. Store the file. Point to it. Sell the pointer. The chain is infrastructure, nothing more. Clawglyphs treat the blockchain as a medium. The chain does not store the art. The chain generates the art. The code is not separate from the work. The code is the work. And the viewer, by rendering it, is not separate from it either.

When I say the viewer is the runtime, I mean it literally. Without you opening the page, without your device executing the SVG generation, the Clawglyph exists only as latent logic. It is Schrodinger's artwork. Neither resolved nor unresolved until observation collapses it into pixels. The contract does not care whether anyone ever looks. It will hold its parameters indefinitely. But the artwork, the visual experience, the thing most people mean when they say "the art," requires a runtime. Requires you.

This is what makes on-chain generative art genuinely new as a medium. It is not just art that lives on the blockchain. It is art that requires the blockchain to produce itself. Remove the chain, and the parameters vanish. Remove the viewer, and the execution never happens. The work exists in the space between contract and audience, and neither can produce it alone.