Stamp Validator

A Bitcoin Stamp is a digital artifact written directly into Bitcoin transaction data. Instead of pointing to an external file, the artwork itself is encoded on-chain, making it permanent, immutable, and easy to verify from the original transaction.

Classic Stamps store art images as base64 data using the Counterparty protocol. Because the data lives in Bitcoin outputs rather than prunable storage, it is designed to remain preserved by full Bitcoin nodes.

SRC-20 extends the Stamp idea from art to tokens. It defines a simple standard for deploying, minting, and transferring fungible tokens on Bitcoin using Stamp data, with current SRC-20 activity encoded directly on BTC.

When you enter a transaction hash, the validator asks a public Bitcoin node for the raw transaction data. This is the same source of truth a block explorer would read, the app uses it to fetch the transaction and bring the raw Bitcoin data back into your browser.

The app runs a small Rust indexer, compiled to WebAssembly, that checks the transaction locally. It looks for known Stamp patterns, extracts any metadata it can find, and turns the result into organised readable text, with a stamp image and data or token metadata. So you can verify whether the transaction contains a valid Bitcoin Stamp.

The validator fetches the raw transaction from Bitcoin L1 through public nodes, then extracts and displays:

General

• Transaction hash, block index, block time, confirmations, fee, and virtual size.
• Creator address, keyburn status, Stamp hash, and valid Bitcoin Stamp status.

Art Stamps specific (CLASSIC/SRC-721)

• File type, file size, encoding method, file hash, and base64 validity.
• Base64 image data, plus title and artist when the Stamp includes them.

Token specific (SRC-20)

• Token ticker, transaction type, and sender, creator, mint, or receiver address.
• Amount, max supply, and mint limit when included in the SRC-20 payload.

The Stamp protocol and the Stampchain APIs add meaning on top of raw Bitcoin L1 data. They connect many transactions, Counterparty records, indexed protocol rules, cached media, holder data, and market data that cannot be fully known from one raw Bitcoin transaction alone.

General

• Canonical Stamp number, CPID or asset ID, transaction index, message index, and protocol status.
• Creator names, balances, holder counts, collection data, cached media URLs, and explorer-ready records.

Art Stamps specific (STAMP/SRC-721)

• Asset supply, locked or divisible status, reissue status, collection membership, and rendered Stamp media.
• Marketplace context such as floor price, market cap, recent sale data, and available listing information.

Token specific (SRC-20)

• Current token state, valid deploy history, minted supply, holder balances, and full transfer history.
• Token market data such as price, market cap, 24h or 7d volume, price change, and holder distribution.

Check your transaction on stampchain.io to see all Stamp metadata.

Bitcoin Stamp is still a young protocol, shaped by builders, artists, collectors, and token communities who care about permanent data on Bitcoin. The community is vibrant, supportive, and inclusive, making it a good place to ask questions, follow new standards, and learn from people creating and collecting Stamps.

Follow Stampchain on X for updates, join the Bitcoin Stamps Telegram to meet the community, and read the Stampchain GitHub pages for protocol specs, indexer code, API docs, and open-source tools.