# A claim that can be checked

Use this record with the worked examples first. For personal use, keep private financial details in your own secure records; the blank file does not need account numbers or credentials.

| Record field | Your observation |
|---|---|
| Chain and asset identifier |  |
| Transaction ID / block ID / metric |  |
| Quantity unit |  |
| Covered time interval |  |
| Publication time |  |
| Retrieval time / confirmation status |  |
| Address-label source and date |  |
| Internal-transfer treatment |  |
| Alternative explanation |  |
| What remains unknown |  |

### What does the record actually establish?

A vendor labels the destination of a 1,000-token transfer as an exchange. Write the strongest supported claim and two facts needed to call it a sale. Then calculate the block-170 transaction fee. Finally, explain whether a revised label proves that an old signal was available in real time.

The transfer and dated attribution can be verified. They do not establish the sender's identity, a completed sale or intent. Calling it a sale needs evidence of a completed exchange and its connection to this transfer.

The fee is 50 BTC in minus 10 BTC and 40 BTC out: zero. This says nothing about the outputs' purpose.

A revised label may improve historical description without proving what a trader knew. Preserve dated versions where available; if only revised history exists, leave real-time signal availability unresolved.