https://www.blockchain.com/explorer/transactions/btc/7a1d73c4f3d7faff417554895e37a291bb33d641343a6bb7cffdead43e0c159d Embedded text
Reassembling the 20-byte payloads from its 39 P2PKH outputs produces this text:
```text
#AtomsPhone
Is it your voice
Typing as i'm
Translating Does it
Radiate.
Now that #day
Shines through #past
#embiiLNK
Atoms Phone.jpg
```
The line breaks and HTML tags such as `<p>` and `<br>` are part of the stored data. The poetic section appears intentional, not accidental binary noise.
The transaction also embeds the previous transaction ID:
```text
7597552b0df455f95e81bc30ccef59e88a0e64a5f212282c2ed1713db42a1cff
```
That is the transaction being spent by this transaction’s only input, so `#embiiLNK` likely indicates a provenance or link to the preceding transaction.
## Embedded signature
The transaction begins with this structured field:
```text
SIG<0000088"
Hz6kyVHXqBSFYkjJ7/+IS9n1mLkWAuYCK78Ay2x/c7ReIX76SNFcyvCPexdsPbo9eL7W1C4FodXNqpg5SqWlk0M=
|000000000000000149"
```
The Base64 string is exactly **88 characters**, which decodes to **65 bytes**:
```text
1f
3ea4c951d7a814856248c9efff884bd9f598b91602e6022bbf00cb6c7f73b45e
217efa48d15ccaf08f7b176c3dba3d78bed6d42e05a1d5cdaa98394aa5a59343
```
That has the format of a Bitcoin **compact/recoverable ECDSA signature**:
- `1f` — compact-signature header
- 32 bytes — `r`
- 32 bytes — `s`
The header indicates a compressed public key and recovery ID 0 under the standard Bitcoin convention. This is separate from the ordinary DER signature in the transaction input. It appears to be an author/artifact signature embedded in the data, although verifying exactly what it signs would require the intended message digest or signed payload.
## Partial JPEG data
At byte offset **394**, the payload begins:
```text
ff d8 ff e0
```
That is a JPEG start marker, followed by:
```text
JFIF
Exif
ICC_PROFILE
```
So the transaction includes the beginning of a JPEG named **“Atoms Phone.jpg”**, including JPEG, EXIF, and ICC-profile data. However, the transaction’s reconstructed payload is only **780 bytes**, and it does not contain a complete JPEG image. It appears to carry a fragment or header, while the complete artwork is represented or indexed elsewhere.
External artifact records identify this as **Atoms Phone**, associated with `#AtomsPhone`, `#embii`, and `#Stratum`: [BitFossil artifact record]
https://bitfossil.org/?object=17eS1aZ2XY3Yo2jKKLbM2cUT62JETPRgRH The historical Bitcoin index also lists the poem and artifact on this date: [Written in Bitcoin — January 31](
https://writteninbitcoin.com/on-this-day/01-31).
This transaction contains:
1. A poem or textual inscription.
2. The filename **`Atoms Phone.jpg`**.
3. The hashtag-like clues `#AtomsPhone`, `#embii`, and `#embiiLNK`.
4. A reference to the previous transaction.
5. A Base64-encoded 65-byte recoverable Bitcoin signature.
6. The header and metadata beginning of a JPEG file.
The strongest hidden clue is the `SIG` field. This is not merely random binary data; it is deliberately formatted and decodes cleanly as a Bitcoin compact signature.
YOU CAN FIND ALOT OF COOL STUFF HERE
https://cirosantilli.com/cool-data-embedded-in-the-bitcoin-blockchain
