Build a Bitcoin-style meme blockchain with a browser node and Actions testnet

A Redditor gave Claude Code a one-line brief and in about three weeks shipped memechain: a proof-of-work chain with a Python node, a matching browser node and a serverless testnet.

Done withClaude CodeinGitHub· Nov 2, 2026

What they did

The poster, u/regressiveparty, wanted to learn how an on-chain market works without launching a coin. The brief to Claude Code was that every meme gets its own block. Working in the terminal, with the poster reviewing and testing each step, Claude Code wrote a small Bitcoin-like chain: double SHA-256 proof of work, difficulty retargeting every 10 blocks, halving rewards, secp256k1 wallets, and memes recorded as signed inscriptions of the image hash that can be listed and sold for a test token. It built the Python node first, then ported it line by line to JavaScript for the browser, with a test that checks both produce the same hashes. It also drove Playwright against the local page and judged its own screenshots, and proposed running the public testnet as a GitHub Actions job every 20 minutes that mines blocks and pushes the chain export to a branch the static site reads.

How it went

The project is live on GitHub Pages and open source under MIT after roughly three weeks. Two layout passes from the screenshot critique were thrown out. The browser miner first locked up the UI until mining moved to batched nonce loops, and the first difficulty retarget overshot badly on the fast browser chain until a clamp was added. The few comments were friendly but did not test the consensus rules.

Worth knowing

The cross-language test was what kept later changes honest: every edit had to pass in both Python and JavaScript. The token has no value and is not for sale, so this is a learning project, not a production chain. Every tenth block hash is also anchored in Bitcoin through OpenTimestamps.

Try it

With Claude Code· 5 parts to fill in

Build a small [Bitcoin-style or other] blockchain for [what each block records] as a learning project. Write the reference node in [Python] first with proof of work, difficulty retargeting, signed transactions and a full replay-from-genesis validator. Then port it line by line to [JavaScript for the browser] and add a test that fails if the two implementations disagree on any hash. Use [Playwright] to screenshot the web UI and critique the layout yourself. Propose a way to run a public testnet without an always-on server. Stop after each milestone, show me the test results and wait for my go-ahead before moving on.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related