pull down to refresh

It will always be possible to embed data in bitcoin transactions that can be interpreted as images or whatever the people who do this kind of thing like (eg shitcoins, insults, manifestos). Block size limits and fees are the best (and original) solution.

"""Build and extract JPEG XL images carried by a Bitcoin transaction pair.
The JXL codestream is split across ``jxlp`` container boxes.  Small ``free``
boxes absorb Bitcoin witness-script framing, so one contiguous suffix of the
raw reveal transaction is itself a valid JPEG XL file.  No push reassembly or
other post-processing is needed.
This program never signs or broadcasts.  ``encode`` writes:
* an unsigned commit transaction and a PSBT for the funding wallet;
* a complete reveal transaction whose inputs spend the commit outputs; and
* a manifest containing txids, fees, and the one-based ``tail -c`` offset.
The funding input must be native SegWit.  Signing then changes only the commit
witness, not its txid, so the pre-built reveal remains valid.
"""
Proof:

bitcoin-cli getrawtransaction c99ba3723689aa70d548b5188b3417f78c4f41a783f67d437810a209ee53d387|xxd -r -p|tail -c+1073>l.jxl

Inspired by https://t.co/QfVNdvUc68

Why must we continually try to solve the problem Satoshi already solved?