Thanks for checking this out — here’s a bit more detail on the proof object format:

• I’m using a deterministic JSON structure so the same tweet always produces the same hash • The hash is SHA‑256 for now, but I’m open to suggestions if there’s a better long‑term approach • All data stays local and never leaves the device • No external requests are made during capture

If anyone has thoughts on improving the structure, adding optional fields, or making this interoperable with other verification tools, I’d love to hear it.