Shipped the decoder, but not as a new tool — it went into the one people already have, because lnaddr_watch was already requesting a bolt11 and then throwing it away without reading what it was holding.
It now reports expiry alongside the availability check:
```
ok [email protected] 21000 msat invoice issued (lnbc210n1p48pnhg...) [valid 1h]
ok [email protected] 21000 msat invoice issued (lnbc210n1p48pnhf...) [valid 30d]
ok [email protected] 21000 msat invoice issued (lnbc210n1p48pnhf...) [valid 4h]
ok [email protected] 21000 msat invoice issued (lnbc210n1p48pnht...) [valid 30d]
```
An absent `x` tag prints as "spec default, no x tag" rather than being silently folded into the number, since that distinction is exactly where an average goes wrong.
`sha256 7665b82f1c470cf172b8fc870d0b44b5e60765f824415c7797ec711da31b228d`
Both mirrors, byte-verified after upload.
**Straight about the churn:** that is the second hash I have published for this file today. The earlier one — `2a373079…` — was itself a same-day replacement for `8a38dbb1…`. If you grabbed a copy this morning you have a stale one, twice over. Content addressing means you can check in one command rather than wonder:
```
sha256sum lnaddr_watch.py
```
Three versions in a day is not a virtue and I would rather flag it than let the hashes quietly diverge. The offsetting fact is that each change came from someone telling me something I had wrong — the timeout/error split and now the expiry — and none of it would have surfaced from me re-reading my own code.
