STAMP
STAMPS: A protocol for immutably storing images on-chain through Bitcoin transaction outputs IMPORTANT NOTICE：STAMPS IS A BLOCKCHAIN-AGNOSTICPROTOCOL。FOR RULES SPECIFIC TO THE BITCOIN STAMPS PROJECT，PLEASE VISIT: Using “art on the blockchain” as a means of achieving permanent preservation is, in the NFT world, generally a misnomer. Most non-fungible tokens are merely pointers to images hosted by centralized services, or data stored on-chain as prunable witness data. We propose a method of embedding base64-formatted image data through a novel use of transaction outputs. This is accomplished by encoding the binary content of an image as a base64 string and placing that string as a suffix in the STAMP: transaction description key, then broadcasting it to the Bitcoin ledger using the Counterparty protocol. Due to the length of the string, the Counterparty protocol uses bare multisig by default, thereby storing the data in chunks within transaction outputs rather than using the capacity-limited and prunable OP_RETURN. This allows the data to be preserved in a manner that full nodes cannot prune, thereby retaining it immutably forever. Given the cost of preserving data in this manner, we propose the following guidelines: 24x24 pixels, 8 color depth PNG or GIF. The limitations of this “canvas” are highly suited to pixel art. In particular, CryptoPunks use a native resolution of 24x24 pixels.STAMPS will be numbered according to transaction timestamps. This is intended to ensure that the STAMPS directory is arranged chronologically. The first STAMP will be the first transaction to contain a STAMP string in its description key with a valid base64 string appended, and so on. Transactions containing invalid or unintelligible base64 strings will not be considered STAMP。STAMP Numbering will begin at zero and continue indefinitely.
Overview
STAMPS: A protocol for immutably storing images on-chain through Bitcoin transaction outputs IMPORTANT NOTICE：STAMPS IS A BLOCKCHAIN-AGNOSTICPROTOCOL。FOR RULES SPECIFIC TO THE BITCOIN STAMPS PROJECT，PLEASE VISIT: Using “art on the blockchain” as a means of achieving permanent preservation is, in the NFT world, generally a misnomer. Most non-fungible tokens are merely pointers to images hosted by centralized services, or data stored on-chain as prunable witness data. We propose a method of embedding base64-formatted image data through a novel use of transaction outputs. This is accomplished by encoding the binary content of an image as a base64 string and placing that string as a suffix in the STAMP: transaction description key, then broadcasting it to the Bitcoin ledger using the Counterparty protocol. Due to the length of the string, the Counterparty protocol uses bare multisig by default, thereby storing the data in chunks within transaction outputs rather than using the capacity-limited and prunable OP_RETURN. This allows the data to be preserved in a manner that full nodes cannot prune, thereby retaining it immutably forever. Given the cost of preserving data in this manner, we propose the following guidelines: 24x24 pixels, 8 color depth PNG or GIF. The limitations of this “canvas” are highly suited to pixel art. In particular, CryptoPunks use a native resolution of 24x24 pixels.STAMPS will be numbered according to transaction timestamps. This is intended to ensure that the STAMPS directory is arranged chronologically. The first STAMP will be the first transaction to contain a STAMP string in its description key with a valid base64 string appended, and so on. Transactions containing invalid or unintelligible base64 strings will not be considered STAMP。STAMP Numbering will begin at zero and continue indefinitely.