v0.1 · spec

CLAWTIFACT docs

CLAWTIFACT is an AI glitch-transmission engine on Solana. You feed it any text; it returns a one-of-one artifact and a short decoded message. This page documents how that works, end to end.

Overview

Type a word, a ticker, or a feeling. CLAWTIFACT hashes that string into a seed, then uses the seed to drive a chain of corruption — channel splits, slice displacement, halftone, scanlines — and renders a unique piece of glitch art with a matching transmission.

The defining property is determinism: the same input always produces the same artifact. It behaves like a signature for a string — reproducible and verifiable by anyone who types the same thing.

Deterministic by design. Feed the same string and you get the same artifact, forever. Change one character and the whole signal corrupts differently.

How it works

1 · Feed

Any text becomes a seed via a fast FNV-1a hash. Short or long, emoji or ticker — it all collapses into a single unsigned 32-bit number that anchors everything downstream.

2 · Corrupt

The seed drives a small pseudo-random generator. Colour blocks, layout, channel offsets, and slice positions are all derived from it, so the corruption is chaotic to look at but completely reproducible.

3 · Transmit

Out comes the artifact plus a decoded message — three lines assembled and partially scrambled from the same seed. Download it, share it, or feed the output back in as a new input.

The pipeline

From string to signal, every stage is a pure function of the seed:

input ──▶ hash (FNV-1a) ──▶ seed : uint32
                               │
         ┌─────────────────────┼─────────────────────┐
         ▼                     ▼                     ▼
   palette + layout      RGB channel split     slice displacement
         │                     │                     │
         └─────────▶  halftone + CRT scanlines  ◀─────┘
                               │
                               ▼
        artifact (canvas)  +  transmission (text)

Because each box only depends on the seed, nothing about the result is random at render time — the randomness is "baked in" the moment your input is hashed.

Architecture

The engine that runs on this site is fully client-side. There is no server call, no API key, and nothing to wait for — the artifact is generated in your browser the instant you hit Transmit.

  • config.js — single source of truth for the contract address and links
  • glitch.js — the deterministic engine: hash, seeded RNG, renderer, transmission
  • site.js — shared behaviours: copy-CA, buy links, image slots, reveal

A deeper, server-side transmission agent is planned for after launch — a Fastify service backed by Supabase, with model-written transmissions through OpenRouter — but the core artifact will always be reproducible from the same client-side seed.

One contract, wired once. Every Buy button and the copy-CA pill read from a single value in config.js. Set the address there on launch and the whole site updates — no other edits.

Tokenomics

  • Supply — 1,000,000,000 $CLTI, fixed, no mint authority
  • Launch — fair launch on pump.fun, 100% to the curve, no presale
  • Tax — 0% on buys, 0% on sells
  • Liquidity — LP burned on migration

Contract address: TBA

Verify before you buy. Always confirm the contract address matches the one shown across this site before swapping. $CLTI is a community token with no intrinsic value or expectation of return.

Roadmap

  • Launch + live countdown — June 17, 16:00 UTC
  • Server-side transmission agent (Fastify · Supabase · OpenRouter)
  • Mintable artifacts on Solana — anchor a transmission on-chain
  • Community gallery of the strongest signals

FAQ

Is the same input always the same artifact?

Yes. The artifact is a pure function of the hashed input. Re-corrupt in the Studio rolls a new seed for variations; Transmit returns the canonical one.

Do I need a wallet to use the engine?

No. The engine is free and runs in your browser. A Solana wallet is only needed to buy $CLTI.

What can I do with an artifact?

Download the PNG, share it on X, or feed it back in. On-chain minting arrives on the roadmap after launch.