DOCS

Overview

ETCH'D is an onchain art marketplace and press in the CypherPunks ecosystem. It stores the exact artwork bytes in EVM contract code, deploys artist-configured sale contracts from pinned templates, and provides discovery, profiles and a secondary market around that permanent core.

The marketplace is in public beta. Ethereum Sepolia and Shape Sepolia use test assets with no real-world value. Mainnet is not live.

Etching a work

1. Configure: the artist chooses the file, title, sale type, price or reserve, royalty and optional collection.
2. Permit: the artist signs an EIP-712 permit bound to the exact file, canonical inscription store and relay escrow.
3. Fund: the artist deposits the quoted relay amount into a permit-specific vault in RelayEscrow.
4. Write: the relayer fronts gas and writes the file to InscriptionsV2 in ordered batches.
5. Seal: the store seals the inscription only when the byte count and rolling content root match the signed permit.
6. Deploy: Factory verifies the creation-code prefix and deploys the selected auction, edition and optional collection template.
7. Claim: the artist signs the authorship claim and the service admits the canonical work to discovery.

The relayer can collect only the authorized amount and only after the exact work seals. An aborted run returns the vault. If the service disappears, the artist can rescue the deposit onchain after the 48-hour lock and any bounded run lease.

Contracts and addresses

These are the current public-beta deployments. All addresses below are testnet addresses.

What each contract does

• InscriptionsV2 stores and seals the exact artwork bytes.
• Factory deploys only pinned collection, auction and edition templates and records their provenance.
• ListingBookV2 manages public and private listings, token offers, collection offers and pull-payment settlement.
• RelayEscrow holds an artist's press-run deposit and gates relayed storage calls.
• Auction1of1, EditionSale and Collection are deployed per work, so there is no single shared address for them.

Auctions and editions

1 of 1 auctions

• A 24-hour clock starts with the first bid.
• The artist may set a reserve; zero means no reserve.
• Late bids extend the end by the anti-snipe period selected at deployment.
• The bid increment is fixed at deployment, with a 0.0001 ETH floor.
• Anyone may settle after the auction ends.
• If an auction remains unsettled two days after its end, the high bidder can reclaim the bid.

Editions

• The price and maximum supply are fixed at deployment; the cap is between 1 and 100.
• An edition may have an onchain opening and closing time.
• Each mint pays the artist and fee recipient. If a receiver rejects payment, the amount remains withdrawable.
• The artist may close a run by reducing its cap to the number already minted. A closed run cannot reopen.

Fees, royalties and the secondary market

The two 1% market fees and treasury address are constants in the deployed bytecode. External marketplaces are not forced to honor ERC-2981 royalties, and the ETCH'D secondary fee does not apply outside ListingBookV2.

A public listing leaves the token in the owner's wallet until purchase. Offers are held by the book until accepted or cancelled. Settlement splits the payment into the royalty, ETCH'D fee and seller proceeds.

How the feed works

The feed starts from the registry of admitted works, removes house-blocked works, and checks sale provenance against the appropriate ETCH'D factory. The feed switch changes the lens over that shared catalogue:

The Following lens requires a connected wallet so the page knows whose follow list to use. Collector qualification means either HASH'D coverage, or an X handle plus CypherPunks ownership in the wallet's linked group.

Manual sort options include Latest, Ending Soonest, Most Bids, Almost Gone, Lowest Price, Highest Price and Heaviest. Some sorts appear only where they make sense: Ending Soonest and Most Bids for auctions, and Almost Gone for editions.

The client refreshes the feed without forcing new cards into the visitor's current scroll position. A “new” notice lets the visitor load them deliberately.

The CypherPunks algorithm

The CypherPunks button turns on an optional server-side admission and ranking layer. It does not change a work's sale contract, price, ownership or royalty.

1. Admission

A work enters the algorithmic feed only after at least one CypherPunks-holding wallet group has liked it. Likes are signed social actions and are offchain.

2. Collector voice

Each qualifying linked-wallet group's voice is earned from:

• the accumulated hold-days of every CypherPunk it currently holds, with at least one day of weight per punk; and
• 30 day-equivalents for each line the group has written to the onchain mailing list.

All wallets in a mutually signed linked group are treated as one collector. Their punk weight is combined, but likes from multiple wallets in the same group count only once.

3. Market pulse

Freshness contributes separately:

• 60% of the pulse comes from mint/etch recency, with a seven-day half-life.
• 40% comes from recent economic activity, the latest primary sale or edition mint, with a three-day half-life.
• The economic component receives a 1.5× boost when a current owner belongs to a CypherPunks-holding linked group. The total pulse is capped at 1.

4. Final score

Collector voice is normalized against the strongest eligible work in the current result set. With the algorithm on and the sort set to Latest, the server score controls the order. Choosing a manual sort keeps the punk-admitted set but reorders it by the selected field. The algorithm preference is remembered in the browser.

Verification badges

Badges describe a specific relationship recorded by the press. They are not identity checks, KYC, authenticity guarantees or endorsements.

Badges can appear beside names in feed cards, work pages, comments, profiles, artist lists, activity, search and the salon. Following is separate: it is the connected visitor's personal relationship with that wallet.

Moderation

The blockchain retains what was written to it. ETCH'D controls only what its own service displays and serves.

Sensitive veil

A sensitive work stays available but appears behind a click-to-reveal veil. The artist can self-label it at etch time; the house can label it; community reports or local screening can also apply the veil.

Community reports

• A wallet must be signed in to report.
• Reports are deduplicated by linked-wallet group: one collector, one report.
• A CypherPunks-holding group has weight 3; another signed-in wallet has weight 1.
• A total report score of 5 automatically veils an unreviewed work.
• Reports can veil a work but cannot block or erase it.

Local image screening

After a successful etch, PNG and JPEG works are screened by a model running on the ETCH'D server. Artwork is not sent to a third-party AI service. High-confidence results can apply the sensitive veil; medium-confidence results create a note for human review. GIF, SVG, HTML, video, oversized images and failed classifications rely on artist labels, reports and house review.

House decisions

• Clear: removes a veil and prevents report arithmetic or the model from automatically re-veiling the work.
• Sensitive: keeps the work served behind the reveal veil.
• Blocked: removes the work from the feed, profiles, work route, share route, artwork gateway, byte endpoint and thumbnails served by this press.

What is onchain and offchain

The offchain layer makes the market usable, but it is not the source of truth for the artwork or sale contracts.

Security and support

The repository includes Foundry tests, pinned artifacts, deployment records, audit evidence and release-verification scripts. Review reduces risk; it does not eliminate it.

• Before a transaction, confirm the network, destination contract, value and fee summary shown by the wallet.
• For a sale, verify factory provenance on the work's chain rather than trusting the page or its address prefix.
• Testnet assets have no real-world value.
• Report vulnerabilities to kenny@cypherpunks.art with SECURITY in the subject.

See the repository's contracts/, scripts/ and docs/audit/ directories for implementation details, tests and review evidence.